Sensor-to-asset assurance architecture

// Keep rejected readings traceable while accepted telemetry flows to operational views.
// Synthetic worked example: all entities, schedules and measurements are illustrative.
// Every string below is EXAMPLE text from a fictional model: replace it.
// Replace assumptions and inputs before applying this model to actual work.

system platform {
  title: "Illustrative Sensor-to-asset assurance architecture"
  owner: "Architecture working group"
}

actor user {
  title: "Asset operator"
  kind: "user"
  depends: [s0]
}

service s0 {
  title: "Device gateway"
  runtime: "Browser or edge client"
  tier: "edge"
}

service s1 {
  title: "Schema validator"
  runtime: "Stateless service"
  tier: "core"
  depends: [s0]
}

service s2 {
  title: "Quality quarantine"
  runtime: "Background worker"
  tier: "core"
  depends: [s1, d1]
}

service s3 {
  title: "Time-series processor"
  runtime: "Durable worker"
  tier: "core"
  depends: [s1, d0]
}

service s4 {
  title: "Asset dashboard"
  runtime: "Application service"
  tier: "core"
  depends: [s3, d0]
}

datastore d0 {
  title: "Telemetry series"
  kind: "postgres"
}

datastore d1 {
  title: "Quarantine evidence"
  kind: "object-store"
}

view architecture: c4_container(platform)