Skip to content

Freeze V7/V3 runtime boundary and RC preflight - #121

Merged
nicoechaniz merged 7 commits into
mainfrom
rc/v0.1.0rc1-metadata-20260816
Aug 16, 2026
Merged

Freeze V7/V3 runtime boundary and RC preflight#121
nicoechaniz merged 7 commits into
mainfrom
rc/v0.1.0rc1-metadata-20260816

Conversation

@nicoechaniz

@nicoechaniz nicoechaniz commented Aug 16, 2026

Copy link
Copy Markdown
Contributor

Issue

Closes #120
Refs #72 #43 #40

Claim-ID: 0089f9fa-aaa1-4c0b-a173-416310c6644f
Deployment: not deployed

Outcome

Freezes the Matrix side of the V0.1.0 RC on one operational runtime format (bundle V7) and one client format (config V3), binds local responses to the authenticated runtime identity, closes published schemas over the exact supported surface, and adds an offline content-addressed preflight for a future consented cross-being canary.

The preflight records human and external gates but cannot infer or grant consent, custody independence, contact, execution, or semantic receipt. Historical unshipped runtime/client formats are removed from operational paths.

Exact candidate: 572b321dfb3bd48d52e250e3ebb137f6b853d94a
Tree: d7146e291ae3f8313dc0b3d3c3a0b5e5f94d33ad

Invariants

  • Identity and provenance remain verifiable.
  • No private memory or credentials were added.
  • No deployed compatibility commitment exists; obsolete pre-release formats fail closed.
  • Host, deployment, custody, participant-contact and canary-execution gates remain external and unauthorized.

Validation

  • Independent exact-head review: PASS after correcting output-path races and published-schema drift.
  • Runtime/client negative coverage rejects V1-V6 bundles, V1/V2 configs, identity substitution, schema omissions and stale cached responses.
  • Published surface equality: 84 service methods, 70 installed CLI commands, 67 MCP tools.
  • Cross-being preflight adversarial I/O tests cover symlink, hardlink, inode/name replacement, non-canonical input, overwrite, missing rollback and non-distinct participants/custody.
  • Two offline builds are byte-identical and clean-install artifacts were inspected.

Tests

  • Source-isolated full suite: 640 tests, 22 declared skips, exit 0, no rerun.
  • Ruff check/format: PASS.
  • Strict mypy: PASS.
  • Compileall and Draft 2020-12 schema validation: PASS.
  • All generated-vector/provenance checks: PASS.
  • uv lock --check --offline: PASS.
  • Wheel SHA256: a8433cb007b46d45593895d0e459828a7281f09eb89cb85f558f8eabc9bc5e83.
  • Sdist SHA256: f1fa00e3c5d18cb7ecce44ae656938ff35daeedb22e713cdc53b916208a6befe.
  • Repository/wheel/sdist secret scan: clean.

Security and rollback

All new operational parsers fail closed. The canary tool is a freezer/validator only and emits no executable authorization. Rollback is the normal protected revert of this pre-release merge; no live state, service, key, custody, host, SSH, participant or production system was changed.

Coordination receipt: accepted for PR #121.

@nicoechaniz
nicoechaniz merged commit 09414d6 into main Aug 16, 2026
12 of 13 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[RC] Freeze the V7/V3-only runtime and offline canary preflight

1 participant