Keep desired and reported edge configuration separate
Sending a setting immediately changes the dashboard to Applied before the gateway responds. Store separate desired and reported revisions.
- Focused work estimate
- 1h 15m + prerequisites
- Priority in the scenario
- Medium
- Engineering practice
- State modeling · Observability
Estimated field mix
- Embedded and edge50%
- Distributed systems30%
- Frontend20%
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-display gateways receive brightness schedules and cache limits. These settings affect only a software display emulator; no real devices, safety controls or customer data are used.
Setup prerequisites
- Define synthetic configuration schema and supported device capabilities.
- Implement local control-plane and gateway adapters with delayed messages.
Preceding work
Complete these dependencies, or supply their agreed outputs before taking this ticket.
Acceptance criteria
- Sending changes desired state
- Acknowledgement changes reported state
- Mismatch appears as pending drift
Implementation constraints
- Delivery is not application acknowledgement.
Verification to include
- Send then acknowledge
- Drop delivery and inspect drift
Deliverables
- State model and projection cases
Rollout and recovery
Stop displaying Applied when acknowledgement is absent.
Value of the work
For the engineer: Practice desired/reported state, compatibility and rollback.
For the team: Inspect whether remote configuration preserves working settings through offline and partial outcomes.
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.