Authorize edge reconnection

A returning edge agent must reconcile stale grants and actions before resuming normal authority.

01 / The operating case

What changes in a real workflow?

A disconnected controller reconnects after central policy revoked its valve-control grant.

Trace the authority boundary
  1. 01Authority origin
  2. 02Task and grant
  3. 03Current decision
  4. 04Observed outcome

02 / Decision contract

What the executor must check

Authenticate current workload, upload signed local decision sequence, compare policy and revocation epochs, quarantine conflicting actions and issue fresh grant.

InputPrincipal · task · action · target
DecisionGrant ancestry · policy · current state
ResultEnforce · record · verify outcome

03 / Failure and evidence

What goes wrong, and what can be proven?

Failure mode

The agent resumes cached authority before learning it was revoked.

Evidence to retain

Keep disconnect interval, local effects, new policy epoch, conflicts and resolution.

04 / Canonical scope

Why this reference stands alone

Offline edge action covers disconnection; this page owns safe re-entry.

Illustrative implementation artifact

Reconnection handshake

authenticate device workload
submit ordered offline decision log
compare grant and revocation epochs
quarantine conflicting actions
issue fresh grant only after reconciliation

Primary references

Read the underlying material

Architecture discussion

Choose one consequential action and make its boundary explicit.

Request a Conversation