Recover bookmarks after a handbook correction
A correction inserts two sections before a bookmark. Its raw character offset now opens an unrelated paragraph.
- Focused work estimate
- 2h 30m + prerequisites
- Priority in the scenario
- High
- Engineering practice
- Versioning · Stable identity · Recovery UX
Estimated field mix
- Frontend70%
- Accessibility30%
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.
Acceptance criteria
- Bookmarks include version, stable section, and optional bounded text anchor.
- A newer version resolves the section or explicitly reports that the passage moved or disappeared.
- The permitted original version remains reachable without silently rewriting the bookmark.
Implementation constraints
- Approximate text matching is not exact; disclose ambiguity and retain the original anchor.
Verification to include
- Insert content before a stable section and reopen its bookmark; the intended section remains selected.
- Delete it and create two similar passages; show ambiguous recovery rather than silently choosing one.
Deliverables
- Version-aware bookmark resolver and correction fixtures
Rollout and recovery
Keep legacy bookmarks readable during migration; fall back to the permitted original version on uncertain resolution.
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.