Define which audit questions require indexed search versus archive retrieval
The design says all audit history must be instantly searchable, but reviewers usually inspect the last week and rarely retrieve older cases.
- Focused work estimate
- 1h 30m + prerequisites
- Priority in the scenario
- Medium
- Engineering practice
- Access-pattern analysis · Requirements
Estimated field mix
- System design60%
- Storage systems20%
- 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
No earlier ticket is required. Complete the project setup above.
Acceptance criteria
- List recent search and older retrieval use cases separately.
- State hypothetical latency and date-range targets.
- Identify fields that may be indexed without exposing payload contents.
Implementation constraints
- Use fabricated events and a named review workflow.
Verification to include
- Map a recent actor search to its target.
- Map an old case retrieval to the declared slower path without claiming instant search.
Deliverables
- Archive access-pattern inventory
Rollout and recovery
Review the inventory before choosing storage; keep unapproved fields out of indexes.
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.