Report edge-update stages without overstating fleet success
Dashboard counts downloaded images as updated kiosks. Project download, staged, boot-pending, healthy and rolled-back separately.
- Focused work estimate
- 2h + prerequisites
- Priority in the scenario
- Medium
- Engineering practice
- Reporting · State projection
Estimated field mix
- Frontend50%
- Embedded and edge30%
- Site reliability20%
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.
- CUPDATE-101 · Parse edge-update manifests with explicit supported versions
- CUPDATE-102 · Verify edge-update image size and digest before staging
- CUPDATE-103 · Validate edge-update manifests using local trust fixtures
- CUPDATE-104 · Write edge-update images only into the inactive simulated slot
- CUPDATE-105 · Record edge-update activation intent before changing the boot selector
- CUPDATE-106 · Mark an edge-update candidate healthy only after simulated boot confirmation
- CUPDATE-107 · Roll back failed edge-update boots without retry loops
- CUPDATE-108 · Reject unintended edge-update downgrades under an explicit version policy
- CUPDATE-109 · Limit concurrent downloads in the simulated kiosk update cohort
Acceptance criteria
- Healthy requires committed boot confirmation
- Rollback remains visible
- Unknown outcomes are not counted successful
Implementation constraints
- Reports describe simulator outcomes, not real-device certification.
Verification to include
- Complete one simulated update
- Interrupt another before boot confirmation
Deliverables
- Update status report and consistency checks
Rollout and recovery
Hide aggregate success if per-device authority is unresolved.
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.