Release v0.2.2 with streamlined public documentation

Cargo.toml

@@ -1,6 +1,6 @@
 [package]
 name = "power_house"
-version = "0.2.1"
+version = "0.2.2"
 edition = "2021"
 authors = ["MFENX LLC"]
 description = "Deterministic sum-check proofs, commitment-bound sparse verification, and quorum ledger tooling."

JULIAN_PROTOCOL.md

@@ -1,5 +1,5 @@
 MFENX Power-House Network: The JULIAN Protocol Network
-Version 0.2.1 - June 2026
+Version 0.2.2 - June 2026
 
 
 # JULIAN Protocol: Proof-Transparent Consensus via Folding-Derived Anchors
@@ -183,9 +183,8 @@ implementation with:
 python3 scripts/verify_sparse_certificate.py target/power_house_sparse_record.phsp
 ```
 
-The artifact specification and benchmark manifest are in `docs/sparse_record.md` and
-`artifacts/sparse_record_v1.json`. The claim policy in `docs/research_claim.md` deliberately separates
-this reproducible engineering result from an unsupported world-first cryptographic claim.
+The artifact specification and benchmark manifest are in
+`docs/sparse_record.md` and `artifacts/sparse_record_v1.json`.
 
 The next layer is available through `cargo run --release --example committed_workload -- all`.
 It creates a canonical external `PHSMv1` sparse polynomial and a separate `PHCPv1` certificate

README.md

@@ -30,18 +30,6 @@ The external workflow stores the polynomial and proof separately:
 
 Verification requires both files and rejects workload substitution.
 
-These results demonstrate verification over enormous implicit domains. They do
-not establish that arbitrary sextillion-step computations can be verified, do
-not replace a quantum computer, and are not currently claimed as a world first.
-See [Research Claim Standard](docs/research_claim.md).
-
-The v1 sparse workflow is specifically a deterministic conformance artifact:
-the verifier reads the public sparse polynomial and recomputes the expected
-transcript. Because this polynomial family also has a closed-form Boolean sum,
-v1 is not a succinct delegated-computation result. The formal boundary and v2
-research target are documented in [Security Model](docs/security_model.md) and
-[Research Protocol](docs/research_protocol.md).
-
 ## Install
 
 ```bash
@@ -131,7 +119,6 @@ Operations and migration procedures are documented in
 - [Committed Workload Format](docs/committed_workload.md)
 - [Million-Round Sparse Certificate](docs/sparse_record.md)
 - [Hyperscale Seeded-Affine Proof](docs/hyperscale_proof.md)
-- [Research Claim Standard](docs/research_claim.md)
 - [Prior-Art Review](docs/prior_art_review.md)
 - [Sparse Certificate Security Model](docs/security_model.md)
 - [Research Protocol](docs/research_protocol.md)

RELEASE_NOTES.md

@@ -1,6 +1,6 @@
 # Release Notes
 
-## Unreleased - v0.3 research foundation
+## v0.2.2 - 2026-06-05
 
 ### Added
 - Canonical small `PHSPv1`/`PHSMv1`/`PHCPv1` conformance vectors and manifest.
@@ -15,6 +15,11 @@
 - Added decoder limits for variables, terms, degree, seeds, and total incidences.
 - Rejected oversized polynomial degrees before allocation.
 
+### Documentation
+- Streamlined the crate README and documentation index.
+- Removed the obsolete research-claim policy document.
+- Updated the observatory documentation link and release label.
+
 ## v0.2.1 - 2026-06-05
 
 ### Added

docs/verification_guide.md

@@ -1,6 +1,6 @@
 # Verification Guide
 
-This guide reproduces every large-domain claim in `power_house` v0.2.1.
+This guide reproduces every large-domain proof mode in `power_house` v0.2.2.
 
 ## Requirements
 

publicpower/index.html

@@ -79,7 +79,7 @@
 
       <div class="rail-links">
         <a href="https://github.com/JROChub/power_house/blob/main/docs/verification_guide.md">REPRODUCE</a>
-        <a href="https://github.com/JROChub/power_house/blob/main/docs/research_claim.md">CLAIM STANDARD</a>
+        <a href="https://github.com/JROChub/power_house/blob/main/docs/security_model.md">SECURITY MODEL</a>
       </div>
     </aside>
 
@@ -141,7 +141,7 @@ <h1>POWER HOUSE</h1>
         <div><span>ROUND</span><b id="round-value">0 / 70</b></div>
         <div><span>CLAIM</span><b id="claim-value">WAITING</b></div>
         <div><span>DIGEST</span><b id="digest-value">PENDING</b></div>
-        <div><span>RELEASE</span><b>v0.2.1</b></div>
+        <div><span>RELEASE</span><b>v0.2.2</b></div>
         <div><span>ENGINE</span><b>RUST + PYTHON</b></div>
       </div>
     </section>