PROJECT SHADOW 1.0.1 · CORRECTED R1 REFERENCE · PRELIVE · 2026-08-17

Project Shadow 1.0.1 contains no Myth package. Generic Myth v0.2.0 and Full-Canon Myth v0.3.5 are separate optional companions; both default off, neither is required by R1, and neither can authorize action or change an R1 result. No production or consequential deployment is authorized. No global green.

PROJECTSHADOW R1.0.1 corrected · PRELIVE
CAPACorrective and preventive action · 2026-08-17closed effective · 2026-08-18

Correct the package. Preserve the record. Verify the boundary.

PS-R1-PRIVATE-MYTH-PUBLIC-BOUNDARY-001 records the public-packaging nonconformity, containment, root cause, correction, prevention controls, verification evidence, and bounded effectiveness closure.

PS-R1-PRIVATE-MYTH-PUBLIC-BOUNDARY-001

Closed effective—within the packaging boundary.

The exact correction is built, tested, authorized, published, anonymously redownloaded from both hosts, and checked across all six GPT Sites within a PRELIVE reference boundary. No predecessor bytes were rewritten, and no production or operational deployment was authorized.

01 / CAPA RECORD

Every state change keeps its evidence and boundary attached.

NONCONFORMITY

Nested private payload crossed the public boundary

The preserved August 14 public outer contained the exact Generic Myth v0.1.1 payload whose own metadata classified it PRIVATE_INTERNAL_ONLY, EXCLUDED_FROM_PUBLIC, and ineligible for public manufacture. Prohibited payload SHA-256: 4d8481ed8f6af3e04d86a5c2de7e94aad47a591e1ce9c8757bbb4b0a397b90bb.

CONTAINMENT

Preserve, supersede, never silently replace

The August 14 R1 archive remains unchanged at 7,679,812 bytes and SHA-256 2f8fe1530b6a83294d15011df95853aaecf08fa4dba756f0c2e91dd089e1b1ec. It is immutable historical evidence and is superseded only for this packaging-boundary correction.

ROOT CAUSE

Eligibility stopped at the outer boundary

The release build and verifier checked outer custody but did not recursively enforce nested publication classifications or deny the exact prohibited-payload hash.

CORRECTION

Issue a deterministic Myth-free successor

R1.0.1 is 5,731,663 bytes with SHA-256 6f6f1e16d5e9a20e62403f14af7ce8629ce2d702528fb7f80aaf4a14deb7a1d1. Its admitted Myth-free inner is 5,463,189 bytes with SHA-256 c8c32b12432c954b1a6f852c0c9f81bbbd40167e936be057d4c3de1a0aa3a623. All 27 active descendants are byte-identical to August 14; zero operational descendant bytes changed.

SEPARATION

Keep Myth external and nonauthorizing

Generic Myth v0.2.0 is a separate 93,676-byte default-off, terminal-only companion with SHA-256 6e7a362d4135f9d626dcfef463bfb1f7166226b3cf8a4c02a953ab39af1538bf. Full-Canon Myth v0.3.5 is a separate 1,428,812-byte default-off mixed-rights companion with SHA-256 2b55867fe7c502a0defd8d6f2e9b53fbd1caaf1b0f225a438bd45b04a3e7bae2. Neither is required by R1 or can alter a gate, result, or authorization.

PREVENTION

Make recursive publication eligibility executable

The successor adds recursive ZIP inspection, an exact prohibited-hash deny rule, release-classification scanning, safe-path and symlink checks, depth and budget limits, deterministic double builds, verifier mutation tests, and runtime replay.

02 / VERIFICATION + EFFECTIVENESS

Passing build controls is necessary. Public effectiveness is a separate gate.

PASS

Deterministic custody

Two outer builds were byte-identical; the full and cold tree verifiers passed.

PASS

Recursive baseline

32 nested-verifier baselines and an 89-ZIP-node / 2,987-file baseline inspection passed.

PASS

Runtime replay

265 of 265 runtime replay checks passed without changing the 27 active descendant bytes.

PASS

Generic companion

32 of 32 Generic Myth v0.2.0 checks passed within its terminal-only, default-off boundary.

PASS

Adversarial prevention

14 of 14 adversarial mutants were rejected by the recursive publication controls.

PASS

Public effectiveness

Anonymous GitHub and Hugging Face redownloads matched the exact authorized ZIPs and checksum files. Live checks across all six GPT Sites matched the corrected boundary. The two retained evidence records close this packaging CAPA only.

CLAIM BOUNDARY

Packaging correction is not deployment proof.

This CAPA establishes package identity, recursive publication control behavior, preserved operational descendant bytes, and the present effectiveness state.

What this record cannot establish

  • Production or operational deployment authority.
  • Field efficacy, safety, or a harm-prevention guarantee.
  • Certification, standards approval, or legal compliance.
  • Fresh independent human validation.
  • Authority from either optional sidecar.
  • Any closure beyond this exact packaging-boundary correction.
CONTINUE

Inspect the exact releases and effectiveness receipts.

Release + downloads →Current status →Public redownload receipt →Six-site effectiveness receipt →The Record corrections →National Trump Record →
THE CAPA RULE
Preserve the failure. Correct the boundary. Test the prevention. Close only on effectiveness evidence.