ProjectShadow/project-shadow-r1-reference

1# CAPA status and preserved closure history2 3**Finding:** `PS-R1-PRIVATE-MYTH-PUBLIC-BOUNDARY-001`  4**Current state:** `IMPLEMENTED_PENDING_EFFECTIVENESS`  5**Reopened criterion:** Six public sites express the corrected boundary with the right relationships and identities.  6**Reopening:** August 22, 2026. This replacement was prepared September 10, 2026.7 8R1.0.1 remains the published corrected public reference. The packaging correction, Myth-free active runtime family, and historical exact-byte observations remain distinct from the reopened effectiveness criterion. Generic Myth v0.2.0 and Full-Canon Myth v0.3.5 remain separate optional, default-off, nonauthorizing companions.9 10The August 18 closure is a preserved historical event. Subsequent adversarial review showed that the old website checks could find all expected words while missing a reversal of their meaning. The prior six-site receipt therefore does not establish current relationship-level effectiveness. This page does not close that criterion or turn an archive checksum into assurance about a website.11 12The governing [August 22 reopening record](https://github.com/PauseBeforeHarmProtocol/Project-Shadow/blob/8b44e84a714c55ffa3eeece9e99eabfe31a0583f/governance/CAPA_PS-R1-PRIVATE-MYTH-PUBLIC-BOUNDARY-001_EFFECTIVENESS_REOPENING_2026-08-22.json) requires the corrected relation checks, negative controls, retained response bodies, explicit execution accounting, all required routes, and human review of visible meaning. The [v2 boundary contract](https://github.com/PauseBeforeHarmProtocol/Project-Shadow/blob/8b44e84a714c55ffa3eeece9e99eabfe31a0583f/docs/PUBLIC_SITE_BOUNDARY_CONTRACT_V2.md) describes those checks. A status-page correction alone does not satisfy them.13 14## Historical record15 16The [previous status JSON](history/2026-08-18/CURRENT_RELEASE_STATUS.json) and [previous closure summary](history/2026-08-18/OPEN_CAPA_SUMMARY.md) preserve what this Space served before correction. These historical files do not govern current status.17 18## Separate 1.0.2 work19 20The 1.0.2 family is an unreleased candidate for review. Neither its local tests nor its preparation for distribution establishes deployed effectiveness or closes this older CAPA. No production or operational deployment authorization is conveyed.21