Skip to content

Document SourceOS interaction reference flow pointer #254

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
mdheller merged 1 commit into from
May 31, 2026
Merged

Document SourceOS interaction reference flow pointer #254

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
28 changes: 28 additions & 0 deletions docs/integration/sourceos-interaction-reference-flow.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,28 @@
# SourceOS Interaction Reference Flow

Status: downstream reference pointer
Canonical packet: `SourceOS-Linux/sourceos-spec#118`
Canonical manifest: `examples/interaction-flow/noetica-superconscious-agentplane-agentterm.flow.json`

## AgentPlane role

AgentPlane records the evidence and replay references for the SourceOS interaction substrate.

The canonical reference flow is:

```text
Noetica creates SourceOSInteractionEvent
-> Superconscious records task-boundary refs
-> AgentPlane records evidence refs
-> AgentTerm displays the governance trace
```

## Local references

- Evidence binding doc: `docs/integration/sourceos-interaction-evidence-binding.md`
- Evidence binding schema: `schemas/integration/sourceos-interaction-evidence-binding.v0.1.schema.json`
- Evidence binding check: `python tools/validate_sourceos_interaction_evidence_binding.py`

## Boundary

AgentPlane owns evidence and replay references. The schema remains owned by `SourceOS-Linux/sourceos-spec`; task coordination, display surfaces, policy decisions, identity grants, and memory context remain in their respective planes.
Loading