RFC-010 Extension: Temporal Evidence Chaining — 2. Proposed Extension: `session_id` Field

AIGP Specification › RFC-010 Extension: Temporal Evidence Chaining › 2. Proposed Extension: session_id Field

← 1. Problem Statement · Section index · 3. Justification (Research Basis) →

2. Proposed Extension: session_id Field

2.1 Addition to RECORD Message

{
  "protocol_version": "2.0",
  "message_type": "RECORD",
  "app_id": "identity-service",
  "request_id": "req-123",
  "session_id": "sess-abc456",      // NEW — links related invocations
  "use_case": "chat",
  "user_id": "owner@ai-governance-protocol.org",
  "model_id": "us.anthropic.claude-sonnet-4-6",
  "timestamp": "2026-06-07T00:00:00Z",
  ...
}

2.2 Addition to TRACE Message

{
  "protocol_version": "2.0",
  "message_type": "TRACE",
  "session_id": "sess-abc456",      // NEW — same session links traces
  "trace_id": "trc-789",
  ...
}

2.3 Session Semantics

Field	Definition
session_id	Opaque identifier linking related invocations across time
Scope	All invocations within a logical interaction sequence
Lifetime	From first invocation to session close (or timeout)
Uniqueness	Unique per user + use_case + app_id + time window

2.4 Chain Construction

The governance server (governance-server) constructs chains from sessions:

Chain = ordered_by_time(
  SELECT * FROM records
  WHERE user_id = X
    AND use_case = Y
    AND session_id = Z
)

Multiple sessions from the same user + use_case form a longitudinal chain:

Longitudinal Chain = ordered_by_time(
  SELECT * FROM records
  WHERE user_id = X
    AND use_case = Y
  GROUP BY session_id
  ORDER BY min(timestamp)
)

---

← 1. Problem Statement · Section index · 3. Justification (Research Basis) →