Encode edge-journal records with bounded length and checksum
Truncated synthetic records are indistinguishable from valid short payloads. Add explicit length and integrity fields.
- Focused work estimate
- 1h 30m + prerequisites
- Priority in the scenario
- High
- Engineering practice
- Binary formats · Integrity
Estimated field mix
- Embedded and edge50%
- Storage systems50%
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
- Payload bytes round-trip
- Length is bounded
- Checksum mismatch rejects record
Implementation constraints
- Checksum is corruption detection, not authentication.
Verification to include
- Encode valid record
- Flip one stored byte
Deliverables
- Record codec and corruption cases
Rollout and recovery
Keep affected pages read-only for inspection.
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.