Add SourceOS interaction substrate for Noetica and AgentTerm#106
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adds a shared SourceOS interaction substrate so Noetica and AgentTerm become different surfaces over the same governed task/event/governance contract rather than parallel bespoke chat surfaces.
This tranche adds:
schemas/SourceOSInteractionEvent.jsonexamples/sourceos-interaction-event.jsondocs/contract-additions/sourceos-interaction-substrate.mdtools/validate_sourceos_interaction_examples.pySourceOS Interaction SubstrateCI workflowContract posture
OpsHistoryEventremains the local-first operational event ledger.SourceOSInteractionEventis the noetic/chat/task projection that can be embedded in, referenced by, or derived from OpsHistory.Noetica owns browser chat, model-selection, steering UX, and inline governance trail. AgentTerm owns terminal-native / Matrix-first operator flow, approvals, event tailing, and trace rendering. Neither surface owns model routing, memory durability, tool grants, policy admission, or execution evidence.
Validation
Local schema check was performed before commit with
jsonschema.Draft202012Validator.check_schemaand example validation againstschemas/SourceOSInteractionEvent.json.Dedicated CI added:
Downstream follow-up
After merge:
Notes
Catalog README update is intentionally deferred to the next small PR if this contract shape is accepted, to avoid mixing discovery/catalog churn with the first substrate contract review.