Objective
Integrate Memory Mesh with the SourceOS/SociOS governed local-first agentic graph foundation.
Memory Mesh must treat durable memory as governed graph state, not ordinary settings.
Required lifecycle
observed -> proposed -> scoped -> approved -> promoted -> synced -> expired/revoked
Required memory fields
- memory ID
- origin
- author
- source agent/user/surface
- confidence
- scope
- sensitivity
- retention
- mutability
- policy class
- policy decision pointer
- audit pointer
- revocation state
Required work
- Define
MemoryObject fixture examples for proposed, scoped, promoted, quarantined, expired, and revoked memory.
- Define memory provenance shape.
- Define memory quarantine behavior.
- Define review requirements for global or cross-profile promotion.
- Add audit events for proposal, approval, promotion, quarantine, expiry, and revocation.
- Add
.sourceos/manifest.json declaring owned schemas, sync engine, policy classes, dangerous surfaces, and audit events.
Critical rule
Agents may propose memory. They may not silently globalize memory or mutate durable cross-device memory without policy and review.
Dangerous surfaces
- memory.promote
- memory.globalize
- memory.cross_profile_sync
- memory.rewrite
- memory.revoke
- memory.agent_proposed
Acceptance criteria
- Memory lifecycle is fixture-backed.
- Memory promotion requires policy decision and audit pointer.
- Untrusted memory writes are quarantined.
.sourceos/manifest.json validates against the sourceos-spec manifest contract once available.
Related
Objective
Integrate Memory Mesh with the SourceOS/SociOS governed local-first agentic graph foundation.
Memory Mesh must treat durable memory as governed graph state, not ordinary settings.
Required lifecycle
observed -> proposed -> scoped -> approved -> promoted -> synced -> expired/revokedRequired memory fields
Required work
MemoryObjectfixture examples for proposed, scoped, promoted, quarantined, expired, and revoked memory..sourceos/manifest.jsondeclaring owned schemas, sync engine, policy classes, dangerous surfaces, and audit events.Critical rule
Agents may propose memory. They may not silently globalize memory or mutate durable cross-device memory without policy and review.
Dangerous surfaces
Acceptance criteria
.sourceos/manifest.jsonvalidates against the sourceos-spec manifest contract once available.Related