Parse edge-update manifests with explicit supported versions
Unknown manifest fields are treated as executable update instructions. Replace loose parsing with a bounded schema.
- Focused work estimate
- 1h 15m + prerequisites
- Priority in the scenario
- Medium
- Engineering practice
- Validation · Update systems
Estimated field mix
- Embedded and edge60%
- Security40%
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 information kiosks receive small generated image blobs through a local update adapter. Simulate slots and boot outcomes in software; do not flash hardware or execute image contents.
Setup prerequisites
- Generate inert byte images with manifests and development-only signing fixtures.
- Implement simulated boot success failure and power-cut points.
Preceding work
No earlier ticket is required. Complete the project setup above.
Acceptance criteria
- Known schema parses
- Unsupported version rejects
- Oversized fields reject before allocation
Implementation constraints
- Manifests are data and never scripts.
Verification to include
- Parse valid inert image manifest
- Reject unsupported version
Deliverables
- Manifest parser and cases
Rollout and recovery
Reject new updates when schema identity is uncertain.
Value of the work
For the engineer: Practice update state machines and recoverable activation.
For the team: Inspect whether an engineer can prevent partial rollout from stranding devices under declared conditions.
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.