noCV
CKV-102 · Specify records

Distinguish missing local keys from empty values

Practice briefBugFoundational

Empty buffers are interpreted as Not found. Return explicit presence separate from byte length.

Focused work estimate
1h + prerequisites
Priority in the scenario
Medium
Engineering practice
API design · Data contracts

Estimated field mix

  • API design60%
  • 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.

Your next step

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

  • Empty stored value is found
  • Absent key is missing
  • Deletion yields missing

Implementation constraints

  • Avoid truthiness checks on encoded values.

Verification to include

  • Read empty value
  • Read deleted key

Deliverables

  • Read result contract and cases

Rollout and recovery

Revert callers to explicit result checking.

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.