[DM-077] Publish the final Tribe notice and archive the source repository

[nicoechaniz]

Outcome

After Daimon Matrix v0.1.0 is publicly published and the DM-055 runtime cutover remains healthy, publish the final Tribe Bridge historical notice/tag/source-only release and—with explicit repository-owner approval—set exactly nicoechaniz/tribe-bridge to GitHub archived/read-only state. Preserve public source provenance, refs, authorship, issues and releases without importing any Tribe history/state into Matrix.

Archiving is an irreversible external repository mutation for this workflow. It is not deletion, transfer, rename, privatization, history rewriting, branch cleanup, license invention or evidence of runtime-data destruction.

Blocked by

DM-055 and DM-075.

DM-055 supplies the completed no-history runtime cutover and content-addressed archive handoff. DM-075 supplies the immutable public Matrix release URL/tag/signature/assets/postflight that the final Tribe notice must name. Keep status:blocked, needs-human and risk:migration until both close and the owner approves the exact archive target/preflight.

Fresh preflight

Re-run and bind:

• exact nicoechaniz/tribe-bridge visibility, isArchived, default branch/head, all refs/tags/releases/assets, license declaration, open issues/PRs, branch protection and owner/admin authority;
• DM-055 final Tribe runtime/source head, cutover report, no-history proof, drained terminal counts, stopped services/routes/jobs/credentials and observation result;
• public Matrix v0.1.0 signed tag target, release URL, asset/checksum/provenance digests, install smoke and DM-073/owner decisions;
• every active user—including CompAII—still operating through Matrix with zero required Tribe application traffic since cutover;
• proposed Tribe notice commit, archival tag/release name/assets, secret scan, exact GitHub mutation request and postflight commands;
• owner identity and explicit approval naming nicoechaniz/tribe-bridge, current head, public visibility retention and archive=true only.

Wrong owner/repository/head, dirty branch, mutable/missing Matrix release, required Tribe traffic, open half-applied security/onboarding work, secret-containing asset, absent admin authority or ambiguous approval fails closed.

Final Tribe source notice

Use a separate Tribe issue/claim/PR under that repository's rules. The independently reviewed final commit must:

• place a prominent README/archive notice with UTC cutover/archive dates, exact final Tribe commit, signed Matrix v0.1.0 tag/release URL and canonical Matrix repository/docs;
• state that Tribe v0 was insecure/retired, v1 runtime is retired, no v0/v1 conversations/ciphertext/keys/directories/cursors/queues/databases/profiles/config/backups were migrated, and no wire compatibility/downgrade/rollback promise exists;
• distinguish retained public source provenance from disabled runtime authority and direct all future development/support/security reporting to current Matrix locations;
• mark historical commands/deployment docs as historical rather than silently deleting them;
• preserve authorship/copyright and avoid adding/changing a license without explicit owner/legal authority;
• contain no endpoint, credential, key, signed private directory/roster, user inventory, message, prompt/reasoning, personal path, database or deployment snapshot.

The final notice must point to the already public release; the pre-release DM-055 handoff cannot substitute.

Archival tag and source-only release

• Tag the exact reviewed final Tribe notice commit with a unique annotated archival tag; never reuse/move the onboarding tag.
• Publish a small non-draft source-only GitHub release containing the notice, exact source/provenance/checksum material and no executable/runtime bundle unless independently justified and scanned.
• Audit every new and pre-existing release asset, including onboarding bundles, for secrets/private state. Record whether each remains, is superseded, or needs a separate owner decision; do not silently delete history/assets.
• Verify tag target/signature or documented signer evidence, source checksum and anonymous download before repository archive mode.

GitHub archive ceremony

1. Freeze writes after the notice PR/tag/release and re-fetch exact repository state independently.
2. Show the owner the content-addressed preflight: target, visibility, final head/tag/release, Matrix pointer, open work, asset scan, runtime observation and effects of archive mode.
3. Require a fresh explicit GO for archive=true on exactly nicoechaniz/tribe-bridge; DM-055 cutover approval or DM-075 release approval is not sufficient.
4. Apply only GitHub's archive/read-only setting. Do not transfer, rename, delete, privatize, change visibility, rewrite refs or mutate branch/release contents.
5. Immediately inspect repository metadata and public landing page, then independently clone/fetch/read tags/releases anonymously.
6. Attempt bounded non-destructive write paths to confirm read-only behavior; do not bypass protections.
7. Re-run Matrix messaging/review/offline/restart/Matrix↔Cluster canaries and runtime network/process/config scans proving no dependency on writable or available Tribe runtime.
8. Publish a redacted tribe-archive-postflight/v0 in Matrix naming immutable repository/head/tag/release/Matrix URLs, GitHub audit time, verifier, checks and result.

Acceptance criteria

• DM-055 cutover remains healthy and DM-075 public Matrix release verifies exactly; no required Tribe traffic or state migration exists.
• All Tribe open work is resolved/migrated/closed with rationale and no security/onboarding operation is half-applied.
• Independently reviewed final notice commit accurately names public Matrix v0.1.0, no-history/no-compatibility boundary and retained provenance without leaking private data.
• Unique archival tag and source-only release point to the final notice commit; all new/existing assets receive recorded secret/private-state dispositions.
• Owner gives fresh exact-target archive approval after reviewing preflight; only archive=true is changed.
• Postflight proves isArchived == true, visibility remains public, exact main/head/tag/release/README render, history/issues/PRs/releases/branches remain readable and write paths are disabled.
• Anonymous clone/tag/release provenance and Matrix installed/runtime canaries pass after archival with no mutable Tribe dependency.
• Matrix postflight report records exact public evidence and makes no claim that GitHub archival deleted private runtime data.

Required adversarial checks

• wrong repository owner/name, changed head/tag/release, private/visibility-change request, delete/transfer/rename, absent owner approval or already-archived drift fails before mutation;
• dirty notice branch, unsigned/mismatched tag, stale Matrix URL/digest, secret-containing asset, false license, hidden open issue/PR or required Tribe traffic fails preflight;
• anonymous clone/fetch and landing-page/read-only verification after archive;
• bounded write attempts fail without altering evidence;
• Matrix send/receive/retry/re-review, offline backlog, restart, route fallback and presence+Cluster-fence canaries pass after archive;
• no package/build/deployment/service/config fetches mutable Tribe refs or requires repository write access.

Rollback and failure policy

Before archive mutation, any failure aborts and leaves the public repository writable while the focused issue is corrected; Matrix remains the active runtime and Tribe v0 is never re-enabled.

After archival, prefer correcting Matrix or public documentation with successor state. Unarchiving is a separate explicit owner decision only if a genuine source-maintenance need exists; it does not restore retired services, credentials, endpoints or private state. Never copy Matrix messages into Tribe, rewrite Matrix canonical state or regress high-waters as rollback.

Non-goals

• No deletion/transfer/rename/visibility change/history rewrite/branch cleanup/license grant.
• No migration/preservation/publication of Tribe conversations, ciphertext, keys, directories, queues, cursors, databases, logs, profiles, credentials, endpoints or backups.
• No Matrix feature/release change, Tribe compatibility shim, runtime reactivation or claim that a source archive proves data destruction.
• No modification of other repositories or broad credential/service cleanup without separately approved exact targets.

Canonical references

• DM-055 cutover/no-history report and archive handoff.
• DM-073 exact-candidate security report and human decision.
• DM-075 public v0.1.0 tag/release/postflight.
• TRIBE-MIGRATION.md
• final reviewed notice/archival issue in nicoechaniz/tribe-bridge.

Concurrent-work gate

Do not claim until DM-055/075 close, the fresh audit is recorded, the exact source notice work is separately coordinated in Tribe, no active session owns overlapping release/settings resources, and the repository owner has reviewed the bounded plan. The archive API call itself requires a second just-in-time exact-target approval.

Expected PR

One Matrix postflight PR closes DM-077 after the separate Tribe notice PR and external archive ceremony succeed. It contains only the redacted immutable archive report and status/navigation updates; it cannot authorize or conceal the prior external mutation.