Use SourceOS State Integrity for local-first memory durability and provenance

[mdheller]

Purpose

Memory Mesh should consume SourceOS State Integrity as the durable local-first substrate for memory facts, invalidations, provenance, profile boundaries, and policy-governed replication.

Canonical spec: SourceOS-Linux/sourceos-spec/docs/architecture/sourceos-state-integrity-layer.md
Program tracker: SourceOS-Linux/sourceos-spec#83

Memory object requirements

• append-only memory event log
• fact provenance
• source actor
• confidence score
• expiry / invalidation
• privacy class
• profile id
• workspace id
• organization visibility
• human override
• policy decision trail

Requirements

• Memory writes must be attributed to registered actors.
• Memory promotion must be policy-gated.
• Memory replication must respect profile and workspace boundaries.
• Invalidations must be explicit objects/events, not silent deletes.
• Repair must preserve durable memory history and rebuild projections/indexes.

Acceptance criteria

• Memory Mesh defines State Integrity-backed memory fact and invalidation schemas.
• Memory facts include actor, source, confidence, profile, workspace, and policy metadata.
• Memory indexing/projections are classified as rebuildable, not durable source of truth.