Encode local key-value records with explicit length limits
Delimiter-based records fail when values contain newlines. Add a length-prefixed binary record format.
- Focused work estimate
- 1h 30m + prerequisites
- Priority in the scenario
- Medium
- Engineering practice
- Binary formats · Validation
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
No earlier ticket is required. Complete the project setup above.
Acceptance criteria
- Arbitrary bytes round-trip
- Key and value limits are enforced
- Version is encoded explicitly
Implementation constraints
- Specify byte order in the format note.
Verification to include
- Round-trip binary fixture
- Reject oversized declared length
Deliverables
- Encoder decoder and format document
Rollout and recovery
Keep old files read-only until conversion is explicit.
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.