Record a manifest before decoding a telemetry batch
Operators see a failed file name but cannot identify the original bytes or the parser version used.
- Focused work estimate
- 1h 30m + prerequisites
- Priority in the scenario
- Medium
- Engineering practice
- Lineage · Checksums
Estimated field mix
- Data engineering60%
- 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
A fictional energy dashboard receives hourly device batches. Corrupt archives and late corrections leave operators unsure which readings reached reports.
Setup prerequisites
- Create synthetic device batches and local object-store fixtures.
- Understand checksums and bounded streaming.
Preceding work
No earlier ticket is required. Complete the project setup above.
Acceptance criteria
- Record object version, byte hash and declared format.
- Bind each ingestion attempt to one manifest.
- Reject a changed object version on retry.
Implementation constraints
- Use synthetic object metadata; avoid storing credentials in manifests.
Verification to include
- Retry unchanged bytes against the same manifest.
- Replace bytes under the same object key and report identity mismatch.
Deliverables
- Manifest schema and identity checks
Rollout and recovery
Start manifests for new batches; retain earlier records as explicitly untracked.
Value of the work
For the engineer: Practice batch integrity, replay and data-quality boundaries.
For the team: Review whether operational data can be traced, corrected and recovered.
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.