Write edge-update images only into the inactive simulated slot
Update copying overwrites the currently selected image before validation finishes. Restrict staging to the inactive slot.
- Focused work estimate
- 3h + prerequisites
- Priority in the scenario
- High
- Engineering practice
- Isolation · Filesystem
Estimated field mix
- Embedded and edge50%
- Storage systems50%
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
Complete these dependencies, or supply their agreed outputs before taking this ticket.
Acceptance criteria
- Active slot remains byte-identical
- Inactive slot gets candidate bytes
- Failed write leaves active selection unchanged
Implementation constraints
- Slot paths must stay inside the fixture root.
Verification to include
- Stage valid image
- Fail copy midway
Deliverables
- Slot writer and isolation cases
Rollout and recovery
Abandon inactive candidate and retain active slot.
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.