Add local-first orchestration event ledger and device graph sync slice

[mdheller]

Context

The smartphone/home orchestration benchmark is moving toward AI camera understanding, natural-language routines, web control, and cross-device automation. SourceOS should treat this as local-first OS infrastructure, not as a cloud-only integration.

Parent planning spec: SocioProphet/prophet-platform/docs/strategy/sovereign-device-orchestration.md.

Scope

Implement the local-first side of sovereign device orchestration: device graph objects, event receipts, durable local queueing, replay protection, repair/reconciliation, and sync-ready provenance records.

Acceptance criteria

• Define internal models for device nodes, adapter state, orchestration events, policy decisions, and sync receipts.
• Add fixture ingestion for a small home/device graph without requiring proprietary cloud credentials.
• Persist events in a durable local queue suitable for offline capture and later reconciliation.
• Include replay/idempotency semantics for repeated adapter events.
• Include repair/reconciliation tests for disconnected and reconnected operation.
• Produce receipt objects compatible with Prophet Platform/Fog evidence ingestion.

Safety boundaries

• No direct high-risk actuation in this issue.
• No raw camera-video storage.
• No storage of proprietary ecosystem credentials in repo fixtures or logs.

Demo target

Fixture adapter emits camera/sensor/routine events -> sourceos-syncd records receipts -> sync/export path produces evidence bundle for Prophet Platform.

[mdheller]

First local-first orchestration fixture slice is now on main:

• examples/orchestration/home-assistant-demo.bundle.json
• tools/validate_orchestration_examples.py

The fixture mirrors the Prophet Platform canonical contract into SourceOS vocabulary and validates adapter ids, node ids, event ids, receipt ids, cross-object references, privacy metadata, trust/revocation state, policy outcomes, and receipt lineage.

Validation target:

python3 tools/validate_orchestration_examples.py

Next step: promote the fixture into durable queue/replay semantics and connect it with the existing control-plane example validator/CI gate.