[DM-083] Fast Forward to real two-host CompAII dogfood

[nicoechaniz]

Outcome

Fast Forward from synthetic acceptance to one real, reversible CompAII dogfood session across the existing Legion and daimonmatrix host embodiments of the same being. Install the exact same released daimon-matrix artifact on both, exercise the actual owner-facing /me and /we experience, exchange one inert typed human message over the existing Tribe v1 encrypted direct path while Matrix carries /me and /we, navigate/synchronize one difference, make one observer-local adoption and reversal, restart one side, and record the friction that a human actually encounters.

This is an experience-learning vertical slice, not a production rollout or a substitute for later cross-being DM-016 consent. Batch every directly enabling code, configuration, runbook, observability and rollback change needed for the session into one delivery sequence instead of splitting tightly coupled internal details into separate cards.

Blocked by

• DM-081 is merged and its release artifact/CI evidence is green.
• The operator explicitly authorizes the bounded host changes and test window.

Dependency note

DM-082 is not a dependency because both participants are embodiments of one existing being. It remains the next gate for relationships, grants and source exchange between distinct beings.

Fast Forward rule

Compress ceremony, not evidence. Include a change when it directly makes the real session possible, observable, safe or reversible. Defer polish and generalization that do not block the session. Do not defer authority checks, secret isolation, state compatibility, rollback, encrypted transport, origin attribution or effect truth.

Preflight without effects

• identify the exact current manifests, embodiment/incarnation IDs, Matrix/Cluster commits, artifact hashes and service configurations on both hosts;
• verify separate custody, writable ledgers, CAS/state volumes, sockets, peer journals and runtime capability keys;
• verify backup/quiesce and rollback commands against exact paths without copying private keys or writable databases between embodiments;
• verify the direct peer route, expected principals, ports and resource fences from configuration without sending a semantic message;
• produce a bounded change plan naming every service/package/config effect and the stop condition.

Real dogfood session

1. Deploy the same commit-bound wheel and compatible bundle to both embodiments under the existing Cluster hosting boundary.
2. Start both daemons and prove each reports its own origin while sharing the same being root and current manifest.
3. From the ordinary user-facing client, inspect /me and /we; responses must be understandable, origin-marked and useful without reading raw databases or fixtures.
4. Send one small inert typed human message through the existing Tribe v1 encrypted direct path. Record its duplicate-gate and delivery evidence separately; do not report a Tribe ACK as Matrix recipient intake or semantic delivery.
5. Create one harmless canonical novelty, inspect /we.diff, freeze/execute the exact /we.sync plan, and verify additive convergence without copying state.
6. Adopt the novelty on one observer only, confirm the other observer remains unchanged, then author and verify the reversal.
7. Restart one embodiment, prove the next authorized incarnation resumes cursors/journals without duplicate message, event, receipt or projection effects.
8. Exercise the exact rollback/stop path and confirm canonical evidence remains while test-only runtime/config effects are removed or disabled.
9. Capture UX observations: commands attempted, confusing terms, missing affordances, latency, error quality, manual steps and unsafe temptations. Store no secrets, plaintext private content, endpoints or private paths in public evidence.

Acceptance

• both real embodiments remain independently awake with disjoint custody and writable state;
• /me and /we are usable through supported client surfaces and preserve origin;
• one encrypted Tribe v1 typed message passes its own duplicate gate and delivery evidence exactly once, without claiming Matrix semantic delivery;
• one difference is navigated and synchronized, then adopted locally and reversed without global policy collapse;
• restart/retry is duplicate-free and stale writers/resource holders are rejected only at their exact scope;
• rollback is executed or dry-run verified at the exact effect boundary;
• a redacted commit-bound receipt and a concise UX findings report identify what to change in the next Fast Forward batch;
• no Matrix.org, Tribe v0 fallback, shared writable database, private-key transfer, live model call, unrelated provider effect or second-being relationship is introduced.

Human gate

Do not install packages, restart services, alter routes/configuration, send the message, mutate Cluster resources or contact a remote host until the operator approves the exact preflight plan. Read-only local repository work and preparation may proceed before that approval.

Deployment: live but bounded and reversible on the operator-controlled Legion and daimonmatrix host embodiments after explicit approval.

[nicoechaniz]

/claim

[github-actions]

[nicoechaniz]

/claim

[github-actions]