Continuous Assurance Telemetry

Continuous Assurance Telemetry A data-flow diagram generated by Archify. 01 / Runtime signals 02 / Control checks 03 / Evidence store 04 / Consumers Traces · runs, spans · 01 / Runtime signals · Layer 04 Traces runs, spans Layer 04 Guardrail events · blocked calls · 01 / Runtime signals · Layer 04 Guardrail events blocked calls Layer 04 Registry state · scope, status · 01 / Runtime signals · Layer 04 Registry state scope, status Layer 04 Control checks · continuous · 02 / Control checks · Layer 05 Control checks continuous Layer 05 Evidence records · one schema · 03 / Evidence store · Layer 05 Evidence records one schema Layer 05 Dashboard · status tile · 04 / Consumers Dashboard status tile Auditor · audit = query · 04 / Consumers Auditor audit = query emit emit emit record live query query Legend primary data data store data flow

Evidence from the data path

  • • Traces, guardrail events and registry state are checked as the system runs
  • • Each check writes a timestamped, structured record on one schema
  • • Point-in-time attestation is replaced by a continuous signal

One queryable store

  • • control_id, subject, decision, metric, threshold, actor, timestamp, signature
  • • Records are keyed on the registry id so status is a live query
  • • A control that stops firing turns its dashboard tile red in minutes

Why continuous

  • • The evidence is produced by the data path, not a quarterly exercise
  • • The cost is the ingest pipeline and a common evidence schema