Specify search indexing as a rebuildable projection of archived events
A search result is edited directly to correct an event, creating a version of history absent from the source archive.
- Focused work estimate
- 4h + prerequisites
- Priority in the scenario
- Medium
- Engineering practice
- Projection design · Append-only modeling
Estimated field mix
- System design50%
- Data engineering30%
- Database engineering20%
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
A fictional procurement platform keeps append-only action records. Operators want fast recent search and affordable old records without losing provenance or leaking tenant data.
Setup prerequisites
- Create synthetic audit events and local storage/search adapters.
- Use an explicit fictional retention policy, not legal advice.
Preceding work
Complete these dependencies, or supply their agreed outputs before taking this ticket.
- AARCHIVE-101 · Define which audit questions require indexed search versus archive retrieval
- AARCHIVE-102 · Calculate archive storage growth from event size and retention assumptions
- AARCHIVE-103 · Choose hot and cold archive boundaries with a reviewable decision record
- AARCHIVE-104 · Define an immutable archive segment manifest
Acceptance criteria
- Treat the index as a projection with source segment identity.
- Corrections append new events rather than rewrite archived facts.
- Define checkpoint and duplicate-indexing semantics.
Implementation constraints
- Use an in-memory search adapter for the contract probe.
Verification to include
- Rebuild the index from named manifests and preserve event identities.
- Replay a segment and verify no duplicate search records.
Deliverables
- Index projection model and replay test
Rollout and recovery
Build a shadow index generation; switch only after source-count reconciliation.
Value of the work
For the engineer: Practice storage tradeoffs, provenance and data-lifecycle decisions.
For the team: Review archive cost and retrieval guarantees before committing to infrastructure.
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.