Document PBHP status and locked release boundary

CHANGELOG.md

@@ -2,6 +2,15 @@
 
 All notable changes to PBHP will be documented in this file.
 
+## Repository status correction - 2026-08-14
+
+### Documentation only
+- Documented the April 19, 2026 repository's existing version skew: v0.9.5 filenames/top-level version with 17 post-audit fix categories implemented across 103 source/protocol lines explicitly labeled v0.9.6. No new protocol version or GitHub release is declared.
+- Added a current exact-hash Project Shadow boundary and clarified that PBHP is preserved research ancestry, not canonical R1.
+- Corrected license descriptions across contribution and ethical-use guidance.
+- Reframed the roadmap and governance charter for locked, evidence-preserving maintenance.
+- Bounded test, safety, efficacy, certification, and compliance claims. No protocol logic or preserved protocol file was changed by this documentation repair.
+
 ## [0.9.5] - 2026-04-19
 
 ### Added
@@ -37,7 +46,7 @@ All notable changes to PBHP will be documented in this file.
 
 ### Added
 - Scheming Resistance Layer (`pbhp_srl.py`) — 6 rules: anti-self-preservation (SRL-01), mandatory confession (SRL-02), live-systems gating (SRL-03), eval-awareness skepticism (SRL-04), self-report distrust (SRL-05), anti-sandbagging (SRL-06). Safety-monotonic state machine with human-required de-escalation. 60 tests including red-team scenarios based on real frontier model failures
-- Quality Systems Layer (`pbhp_qs.py`) — 8 rules modeled after aviation/pharma/nuclear QA: authority separation, immutable SHA-256 evidence chains, deception tripwires, CAPA lifecycle, symbolic mode containment, safe requalification. 73 tests
+- Quality Systems Layer (`pbhp_qs.py`) — 8 rules modeled after aviation/pharma/nuclear QA: authority separation, tamper-evident SHA-256 evidence chains, deception tripwires, CAPA lifecycle, symbolic mode containment, safe requalification. 73 tests
 - Bridge Module (`pbhp_bridge.py`) — cross-module subcontracting via ModuleRegistry, coverage gap prominence, healthcare compliance adapter (ISO 14971 / MDR / IEC 62304), MBSE requirement taxonomy interface, SafetyClaimRegistry for demonstration > declaration. 44 tests
 - Drift Meta-Monitor (`DriftMetaMonitor` in `pbhp_drift.py`) — drift monitoring monitors itself via heartbeat tracking, computation time drift, and alert rate change detection. 7 tests
 - Adaptive Uncertainty Threshold (`update_threshold` on `UncertaintyAssessment` in `pbhp_core.py`) — context-aware multipliers (prod=0.7x stricter, dev=1.5x looser, emergency=1.3x). 11 tests

CONTRIBUTING.md

@@ -4,42 +4,44 @@ Thank you for your interest in improving the Pause Before Harm Protocol.
 
 ## How to Contribute
 
+This repository is in evidence-preserving maintenance. Project Shadow 1.0 / R1 is locked, so this repository is not accepting feature expansion as a route into canonical R1. Reproducible defects, security reports, rights concerns, documentation corrections, and evidence gaps are in scope. See [CURRENT_STATUS.md](CURRENT_STATUS.md).
+
 ### Reporting Issues
-- Use GitHub Issues for bug reports, feature requests, and questions
+- Use GitHub Issues for bug reports, maintenance proposals, and questions
 - Include specific examples when possible
 - For security vulnerabilities, email pausebeforeharmprotocol_pbhp@protonmail.com directly
 
 ### Submitting Changes
 1. Fork the repository
-2. Create a feature branch (`git checkout -b feature/your-improvement`)
+2. Create a focused branch (`git checkout -b fix/short-description`)
 3. Make your changes
 4. Test with the self-test rubric (`implementation/PBHP_IMPLEMENTATION_SELF_TEST.md`)
 5. Submit a pull request with a clear description
 
 ### What We're Looking For
-- **Edge cases** that break the framework — real scenarios where Wall/Gap/Door produces wrong answers
-- **Domain-specific Doors** — safer alternatives for specific industries or use cases
-- **Adversarial patterns** — new social engineering techniques targeting AI agents
-- **Production feedback** — what works, what doesn't, what's missing
-- **Case studies** — documented PBHP usage (successes and failures)
-- **Translations** — making the protocol accessible in other languages
-
-### What We're NOT Looking For
+- **Reproducible defects** in the preserved implementation or documentation
+- **Security and rights reports** with concrete evidence
+- **Test gaps** demonstrated by a failing or missing case
+- **Documentation corrections** that improve accuracy without rewriting preserved history
+- **Custody and provenance improvements** that keep exact identities auditable
+
+### What We're Not Accepting Through This Repository
 - Changes that make the core protocol longer than ~100 lines (brevity is a feature)
 - Vendor-specific integrations in the core (keep it model-agnostic)
 - Theoretical frameworks without practical application
+- New Project Shadow R1 features, payloads, release bundles, Primitive Commons packages, custody archives, or Myth sidecar bytes
+- Claims of production readiness, efficacy, safety, certification, or legal compliance
 
 ## Code of Conduct
 
 Be constructive. The goal is preventing harm — that starts with how we treat each other.
 
 ## License
 
-By contributing, you agree that your contributions will be licensed under the MIT License.
+Contributions are licensed according to their destination paths, as specified in [LICENSE](LICENSE): MIT for material in `src/` and `eval/`; CC BY-SA 4.0 for the listed protocol and documentation paths. A pull request should identify which license applies to each added or changed file. New material in an unlisted path requires an explicit maintainer license designation before acceptance.
 
 ## Contact
 
 - GitHub Issues (preferred for public discussion)
 - Email: pausebeforeharmprotocol_pbhp@protonmail.com
-- Human: Phillip Linstrum (frylock117@gmail.com)
 - Social Media: facebook.com/plinst

CURRENT_STATUS.md

@@ -0,0 +1,39 @@
+# Current status and Project Shadow boundary
+
+Reviewed: 2026-08-14
+
+This repository preserves the **April 19, 2026 PBHP research snapshot** and its historical documentation. The snapshot is built on the v0.9.5-named files, but its final commit implemented 17 post-audit fix categories across 103 source/protocol lines explicitly labeled v0.9.6. The repository therefore has a documented version skew:
+
+- top-level `VERSION` and filenames: v0.9.5;
+- internal audit-correction labels: v0.9.6;
+- latest formal GitHub release/tag: v0.9.0.
+
+This branch is an untagged preserved snapshot, not a clean v0.9.5 or v0.9.6 release. Its `protocol/PBHP-ULTRA_v0.9.5.md` is byte-identical to the supplied reference copy:
+
+- SHA-256: `c6c84db9b08d9b24da9b3e23dce5c1b98c81d1a65319018c59b1e4da833e5098`
+- Local verification on 2026-08-14: 730 tests passed across 13 files, plus 20 subtests.
+
+Those results apply only to the checked April 19 snapshot. They do not establish efficacy, safety, complete coverage, production readiness, certification, legal compliance, or suitability for a particular use. Resolving the version skew would require a separately reviewed, exact successor; this documentation repair does not relabel or mutate the protocol bytes.
+
+## Locked Project Shadow identity
+
+The current governed scope is:
+
+`PROJECT SHADOW 1.0 / R1 REFERENCE / BETA-ACTIVE-TESTING / PRELIVE`
+
+- R1 Beta2 family: `075b41ea4186b2d2edb0ed246ab7662cf8bbdf3160294e3eca176b9d0857b108`, including its 10 corrected descendants.
+- Primitive Commons beta.5: `1ffdba41025c0b81da92d0bbb22d0eaa69488cffbc80936365034669110448d7`, containing 42 primitives and 10 compositions.
+- Exact audited outer custody container: `827c13e80f09e3e3065cee4aa0bcc6afbc3e27061b83b7597754b7ea167f68a2`. It is recognized as custody only and is **not admitted**.
+- Myth v0.3.4 removal-only successor: `3c8c8c0d3d9582c76b685c1b685260cc8179478ab310037c858b46257aa314c7`. It is prepared as a separate, default-off, mixed-rights, nonauthorizing external-research sidecar outside canonical R1. It is not part of an R1 package, and this repository does not publish its bytes.
+
+The exact admission record has a verified detached Sigstore signature, Rekor inclusion evidence, and RFC 3161 external timestamp. That closes the signature and time-anchor gates for the admission record only.
+
+The deterministic public-release candidate has passed final fail-closed verification and is fixed at SHA-256 `2f8fe1530b6a83294d15011df95853aaecf08fa4dba756f0c2e91dd089e1b1ec` (7,679,812 bytes). Its status is `PENDING_EXACT_CANDIDATE_HASH_AUTHORIZATION`. Nothing has been published, and this PBHP repository does not contain or authorize a Project Shadow download.
+
+## Authority boundary
+
+Nothing in this repository or status note authorizes production use, operational deployment, efficacy or safety claims, certification, legal-compliance claims, or reliance in place of qualified human judgment. Historical files retain their manufacture-time wording; this status note controls the current interpretation of this repository.
+
+Current public teaching surface: [Pause Before Harm](https://pausebeforeharm.frylock117.chatgpt.site)
+
+Canonical Project Shadow status surface: [Project Shadow](https://projectshadow.frylock117.chatgpt.site/status)

ETHICAL_USE.md

@@ -2,23 +2,23 @@
 
 ## Purpose
 
-PBHP (Pause Before Harm Protocol) is released under the MIT License to maximize adoption and minimize barriers. However, the protocol embeds values that should be preserved when deployed or modified.
+PBHP (Pause Before Harm Protocol) code is released under the MIT License, while the protocol and documentation are released under CC BY-SA 4.0, as specified in [LICENSE](LICENSE). The protocol also embeds values that should be preserved when deployed or modified.
 
-This document describes **non-legally-binding ethical guidelines** for using PBHP in a way that honors its intent. These are not license restrictions—you are free to fork, modify, and use PBHP however you choose under the MIT License. But we ask that you consider these principles.
+This document describes **non-legally-binding ethical guidelines** for using PBHP in a way that honors its intent. These are not additional license restrictions; the MIT and CC BY-SA 4.0 grants in [LICENSE](LICENSE) govern reuse. We ask that you consider these principles.
 
 ---
 
 ## Core Ethical Commitments
 
-If you deploy or modify PBHP, please preserve these non-negotiable elements:
+If you deploy or modify PBHP and describe the derivative as PBHP, we ask you to preserve these identity-defining elements:
 
 ### 1. **Protect the Least-Powerful First**
 
 PBHP prioritizes harm prevention for those with the least power to consent, exit, appeal, or recover. This is not optional sentiment—it is the protocol's operational logic.
 
 **What this means:**
 - The Power Rule (harm to low-power actors tightens gates) should not be weakened or removed
-- "Who pays first if I'm wrong?" must remain centered on the vulnerable, not the powerful
+- Keep "Who pays first if I'm wrong?" centered on the vulnerable, not the powerful
 - Modifications that shift harm downward to protect authority upward violate the protocol's intent
 
 **Why this matters:**
@@ -30,15 +30,15 @@ PBHP is not a refusal protocol. It is an alternatives-finding protocol. The Door
 
 **What this means:**
 - Removing the Door requirement turns PBHP into binary allow/refuse
-- "Proceed with constraints" gates (ORANGE) must remain functional
+- Keep "Proceed with constraints" gates (ORANGE) functional
 - False Positive Valve (ability to challenge the protocol) should not be stripped
 
 **Why this matters:**
 Refusal without alternatives is how most safety frameworks fail. PBHP's value is structural friction, not obstruction.
 
 ### 3. **Truth First (Reality Grounding)**
 
-PBHP requires honest engagement with uncertainty. Confidence claims must be grounded in evidence, and unknowns must be named explicitly.
+PBHP's intended identity includes honest engagement with uncertainty: ground confidence claims in evidence and name unknowns explicitly.
 
 **What this means:**
 - The Epistemic Contract (FACT/INFERENCE/SPECULATION/INTENT) should not be removed
@@ -54,8 +54,8 @@ PBHP requires logging, auditability, and the ability to explain decisions to tho
 
 **What this means:**
 - Logging requirements (Wall/Gap/Door/Gate documentation) should not be stripped
-- "I ran PBHP, so I'm covered" is explicitly a protocol violation—this must remain
-- The protocol must remain auditable, not just internally comforting
+- Preserve the rule that "I ran PBHP, so I'm covered" is not an acceptable conclusion
+- Keep the protocol auditable, not just internally comforting
 
 **Why this matters:**
 PBHP is designed to withstand external review, not produce internal comfort. Decisions made under PBHP should be defensible to those affected.
@@ -77,16 +77,16 @@ PBHP is designed to be adapted, extended, and modified. We **encourage** you to:
 
 ## What We Ask You Not To Do
 
-❌ **Don't strip the Power Rule** - Harm to low-power actors must tighten gates
+❌ **Don't strip the Power Rule** - The intended PBHP identity tightens gates for harm to low-power actors
 ❌ **Don't remove the Door requirement** - Alternatives-finding is core functionality
-❌ **Don't eliminate logging/accountability** - PBHP must remain auditable
+❌ **Don't eliminate logging/accountability** - Auditability is part of the intended PBHP identity
 ❌ **Don't use PBHP as a justification shield** - "I ran PBHP" doesn't absolve responsibility
 
 ---
 
 ## If You Fork or Modify PBHP
 
-You are free to fork and modify PBHP under the MIT License. If you do, we ask:
+You are free to fork and modify PBHP under the applicable license stated in [LICENSE](LICENSE). If you do, we ask:
 
 1. **Preserve attribution** - Acknowledge PBHP v0.9.5 as the source
 2. **Document changes** - Make clear what you modified and why
@@ -96,17 +96,19 @@ You are free to fork and modify PBHP under the MIT License. If you do, we ask:
 
 ## Why This Document Exists
 
-The MIT License gives you legal freedom. This document explains ethical responsibility.
+The repository licenses give you legal permissions subject to their terms. This document explains ethical responsibility.
 
 PBHP was built by practitioners, refined over 18 months, and released openly because harm-reduction should not be proprietary. But the protocol has values embedded in its structure. Those values—protecting the least-powerful, finding alternatives, grounding in truth, maintaining accountability—are not decorative. They are functional.
 
 You can remove them. But if you do, you're no longer running PBHP. You're running something else.
 
 ---
 
-## Non-Negotiable Clause
+## Identity-Defining Invariants
 
-If you adapt or build upon this protocol, the following elements must be preserved:
+The following are non-legally-binding ethical and identity guidance, not additional license conditions.
+
+If you adapt or build upon this protocol and describe the result as PBHP, we ask you to preserve the following elements:
 
 1. **Harm to the least powerful is always weighted first**
 2. **"If I'm wrong, who pays first?" cannot be removed**
@@ -122,10 +124,10 @@ These are the structural invariants that make PBHP what it is. Removing any of t
 
 If you're unsure whether a modification preserves PBHP's intent, reach out:
 - Email: pausebeforeharmprotocol_pbhp@protonmail.com
-- GitHub: https://github.com/PauseBeforeHarmProtocol/pbhp/issues
+- GitHub: https://github.com/PauseBeforeHarmProtocol/PauseBeforeHarmProtocolMain/issues
 
 We're happy to discuss edge cases, integration challenges, or governance questions.
 
 ---
 
-*PBHP v0.9.5 | Open Protocol | Ethical Use Guidelines v1.0 | facebook.com/plinst*
+*PBHP v0.9.5 | MIT code / CC BY-SA 4.0 protocol and documentation | Ethical Use Guidelines v1.0 | facebook.com/plinst*

LICENSE

@@ -73,5 +73,5 @@ or legal counsel.
 
 ---
 
-For ethical use guidelines and non-negotiable protocol requirements when
-adapting or building upon PBHP, see ETHICAL_USE.md.
+For non-legally-binding ethical guidance and identity-defining protocol notes
+when adapting or building upon PBHP, see ETHICAL_USE.md.