Model edge-journal flash writes with explicit emulator constraints
The byte-array stub permits writes that real flash-like storage would reject. Declare and enforce the chosen emulator model.
- Focused work estimate
- 1h 30m + prerequisites
- Priority in the scenario
- Medium
- Engineering practice
- Emulation · Storage
Estimated field mix
- Embedded and edge60%
- Storage systems40%
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
No earlier ticket is required. Complete the project setup above.
Acceptance criteria
- Page boundaries are explicit
- Forbidden bit transitions fail
- Erase resets one selected page
Implementation constraints
- This models selected behavior and does not certify real hardware.
Verification to include
- Write allowed transition
- Attempt forbidden transition without erase
Deliverables
- Flash emulator contract and cases
Rollout and recovery
Stop journal writes when adapter behavior violates the declared model.
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.