Keep annotation review stable through collaborator updates
A colleague resolves a comment while another reader edits a reply. The panel reorders, steals focus, and sends the reply to the newly selected thread.
- Focused work estimate
- 3h 30m + prerequisites
- Priority in the scenario
- Medium
- Engineering practice
- Concurrent UI · Focus ownership · Conflict recovery
Estimated field mix
- Frontend50%
- Accessibility30%
- Real-time systems20%
Field percentages are editorial estimates of the ticket's engineering focus. They total 100%; they are not measured time, proficiency scores, or ownership evidence.
Review it, then add it to your workspace.
The board opens an editable draft; nothing is saved until you confirm it. Sign-in and workspace permissions apply, and Demo boards remain ephemeral.
Project context
The fictional Plainview handbook reader serves versioned HTML documents with headings, tables, footnotes, and annotations. Scope is accessible HTML rendering from a structured model; OCR and arbitrary PDF remediation are excluded.
Setup prerequisites
- Versioned synthetic documents with stable section IDs
- Annotation and document-access API contracts to stub
Preceding work
Complete these dependencies, or supply their agreed outputs before taking this ticket.
- READ-101 · Restore heading and table semantics in handbook chapters
- READ-103 · Navigate search matches without breaking document text
- READ-102 · Let readers adjust text without losing their place
- READ-104 · Keep contents links and footnote returns oriented
- READ-105 · Recover bookmarks after a handbook correction
- READ-106 · Render annotations safely and expose their controls
- READ-107 · Load long handbooks without losing reading order
Acceptance criteria
- Editing binds to immutable thread identity and revision, not list position.
- Remote updates never silently retarget a draft or move current focus.
- Resolved/deleted-thread conflicts preserve the draft, announce once, and offer explicit permitted recovery.
Implementation constraints
- Use fixture events; a full collaboration backend and automatic merging are excluded.
Verification to include
- Insert a remote comment above the active thread while typing; the draft keeps its original thread.
- Resolve the active thread during reply acknowledgement; no reply lands elsewhere and the confirmed state stays coherent.
Deliverables
- Revision-aware annotation model and concurrent-update tests
Rollout and recovery
Pilot manual refresh before live events; pause remote panel updates if focus or binding becomes unstable.
Value of the work
For the engineer: Practice semantic structure, accessible navigation, safe annotations, and stable reading positions.
For the team: Inspect how an engineer makes information usable while protecting document integrity and access boundaries.
Evidence boundaries
Outcome Evidence: Tests, patches, and runbooks are requested deliverables. They become Outcome Evidence only through a qualified Mission and immutable Evidence IDs.
Ownership Evidence: Independent adaptation must be observed under a declared verification policy and cite immutable Evidence IDs. Completing a planning ticket establishes no Ownership Evidence.