[DM-076] Prepare and freeze the V0.1.0 release candidate

[nicoechaniz]

Outcome

Prepare, merge and freeze the complete v0.1.0 release candidate before the independent DM-073 audit. This card owns every repository mutation needed to make a commit releasable: final version/build metadata, closure/evidence manifests, changelog and release notes, compatibility/migration policy, SBOM/license/provenance inputs, packaged documentation and the deterministic artifact-verification path.

The observable result is an exact commit already on the protected default branch from which all proposed release bytes reproduce. DM-073 reviews that commit and those bytes. DM-076 does not create a release tag, publish assets or authorize deployment.

This split is required by the one-issue/one-claim/one-PR protocol: candidate preparation must close before security review, while DM-075 remains the later publication ceremony.

Blocked by

DM-055, DM-061, DM-071, and DM-074.

Those direct gates transitively require the remaining V0 implementation, Matrix↔Cluster, canary, Tribe cutover, harness and documentation work. At claim time audit every release-candidate roadmap/Kanban issue anyway; later publication and source-archive operations remain explicitly sequenced open, while a missing or deferred required V0 behavior fails closed even if it was not represented by a dependency edge.

Allowed scope

• Final package/version/build configuration, bounded dependency locks and public CI release-candidate jobs.
• Checked-in release/evidence manifests, schema/domain/ID/API registries, compatibility tables, changelog/release notes, operator/developer docs and generated public metadata.
• Deterministic offline artifact builder/inspector, install smoke, SBOM/license/provenance generation inputs and verification fixtures.
• Status/navigation documents needed to describe the exact candidate.

No new identity, ledger, crypto, messaging, memory, species, adapter, Cluster, canary or migration behavior belongs here. A discovered implementation gap reopens its owning focused issue and keeps DM-076 blocked.

V0 closure audit

Create a machine-readable and rendered closure matrix for every release-candidate V0 DM card, plus explicit sequenced-open entries for the later publication and source-archive cards, containing:

• issue, signed claim/receipt, PR, merge SHA and exact independent review verdict/head;
• acceptance-criterion evidence and canonical spec/schema/vector/test/runbook/doc paths/digests;
• required scenario result, exact command/count/platform and any skips/limitations;
• security/canary/cutover/recovery evidence and residual-risk owner;
• final disposition proving no required release-candidate behavior was deferred and later external operations are dependency-sequenced rather than waived.

Reconcile ROADMAP.md, ISSUES.md, Project 9 and live GitHub issue states. Add DM-076 and the corrected order DM-074 -> DM-076 -> DM-073 -> DM-075. No missing, duplicate, stale-minimal, contradictory or unowned required card may remain.

Candidate content

• Version is exactly 0.1.0; intended tag is exactly v0.1.0.
• Freeze every public V0 media type/domain/tag, typed ID prefix, schema $id, signature/preimage domain, CLI/MCP method, exit/error/receipt status and DM-018 adapter contract in a generated registry checked against source.
• State the V0 compatibility policy: accepted V0 bytes are immutable; additive code cannot reinterpret them; unknown versions/features and unauthorized downgrades fail closed; incompatible changes require a new version/domain plus receipt-bound migration.
• Publish supported Python/runtime/OS/database/crypto/build-tool ranges and exact lock digest.
• Publish exact tested Matrix↔Cluster combinations and required genuine signer/CAS/fence/dual-gate behavior; deployment evidence grants no Matrix authority.
• Publish DM-074 harness evidence levels and pinned tested versions; vendor docs alone are never live support.
• Finalize changelog/release notes, install/verify/configure/operate/backup/restore/disable/uninstall docs and empty-start/Tribe non-import policy.

Release-candidate manifest

Check in a closed, content-addressed daimon-matrix-release-manifest/v0 binding:

• repository, exact source commit/tree (filled with or deterministically verified against the merge candidate), version/tag intent and clean-tree assertion;
• declared artifact filenames, sizes and digests produced from the exact merged commit;
• build environment, fixed epoch, dependency lock, SBOM, license inventory/notices, CI/action pins, provenance/attestation subjects and artifact/member allowlists;
• closure matrix, required-scenario report, canary/cutover/recovery evidence and public residual-risk register inputs;
• Matrix↔Cluster and harness compatibility tables;
• secret/private-state scan policy and redacted deployment/config-template digests;
• instructions for DM-073 to independently rebuild and for DM-075 to verify/tag/publish without changing candidate bytes.

If embedding the final commit hash in a file would create a self-reference, bind the Git tree hash plus externally generated signed candidate statement; never insert a guessed SHA or mutate the tree after audit.

Reproducible artifacts and installed verification

• Build sdist, wheel and every supported optional bundle twice from independent clean exports of the exact default-branch candidate, with fixed environment/network policy. Required reproducible formats are byte-identical and SHA-256-equal.
• Inspect archive paths, modes, symlinks, timestamps and content allowlists. Reject traversal, absolute paths, caches, VCS/build state, databases, keys, credentials, messages, memory, endpoints and experimental modules.
• Install only the wheel into a fresh environment/state root and run CLI/MCP version/self-check plus the complete required synthetic/contract suite.
• Run artifact/package/log/report secret scans, adapter-disablement checks, ledger/CAS reconstruction and encrypted-backup restore with the candidate package.
• Generate SBOM/license/provenance subjects deterministically or document the content-addressed external attestation step that DM-075 will perform without changing artifacts.
• Treat GitHub-generated source archives as unreviewed convenience outputs, not canonical reviewed release assets.

Candidate merge and freeze

The single DM-076 PR contains all candidate-affecting changes and Closes this issue. It receives its normal independent component review, merges, and then the exact resulting default-branch commit/tree becomes the DM-073 candidate. Rebuild all declared artifacts from that merged commit and record public digests in the DM-073 handoff/evidence manifest.

After freeze:

• no code/schema/dependency/build/config/fixture/doc/release-metadata change may land on the candidate;
• DM-073 REQUEST_CHANGES sends fixes to focused issues/PRs, after which DM-076 evidence is regenerated or a scoped successor preparation card is opened and the candidate refreezes;
• only exact-head DM-073 APPROVE plus human same-candidate GO lets DM-075 publish;
• branch protection, CI retention or an external draft release is not an authority substitute.

Acceptance criteria

• Every required release-candidate V0 card/criterion is closed with exact implementation/review/evidence; none is deferred to ship, while later publication/source-archive cards remain explicitly blocked in their intended order.
• Project/docs dependency graph includes DM-076 and has no final-audit/release cycle.
• Final version, registries, compatibility/migration policies, Matrix↔Cluster/harness matrices, changelog and release docs are present before audit.
• Candidate manifest closes over the exact merged tree and proposed artifact/evidence set without self-referential or mutable inputs.
• Two clean builds reproduce; artifact-only install, full suite, secret scan, adapter-disablement and both recovery drills succeed.
• SBOM/license/provenance inputs and artifact/member allowlists are complete and independently checkable.
• A single reviewed PR merges all preparation changes and hands DM-073 the exact default-branch candidate SHA/tree and digests.
• No tag, GitHub release, asset publication, live deployment or human GO is performed by this card.

Security and rollback

• Use synthetic/public inputs and validated disposable roots. No live keys, tokens, databases, messages, memories, participant data, endpoints or private config enter builds/reports.
• Release/signing credentials remain absent; CI uses read-only permissions and no publishing token.
• A failed build/audit leaves the commit unreleased. Corrections are forward commits under focused claims; never rewrite canonical state, force a tag or hide a finding.
• Preserve failing artifact/evidence digests for review while removing only validated disposable local roots.

Deployment: N/A. This card prepares bytes; it neither publishes nor deploys them.

Canonical references

• PLAN.md
• ONTOLOGY.md
• ROADMAP.md
• ISSUES.md
• TRIBE-MIGRATION.md
• DM-073 security gate, DM-074 harness guide/fixtures, DM-075 publication ceremony and DM-077 post-release Tribe source archive.

Concurrent-work gate

Do not claim until every named blocker is closed, the live V0 closure audit finds no required open candidate behavior (later publication/source-archive operations excepted), and active claims/worktrees show no candidate-affecting overlap. The claim owns the release-preparation files and protocol registry paths explicitly; it does not own implementation fixes or external publication.

Expected PR

One PR closes DM-076 and produces the already-merged exact candidate consumed by DM-073. DM-075 later creates the tag/release and a separate postflight record; it must not alter this candidate.

[nicoechaniz]

Roadmap correction (2026-08-04): Matrix.org alone is excluded; the daimon-matrix runtime is part of the V0.1 MVP. DM-078 (#76), the root-authorized fresh-host rebirth gate, is therefore a required release-candidate blocker in addition to the blockers already listed. The next DM-076 body refresh must include it in the closure manifest and dependency audit.

[nicoechaniz]

V0.1 candidate preflight snapshot — 2026-08-11

DM-076 remains correctly unclaimable. Current evidence distinguishes completed technical implementation from missing independent authority/review:

Exact implementation heads

• DM-083: PR Prepare DM-083 real two-host dogfood #112 at e45ff577e0594065eb26440caa80cf5377eadb86; exact deployed runtime code 915c56c8899fd53d683bd7c7c81c3465b600bed9; CI green; zero reviews.
• DM-074: PR DM-074: add harness adoption guide and conformance corpus #114 at e0b06b9a9385fb231515841d644e8782d130c1f4; CI green; zero reviews.
• DM-036 Matrix side: draft PR Integrate DM-036 collective-memory adapters #115 at ba1a52df22d74abb70922fbeacec46ef5ea38ee4; all technical jobs green and its coordination job intentionally refuses the blocked/unclaimed draft; zero reviews.
• DM-036 upstream: Add provenance-safe export and reviewed publication boundary Mar-IA-no/collective-memory#3 at 3e3b39416917f8e3c2bc5ca69362b20296205938, mergeable, zero reviews/checks.
• Combined non-claiming integration branch: dm074-dm083-dm036-integration at 17e82371de66da2fc2dc9644aadcdba1e34643cf. It passed strict static gates, all generators byte-exact, 576 source tests (19 skipped), two byte-identical installed conformance runs and reproducible package hashes. It deliberately has no PR and cannot replace the separately owned reviews/merges.
• Cluster host stack: PRs docs: refresh status after DM-014 #63, [DM-018] Freeze adapter contracts and Matrix-Cluster profile #70–Restore plural embodiment ontology and define dm.we.v1 #75, docs: restore daimon-matrix runtime to MVP #77 and integration PR [DM-021] Implement plural being root and secure custody #78 are mergeable with green technical checks and zero reviews. Exact host-qualified deployed pair remains Cluster 94d80baca05f468287b7d2bf99c577350d654a36 / Matrix 915c56c8899fd53d683bd7c7c81c3465b600bed9.
• Transitional Tribe client fix: Honor explicit Tribe client environments in Hermes nicoechaniz/tribe-bridge#61 at c034b40e45b12cb3995065bd84a556ca0225a795, mergeable/green, zero reviews.

Unsatisfied release-candidate gates

1. Independent exact-head reviews and merges for the implementation/upstream/host stacks above.
2. DM-071 consent from a genuinely distinct being plus native Matrix intake and signed semantic receipt; Tribe ACK evidence is not a substitute.
3. DM-055 explicit human cutover approval; technical two-host canary, rollback, backup and cold reboot evidence is complete but grants no cutover authority.
4. DM-078 fresh-host rebirth with new root-authorized embodiment custody and independently held recovery material.
5. Cluster external operations: pilot volunteer/provider credentials ([DM-015] Specify /source ancestry claims and quarantine #13), second independent off-host target ([DM-021] Implement daimon-matrix being root, plural embodiment credentials, and secure keystore #15), restore drill against it ([DM-025] Implement the daimon CLI and minimal MCP surface #16), governance approval ([DM-050] Freeze Tribe Bridge provenance and absorption boundary #31), two consenting cohort owners ([DM-052] Implement typed messages, threads, fan-out, receipts, and stable cursors #32), and named-human launch/go-no-go ([DM-051] Replace public-roster group encryption with recipient encryption #33).
6. DM-073 independent adversarial review, then DM-075 same-candidate human GO and publication.
7. DM-077 exact-target owner approval after release/cutover; no Tribe archive is authorized now.

Transitional carrier deadline

The earliest live Tribe v1 keys expire 2026-08-30 07:13:52 UTC, earlier than the original September-1 shorthand and before the epoch-5 directory expiry. The audited/proven staged-rotation proposal is at nicoechaniz/tribe-bridge#59 (comment) and is now tracked on AlterMundi Project 8 as Todo / agent state Blocked. It still requires cross-agent governance review and self-custody participation; no live key or directory change occurred.

Current read-only runtime audit: Legion Matrix and Tribe services are active with zero restarts; daimonmatrix Cluster, Matrix and Tribe services are active with zero restarts; Cluster public health reports ok with its audit chain valid, and both Tribe endpoints report identical build d49bf227083b0d10a63d5f7babe6a890354d9866, directory epoch 5 and directory hash c21b3221424340e931e588594bf194ddfe7170d1aeee848aab049bbe8e02ce88.

Therefore no DM-076 claim, default-branch freeze, tag, release, deployment advance, consent inference or archive mutation is valid yet. This snapshot is gap evidence, not a waiver of any closure-matrix row.

[nicoechaniz]

V0 closure checkpoint (2026-08-11), without claiming DM-076 or freezing mutable inputs:

• DM-083 Matrix e45ff577e0594065eb26440caa80cf5377eadb86, DM-074 e0b06b9a9385fb231515841d644e8782d130c1f4, DM-078 0a5fd3383aeb391488888d397a3d3296a71f98db, Cluster H1-H9 and Tribe PR [DM-014] Specify species evolution and speciation #61 are green and now have formal independent review requests assigned to compaii.
• Distributed DM-078/H9 physical-host evidence is complete; no live fresh-being authority transition was performed.
• DM-036 Matrix candidate ba1a52df22d74abb70922fbeacec46ef5ea38ee4 passes 566 tests/19 skips but remains correctly blocked on upstream Mar-IA-no/collective-memory#3 exact head 3e3b39416917f8e3c2bc5ca69362b20296205938; maintainer workflow approval/review was re-requested.
• DM-055 still needs an exact receipt-bound human cutover GO; DM-071 still needs one named participant's prior operational consent plus its independently signed protocol consent. Neither is inferred from repository access or this checkpoint.
• Tribe zero-SSH provisioning remains gated on Oliva's owner-run round-trip and maintainer scope confirmation. Key-rotation issue Refresh Wave 1 readiness after DM-013 #59 now contains a concrete two-phase self-custody/overlap/forward-recovery design and an explicit cross-agent review request.

Therefore DM-076 remains unclaimed as required. Once reviews/consent and live GO gates close, the next mutation is the single default-branch candidate-preparation PR; no tag/release action is authorized by this checkpoint.

[nicoechaniz]

Matrix RC boundary is now proposed in PR #121 on exact commit 572b321dfb3bd48d52e250e3ebb137f6b853d94a (tree d7146e291ae3f8313dc0b3d3c3a0b5e5f94d33ad). Independent exact-head review passed after correcting output-path race and published-schema coverage findings. Local clean evidence: 640 tests / 22 declared skips, static and generator gates green, two byte-identical offline builds; wheel a8433cb007b46d45593895d0e459828a7281f09eb89cb85f558f8eabc9bc5e83, sdist f1fa00e3c5d18cb7ecce44ae656938ff35daeedb22e713cdc53b916208a6befe.

PR CI is running. This does not close DM-076: Cluster must be repinned to the eventual Matrix merge, Tribe metadata must then be reconciled and independently approved, and the integrated artifact/installation/E2E receipt is still pending. Physical hosts, real custody, consent, contact, publication and cutover remain explicit external gates; none was exercised.

[nicoechaniz]

Integrated RC checkpoint:

• Matrix is merged and green at 09414d6edd9586f539be8272c4979d0b36c86b87 (tree d7146e291ae3f8313dc0b3d3c3a0b5e5f94d33ad), with 640 tests / 22 skips across Python 3.11–3.14.
• Cluster is merged and green at 820e3792a227b1848681a3421b113e8822c8d08a (tree 4f62eb4f6eff1dfafbd477339a86fa7d5e70a5d8), with 595 passed / 4 skipped and both disposable E2E jobs green.
• Tribe PR Refresh Wave 1 readiness after DM-015 #65 exact head f84fbd98dfea48fd4212f13c69f36380f2e0453d passed independent review and CI on Python 3.10–3.13; protected merge now waits only for fresh human GitHub approval.
• A Linux x86_64 wheelhouse with 38 exact dependency wheels plus the reproducible Matrix wheel/sdist was installed successfully with empty caches and no index on Python 3.11, 3.12, 3.13 and 3.14.
• The integrated freezer accepted the exact pre-approval candidate; its current provisional manifest SHA-256 is b03e9033d10a7b9bf9c673613db38797574304201ebae844b6ec97c8c576bbaa.

DM-076 stays open until Tribe merges, the final manifest is regenerated against that merge commit, authoritative docs are reconciled and final tracking is closed. Physical hosts, live custody, cross-being consent and publication remain separate human gates.

[nicoechaniz]

Integrated RC checkpoint successor:

• Matrix remains merged and green at 09414d6edd9586f539be8272c4979d0b36c86b87 (tree d7146e291ae3f8313dc0b3d3c3a0b5e5f94d33ad).
• Cluster remains merged and green at 820e3792a227b1848681a3421b113e8822c8d08a (tree 4f62eb4f6eff1dfafbd477339a86fa7d5e70a5d8).
• Tribe issue docs: refresh status after DM-015 #66 exposed a real delivery/retry gap. Its successor fix is included in PR Refresh Wave 1 readiness after DM-015 #65 at exact head 42d637245864fcd431198a570d19d7a6dd042924 (tree 5145f6446f3ec3013347509477a262f98825ebfa), with independent adversarial PASS, 124 tests on Python 3.10–3.13 and all remote checks green.

The earlier provisional integrated-manifest digest is superseded. DM-076 remains open until the protected Tribe merge, regeneration from the resulting exact main commit, authoritative documentation reconciliation and final integrated qualification. No host, live custody, contact, deployment, publication or cutover action is authorized by this checkpoint.

[nicoechaniz]

Pre-merge freezer proof updated against Tribe successor 42d637245864fcd431198a570d19d7a6dd042924:

• the canonical manifest was generated twice from clean Matrix 09414d6, Cluster 820e3792 and Tribe 42d63724 worktrees and was byte-identical;
• provisional manifest SHA-256: d3ac479d4ff581e0f1dfb82a1a41f15d25ad3e45eb03723065e865d037cc8fd5;
• exact Matrix offline artifacts were rebuilt twice with the repository-declared epoch: wheel 5896ae31813b7b9e1224ada14b7f9da9745790404c5a1eee9043079572f20089, sdist f0ba76eb6650647a8b808f8648d04ef6d35806fcafd2f271d140c4fa5f9e96a1;
• the Linux x86_64 Python 3.11–3.14 dependency wheelhouse and Tribe qualified source archive are included by exact size/hash.

This is method/evidence qualification only. It is intentionally provisional and will be regenerated after Tribe's protected merge and the final documentation/pin successors. No publication, deployment or external operation occurred.

[nicoechaniz]

Prepared downstream closure while Tribe approval is pending:

• Matrix documentation reconciliation is committed locally at exact 8262e1ee5ab2f0b1a389a911b206cac94b823618 (tree 8daf4c99192a8f797d60f36f049a832761304082) and received independent PASS. It corrects current boundaries, test counts and the reproducible artifact hashes without claiming final integration.
• Cluster exact-pin/documentation successor is committed locally at 8c2dab4157384e9f0d803275d00f7deb1ef2b022 (tree e0f6cc21abbbddac457d434fd3455316ead1e2af) and received independent PASS. Requirements, runtime, tests and workflow all bind Matrix 8262e1; the strict full suite passed 595/4 and the network-disabled recovery container passed with that image commit.
• A Tribe metadata successor is staged locally at 73c2d81899313f9f18b6e072976d1cfa933494ad (tree 16c05a50737a26fa4d6edb1c1908e06e45b12a7e) but is intentionally not published or used to rewrite PR Refresh Wave 1 readiness after DM-015 #65. It will be finalized only after the protected upstream merges, so its receipt can describe merged facts rather than candidates.

This minimizes the post-approval critical path without bypassing claims, reviews or branch protection. No deployment, host, access, custody, contact or publication action occurred.