Semantic Observability Envelope (SDS-030)

Context-preserving telemetry for SEA™ Forge.


Envelope Structure

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
{
  "traceId": "12345...",
  "spanId": "abcde...",
  "timestamp": "2026-01-05T10:00:00Z",
  "semanticContext": {
    "domain": "Sales",
    "concept": "OrderPlacement",
    "regimeId": "regime:v1"
  },
  "provenance": {
    "executor": "agent:shipping-optimizer-v2",
    "trigger": "event:order-received"
  },
  "payloadMode": "full_fidelity",
  "data": { ... }
}

Signal Mapping

Signal Purpose Cardinality Control
Metrics Health, SLAs Strict (no entityId, userId)
Traces Causality entityId allowed
Logs Debugging Full payload (sampled)

Privacy Constraints

Type Rule
Direct PII REDACT or hash
Indirect PII Differential privacy
Sensitive Provenance Hash decision paths

Payload Modes

Mode Use Case Retention
full_fidelity Audit, debugging 7 days (7 years for audit)
aggregated Metrics, KG projection Indefinite

Correlation IDs

Header Purpose
traceparent W3C Trace Context
sea-correlation-id Business Transaction ID
sea-causation-id Direct Causal Parent

Invariants

ID Rule
INV-OBS-01 All telemetry must use OTLP
INV-OBS-02 PII must be scrubbed
INV-OBS-03 Semantic context preserved
INV-OBS-05 Logs correlate with traces

Last Updated: January 2026