Commit edge-journal records only after their marker is durable
A record appears readable before its body finishes writing. Introduce a commit-marker protocol compatible with the emulator.
- Focused work estimate
- 3h + prerequisites
- Priority in the scenario
- High
- Engineering practice
- Durability · Atomicity
Estimated field mix
- Storage systems60%
- Embedded and edge40%
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 edge display gateway stores noncritical synthetic readings while disconnected. Implement a byte-array flash emulator with explicit erase/write behavior and injected power cuts; no physical storage device is required.
Setup prerequisites
- Specify emulator page size write rules and erase behavior.
- Generate synthetic records and deterministic power-cut schedules.
Preceding work
Complete these dependencies, or supply their agreed outputs before taking this ticket.
Acceptance criteria
- Uncommitted bodies stay invisible
- Acknowledgement follows durable marker
- Invalid marker cannot authorize partial body
Implementation constraints
- Specify write and flush ordering explicitly.
Verification to include
- Write committed fixture
- Cut power before marker
Deliverables
- Commit protocol and cut-point tests
Rollout and recovery
Disable acknowledgement if the durability barrier fails.
Value of the work
For the engineer: Practice torn writes, wear-aware batching and acknowledged durability.
For the team: Inspect whether offline device records remain recoverable within stated constraints.
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.