Attach AgentPlane run/evidence refs to SourceOSInteractionEvent

[mdheller]

Mission

Bind AgentPlane run, replay, validation, placement, and evidence references into the shared SourceOS interaction substrate now merged in SourceOS-Linux/sourceos-spec#106 and indexed in SourceOS-Linux/sourceos-spec#115.

This complements AgentPlane#83. OpsHistory remains the local-first operational ledger. SourceOSInteractionEvent is the noetic/chat/task projection that Noetica emits and AgentTerm renders.

Context

Current downstream status:

• SocioProphet/Noetica#16 emits SourceOSInteractionEvent from chat lifecycle events.
• SourceOS-Linux/agent-term#46 ingests/renders/records interaction governance traces.
• SocioProphet/superconscious#59 tracks task-boundary accept/emit behavior.
• SocioProphet/agentplane#83 tracks OpsHistory context-pack intake and run/evidence emission.

AgentPlane should attach authoritative evidence and replay refs to interaction events rather than requiring Noetica, AgentTerm, or Superconscious to invent evidence semantics.

Required work

1. Add or mirror a bounded SourceOSInteractionEvent fixture with AgentPlane refs populated:
   • governanceTrace.agentPlaneRunRef
   • governanceTrace.evidenceRefs
   • governanceTrace.replayRef
   • optional validation / placement / context-pack refs as evidence refs.
2. Define how AgentPlane accepts a source interaction event or event ref during bundle validation/run submission.
3. Emit or return an interaction-event-compatible reference envelope after:
   • validation start/complete;
   • placement decision;
   • run start/complete/failure;
   • replay artifact emission;
   • evidence bundle emission.
4. Ensure AgentTerm can render the resulting event without custom AgentPlane-specific parsing.
5. Ensure Noetica/Superconscious can carry the AgentPlane refs without becoming evidence authorities.

Boundary rules

• AgentPlane owns execution evidence, run artifacts, replay artifacts, validation artifacts, and placement artifacts.
• AgentPlane does not own Matrix/terminal/browser surfaces.
• AgentPlane does not own Memory Mesh writeback, Agent Registry grants, or Policy Fabric admission.
• Do not place raw execution logs, secrets, unrestricted shell output, or private chain-of-thought in the interaction payload.
• Use refs/hashes/evidence bundle IDs for artifacts.

Acceptance criteria

• Fixture exists showing SourceOSInteractionEvent populated with AgentPlane run/evidence/replay refs.
• Validation/docs explain the relationship between OpsHistory context-pack intake and SourceOSInteractionEvent governance trace output.
• A dry-run path can consume a Noetica/Superconscious-origin interaction ref and emit AgentPlane refs.
• AgentTerm can render the resulting governance trace as-is.

Related

• OpsHistory context-pack intake and run/evidence emission contract #83
• Accept and emit SourceOSInteractionEvent at the task boundary superconscious#59
• Add SourceOS interaction substrate for Noetica and AgentTerm SourceOS-Linux/sourceos-spec#106
• Index SourceOS interaction substrate in contract catalogs SourceOS-Linux/sourceos-spec#115
• Emit SourceOSInteractionEvent from Noetica chat lifecycle Noetica#16
• Render SourceOSInteractionEvent governance traces SourceOS-Linux/agent-term#46