Skip to content

RELEASES.md

Latest commit

 

History

History
85 lines (70 loc) · 4.35 KB

RELEASES.md

File metadata and controls

85 lines (70 loc) · 4.35 KB
Raw

Releases

Release assets are kept out of Git history and attached to separate GitHub Releases. Automatically generated source ZIP/TAR archives are repository snapshots, not Project Shadow release artifacts.

Current public releases

Publication phase: POSTPUBLICATION. The packaging correction remains implemented; its six-site effectiveness criterion is pending reverification.

  1. generic-myth-v0.2.0 — Generic Myth Sidecar v0.2.0, optional public companion. Its final identity is frozen, its final tests pass, and its exact hash is published separately on GitHub and Hugging Face.
  2. r1.0.1-2026-08-17 — Project Shadow 1.0.1 R1 reference packaging correction. Its exact inner is admitted and its deterministic outer build is frozen, separately exact-hash authorized, and published on GitHub and Hugging Face.

The Generic sidecar was published first. R1.0.1 was published last so the corrected R1 is the latest release. Subsequent anonymous GitHub and Hugging Face redownloads and bounded package verification remain valid. The historical six-site checks passed their then-current lexical predicates, but external adversarial review showed those predicates did not adequately prove the relation-level boundary. The packaging-boundary CAPA is currently IMPLEMENTED_PENDING_EFFECTIVENESS.

Existing public releases

  • myth-v0.3.5 — Full-Canon Myth Sidecar v0.3.5, optional public companion.
  • myth-v0.3.4 — preserved historical optional research sidecar.
  • r1-2026-08-14 — preserved historical R1 release. Its bytes are immutable; R1.0.1 supersedes it as the current reference because the old outer package included a nested Generic Myth v0.1.1 member carrying non-public metadata.

Historical release notes and governance records remain in place. Nothing in the 2026-08-17 correction back-writes the August 14 authorization, status, redownload receipt, tags, or archive.

Files under release-notes/ are content-aligned publication-time snapshots of the live GitHub release bodies (line endings and trailing Markdown spaces are normalized). Any open/pending CAPA wording retained there records the then-current release-time state. Current lifecycle status is defined by PUBLIC_RELEASE_STATUS_2026-08-17.json, PUBLICATION_MANIFEST.json, the current CAPA and reopening records, and whichever effectiveness records those current records explicitly bind. Historical receipts remain evidence of their own observations; they do not independently define today’s state.

Historical effectiveness sequence and reopening

  1. The recorded Generic, inner, and outer exact-hash authorities were preserved without broadening them.
  2. GitHub and Hugging Face copies of Generic v0.2.0 and R1.0.1 were anonymously redownloaded and matched their exact byte counts and SHA-256 values.
  3. Both downloaded Generic archives passed the bounded 23-path verifier, and R1.0.1 passed recursive zero-Myth verification.
  4. All six public sites passed the original corrected-boundary lexical checks, including the Project Shadow status surface and the National Trump Record route.
  5. CAPA PS-R1-PRIVATE-MYTH-PUBLIC-BOUNDARY-001 was recorded closed effective on 2026-08-18 using the retained redownload and six-site receipts.
  6. On 2026-08-22, external adversarial fixtures demonstrated that release-role reversal, dual-current, contradictory CAPA, reversed sidecar semantics, and identity misbinding could preserve the old PASS result.
  7. The historical closure was preserved and the current CAPA state returned to IMPLEMENTED_PENDING_EFFECTIVENESS for the six-site criterion only. A new v2 receipt must retain and replay exact response bodies before reclosure. A named human must then review all six browser-rendered sites, bind that review to the exact v2 receipt/evidence pack, and confirm the visible meaning.

Prospective custody procedure

Future release tags should be signed annotated tags from the intended verified commit. Release assets must not be replaced after publication. GitHub release immutability and tag protection do not rewrite the original August 14 tags.

git tag -s <release-tag> -m "<release title>" <verified-commit-sha>
git tag -v <release-tag>
git push origin <release-tag>

For questions or corrections, use projectshadowqa@protonmail.com with the subject prefix described in CONTACT_AND_CORRECTIONS.md.