Preparing the next view without exposing private workflow data.
System design · Phased project
Design a searchable audit archive with retention boundaries
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.
Practice brief · Version 5
Project scope
10 tickets / 3 phases
Total focused work estimate
32h + setup
Suggested stack
PostgreSQL · Object storage · TypeScript
Recommended next step
Start with AARCHIVE-101
Open the first ticket for its prerequisites, acceptance criteria, verification plan, and an editable task draft.
Practice storage tradeoffs, provenance and data-lifecycle decisions.
What the team gains
Review archive cost and retrieval guarantees before committing to infrastructure.
Before you start
Create synthetic audit events and local storage/search adapters.
Use an explicit fictional retention policy, not legal advice.
Delivery agreement
Ten scoped tickets across three phases. Build a synthetic local service or select a ticket after recreating its prerequisites; estimates exclude setup.
AI tools are welcome during implementation. Record assumptions, review the result, and verify its behavior.