Reject edge settings unsupported by the declared gateway capability version
Older gateway emulators silently ignore new settings while reporting success. Check capability compatibility explicitly.
- Focused work estimate
- 2h 15m + prerequisites
- Priority in the scenario
- Medium
- Engineering practice
- Compatibility · Versioning
Estimated field mix
- Embedded and edge70%
- API design30%
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.
- CCONFIG-101 · Validate emulated display brightness and cache-limit settings
- CCONFIG-102 · Keep desired and reported edge configuration separate
- CCONFIG-103 · Scope emulated gateway configuration reads by organization
- CCONFIG-104 · Reject stale configuration revisions arriving at the edge gateway
- CCONFIG-105 · Stage edge settings before committing a complete configuration
Acceptance criteria
- Supported configuration applies
- Unsupported fields report incompatibility
- Reported revision does not advance on rejection
Implementation constraints
- Do not infer capability from device display names.
Verification to include
- Apply to compatible fixture
- Apply new field to older capability
Deliverables
- Compatibility check and cases
Rollout and recovery
Keep existing revision on unsupported gateways.
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.