← Back to the chapter · Next detail →

Technical detail · Applied: Edge Workload Placement

State changes and outage accountability

Level 2 moves packets and frames. Its evidence includes delivery status, link quality, retries, and addresses. Level 3 changes payload meaning: raw waveforms become features, device-specific payloads become a common schema, and readings become alerts, summaries, or local control actions. Level 4 changes persistence state by assigning retention, indexes, lineage, and replay rules. Levels 5 to 7 turn stored records into trends, dashboards, maintenance tickets, automation rules, or business decisions.

Write the corresponding contract at each crossing. For Level 3, name raw input, transformation, output summary, local rule or model version, and retained replay evidence. For Level 4, name schema, retention class, lineage key, and replay or deletion rule. For Levels 5 to 7, name analytics result, application action, owner, and business consequence.

During a cloud outage, a well-designed Level 3 gateway keeps applying local safety rules, buffers evidence, and forwards a compressed backlog when connectivity returns. During a gateway outage, Level 4 may contain stale records; a dashboard must label them rather than imply that fresh local assessment occurred. A versioned cloud rollout must identify the model actually running for each gateway decision, even when reviewed weeks later. The reference model is an accountability map as well as an architecture diagram.

← Back to the chapter · Next detail →