Define SourceOS State Integrity implementation program and sourceos-syncd repo cut

[mdheller]

Purpose

Turn the SourceOS State Integrity architecture into an executable implementation program.

Canonical spec: docs/architecture/sourceos-state-integrity-layer.md

Required outcomes

• Decide whether to create SourceOS-Linux/sourceos-syncd as the implementation home.
• Define the MVP cut as a concrete milestone.
• Lock the first object model, actor model, schema model, sync plan model, and repair report model.
• Define repo ownership across boot, devtools, workspace, agent plane, policy, memory, cloud/fog shell, terminal, observability, and model artifact lanes.

MVP scope

• local object registry
• actor registry
• schema registry
• append-only local event log
• status and doctor CLI
• one file/workspace object adapter
• one agent actor path
• one policy decision hook
• one conflict type
• one repair path for derived index corruption
• structured observability events
• basic SourceOS Workspace and TurtleTerm status surfaces

Acceptance criteria

The program is ready to implement when the MVP can answer from structured state:

• What is this object?
• Which schema governs it?
• Who or what last changed it?
• Which device and profile own it?
• Is it safe to sync?
• Why is it blocked?
• What conflicts exist?
• What can be repaired automatically?
• What requires human review?
• What data is durable vs rebuildable?
• Can we prove restore integrity?

Integration targets

• SourceOS-Linux/sourceos-boot
• SourceOS-Linux/sourceos-devtools
• SourceOS-Linux/sourceos-shell
• SourceOS-Linux/TurtleTerm
• SocioProphet/sourceos-workspace
• SocioProphet/sociosphere
• SocioProphet/cloudshell-fog
• SocioProphet/agentplane
• SocioProphet/agent-registry
• SourceOS-Linux/agent-machine
• SourceOS-Linux/agent-term
• SocioProphet/policy-fabric
• SocioProphet/guardrail-fabric
• SocioProphet/memory-mesh
• SocioProphet/sherlock
• SocioProphet/holmes
• SocioProphet/lampstand
• SourceOS-Linux/sourceos-model-carry
• SocioProphet/model-router
• SocioProphet/hermes-agent

Notes

This is not commodity file sync. This is the SourceOS local-first state integrity layer: provenance, repair, profile isolation, policy-governed replication, and agent-operable state.

[mdheller]

Implementation update from SourceOS-Linux/sourceos-syncd:

The repo already contains a Python implementation lane for State Integrity Report generation, diagnosis, verification, and repair planning. We should preserve that lane as the current MVP baseline instead of introducing a split Rust implementation prematurely.

Current executable contract:

sourceos-syncd health snapshot
sourceos-syncd health snapshot --compact
sourceos-syncd health explain --file examples/health/healthy.snapshot.json
sourceos-syncd health verify --file examples/health/healthy.snapshot.json
sourceos-syncd repair plan --file examples/health/degraded.snapshot.json

Work completed in sourceos-syncd:

• aligned docs/contracts.md to the Python implementation and current CLI
• added contract tests for State Integrity Reports and repair plans
• opened MVP issues for persistence, model contracts, and service endpoints:
  • MVP: add local state directory, append-only event log, and registry persistence sourceos-syncd#10
  • MVP: add actor, schema, object, policy, and conflict contract models to Python implementation sourceos-syncd#11
  • MVP: serviceize health, readiness, state, events, metrics, and repair planning endpoints sourceos-syncd#12

Correct sequencing now:

1. keep Python report/repair pipeline as MVP baseline
2. add local state directory + append-only event log + registries
3. add Python actor/schema/object/policy/conflict models
4. serviceize local-only endpoints after persistence contracts are stable
5. only consider Rust/Go later if runtime constraints justify migration