Declare local write acknowledgement after the durability barrier
Put returns success before the log flush completes. Define durable acknowledgement using the filesystem adapter.
- Focused work estimate
- 3h + prerequisites
- Priority in the scenario
- High
- Engineering practice
- Durability · Filesystem
Estimated field mix
- Storage systems70%
- Database engineering30%
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
Fictional desktop cache Pebble needs a small embedded key-value engine. Build against generated keys and bytes using an ordinary filesystem adapter; no production database replacement is implied.
Setup prerequisites
- Create a disposable local fixture directory.
- Implement fault injection for partial writes, sync failure and process restart.
Preceding work
Complete these dependencies, or supply their agreed outputs before taking this ticket.
Acceptance criteria
- Success follows required sync
- Sync failure reports uncertain outcome
- Failed acknowledgement is not silently retried as new write
Implementation constraints
- Document the adapter's actual durability assumptions.
Verification to include
- Put with successful sync
- Inject sync failure after write
Deliverables
- Acknowledgement contract and fault cases
Rollout and recovery
Switch to read-only if durability barriers fail repeatedly.
Value of the work
For the engineer: Practice storage formats, durability boundaries and corruption handling.
For the team: Inspect whether an engineer can state and test persistence guarantees.
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.