Bind Memory Mesh context-pack and memory refs into SourceOSInteractionEvent runtime bridge

[mdheller]

Mission

Define how Memory Mesh context-pack and durable memory references should attach to Noetica-emitted SourceOSInteractionEvent records without moving memory authority into Noetica or AgentTerm.

Current state

The SourceOS interaction runtime bridge is now bounded and artifact-based:

• SocioProphet/Noetica#47: ADR selected bounded artifact/export first.
• SocioProphet/Noetica#48: event builders and artifact export landed.
• SourceOS-Linux/agent-term#50: opt-in AgentTerm import landed.
• SourceOS-Linux/sourceos-spec#123: runtime bridge ledger landed.

Current event payloads include governanceTrace.memoryScopeRef, memoryWritten, and contextPackRefs, but the concrete Memory Mesh binding is not yet defined.

Required work

1. Define canonical Memory Mesh refs for memory scope, context packs, and durable memory writes.
2. Define when memoryWritten may be true and which plane owns the durable write record.
3. Define standalone, SourceOS, and replay-mode assumptions.
4. Provide at least one fixture showing a Noetica interaction event with Memory Mesh-backed refs.
5. Document non-goals, redaction, retention, and authority boundaries.

Boundary rules

• Do not move durable memory authority into Noetica.
• Do not make AgentTerm a memory authority.
• Do not require live Noetica runtime integration in this issue.
• Do not store raw transcripts, private reasoning, raw shell output, browser history, secrets, credentials, unrestricted provider payloads, or raw execution logs.

Acceptance criteria

• Memory scope, context-pack, memory-write, retention, and redaction semantics are documented.
• Fixture or example demonstrates the binding.
• Noetica and sourceos-spec can reference the binding without owning durable memory authority.
• Existing validation remains green.