noCV
CBACK-101 · Describe backup content

Define archive backup manifests with explicit format versions

Practice briefTaskFoundational

Backup folders contain unnamed files with no declared schema. Add a bounded manifest describing required objects.

Focused work estimate
1h 15m + prerequisites
Priority in the scenario
Medium
Engineering practice
Serialization · Validation

Estimated field mix

  • Storage systems80%
  • Data engineering20%

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 archive Alder backs up synthetic document metadata and generated blobs into a dedicated local directory. No real organizational data or cloud accounts are required.

Setup prerequisites

  • Create synthetic metadata and generated blob fixtures.
  • Provide isolated source backup and restore directories.

Preceding work

No earlier ticket is required. Complete the project setup above.

Acceptance criteria

  • Manifest declares version
  • Entries have size and digest
  • Duplicate logical paths fail validation

Implementation constraints

  • Treat manifest text as untrusted input.

Verification to include

  • Parse valid fixture
  • Reject duplicate and future-version entries

Deliverables

  • Manifest schema and parser

Rollout and recovery

Keep unknown backup versions read-only.

Value of the work

For the engineer: Practice consistent snapshots and recoverable restoration.

For the team: Inspect whether backup success can be substantiated by a usable restore.

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.