Skip to content

feat(release): add versioned SN39 seals - #142

Merged
wallscaler merged 1 commit into
mainfrom
codex/sn39-release-generation
Aug 16, 2026
Merged

feat(release): add versioned SN39 seals#142
wallscaler merged 1 commit into
mainfrom
codex/sn39-release-generation

Conversation

@wallscaler

Copy link
Copy Markdown
Contributor

What changed

  • preserve the historical root release.json seal
  • publish later seals under digest-addressed releases/sha256/<digest>.json[.sig] paths
  • add an operation-bound, filesystem-read-only preflight mode
  • bind the rotating controlled-evidence selector to one safe direct-sibling epoch by directory descriptor
  • verify digest-addressed releases in the public reproducer
  • provision versioned release directories and document the operator flow
  • add adversarial tests for symlink escape, publication conflict, historical preservation, context separation, and Git-index immutability

Why

The current root seal is publish-once. A second ceremony needs a new immutable generation without replacing historical bytes. The previous finalizer also rejected the live current selector symlink, and an ordinary git status could refresh .git/index during a claimed read-only preflight.

Impact

This prepares a legitimate second-generation SN39 ceremony. It does not authorize or perform a seal, chain write, deployment, or production mutation. Operators still need matching immutable producer and validator revisions, current passing provenance gates, and complete release pins before preflight.

Validation

  • independent security review after remediation: PASS
  • release-generation tests: 20 passed
  • expanded release, reproduction, manifest, and launcher set: 80 passed
  • Ruff check: passed
  • Ruff format check: passed
  • git diff --check: passed
  • live read-only route audit: nested evidence paths are supported; actual versioned artifact retrieval remains unproven until a legitimate publication exists

Known boundary

The full repository suite is not proven in the local macOS environment because unrelated installed dependency conflicts and /usr/bin/python3.12 fixture assumptions prevent complete collection. GitHub CI remains required before merge.

Preserve the historical root seal while allowing digest-addressed release generations. Add a read-only preflight, safe controlled-root selection, reproducible versioned fetches, and adversarial coverage so a later ceremony can fail closed before signing.
@wallscaler
wallscaler marked this pull request as ready for review August 16, 2026 05:37
@cursor

cursor Bot commented Aug 16, 2026

Copy link
Copy Markdown

Bugbot is not enabled for your account, so this pull request was not reviewed.

Enable Bugbot in the Cursor dashboard to get automatic reviews on future PRs.

@wallscaler
wallscaler merged commit 4234d5b into main Aug 16, 2026
4 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.

1 participant