Skip to content

Ingest and render SourceOSInteractionEvent governance traces #43

Description

@mdheller

Mission

Bind AgentTerm to the shared SourceOS interaction substrate from SourceOS-Linux/sourceos-spec#106.

AgentTerm remains the terminal-native / Matrix-first operator console. It should ingest and render the same SourceOSInteractionEvent shape emitted by Noetica, Superconscious, AgentPlane, Matrix, or terminal command flows.

Required contract

Implement an AgentTerm-side model/adapter for SourceOSInteractionEvent aligned to SourceOS-Linux/sourceos-spec/schemas/SourceOSInteractionEvent.json once sourceos-spec#106 merges.

Required capabilities

  • Load a SourceOSInteractionEvent fixture from JSON.
  • Validate or minimally check required fields without live network dependencies.
  • Convert interaction events into AgentTerm-local AgentTermEvent records where appropriate.
  • Render governance trace fields in terminal-readable form:
    • policy admitted / blocked;
    • policy refs;
    • grant refs;
    • memory scope and memory-written posture;
    • context-pack refs;
    • request hash;
    • evidence hash;
    • provider route evidence ref;
    • AgentPlane run ref;
    • evidence refs;
    • replay ref;
    • task status, provider, model, latency.
  • Support both Noetica standalone completion events and SourceOS unavailable/blocked events.

Boundary rules

  • AgentTerm renders and records interaction events; it does not become the cognition loop.
  • AgentTerm may tail Noetica/Superconscious/AgentPlane traces, but those planes retain their authority boundaries.
  • High-risk terminal, Matrix, slash-command, shell, tool, and handoff actions still require Policy Fabric decisions and Agent Registry grants before dispatch.
  • No raw secrets, unrestricted shell output, unrestricted browser history, credentials, or private chain-of-thought may be rendered or stored from payload.
  • OpsHistory remains the local-first operational ledger; SourceOSInteractionEvent is the noetic/chat/task projection.

Acceptance criteria

  • Add fixture copied or adapted from examples/sourceos-interaction-event.json.
  • Add command or dry-run helper that renders the fixture governance trace.
  • Add tests for conversion/rendering without live Matrix, provider, or Superconscious dependencies.
  • Existing ruff check . and pytest pass.
  • Docs clarify that Noetica and AgentTerm are separate surfaces over the same contract.

Related

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions