# Self-Validating Experiments — PoC Feedback (H-POC-VALIDATE + H-POC1..H-POC10)

**Bundle channel:** djat-poc-20260602  
**Hypothesis registry:** pre-registered *(filed before proof; none evaluated yet)*  
**Reciprocation contract:** not required *(AAIS reply optional; unilateral experiments suffice)*  
**Bundle lifecycle:** ASSEMBLED *(see [BUNDLE_STATUS_GUIDE.md](../../BUNDLE_STATUS_GUIDE.md))*

*Investigation returns:* [`proof-results/index.yaml`](../../proof-results/index.yaml)  
*Encoded by:* [`Collaboration.Meta.EncodeBundleStatus@v1`](../pathways/Collaboration.Meta.EncodeBundleStatus.v1.yaml) (`pr_poc_status_vocabulary_clarity`)

---

## H-POC-VALIDATE — Singular bundle validation via dynamic update proof loop

**Investigation status:** design_pending  
**Effort:** S (design encoded; execution pending)  
**Pathway:** [`Collaboration.Validation.DynamicUpdateProofLoop@v1`](../collaboration-pathways/pathways/Collaboration.Validation.DynamicUpdateProofLoop.v1.yaml)  
**Sole signatory:** Tricia Wang (AAIS Society) — see [`bundle-validation-policy.v1.yaml`](../collaboration-pathways/meta/bundle-validation-policy.v1.yaml)

**This hypothesis alone can validate the entire collaboration-bundle design.**

### Loop

1. **Anchor** — Treat this sealed bundle as cryptographic context (`Collaboration.Bundle.CryptographicContextAnchor@v1`).
2. **Update** — Execute a full dynamic model update with provenance (`Model.Update.Apply@v1`), binding `upstream_context_anchor` to this bundle's `bundle_root_hash` and origin manifest.
3. **Prove** — Record PathwayRun + `model_update_provenance_json` + Aqua revisions.
4. **Return** — Write proof artifacts to [`assets/validation-proof/`](../assets/validation-proof/).
5. **Confirm** — Sole signatory attests the loop closed (policy mutable via `Collaboration.Validation.SoleSignatoryConfirm@v1`).
6. **Re-seal** — `verify: OK` on the enlarged bundle validates the anchor thesis.

### Success criterion

- Proof files present under `assets/validation-proof/` with SHA-256 in CONTENT_MANIFEST
- `model-update-pathway-run.json` references this bundle's context anchor
- Sole signatory confirmation recorded
- `python3 tools/collaboration-bundle/sign_bundle.py verify collaboration/20260602-160000` → **verify: OK**

### Why this matters for PoC

Demonstrates that the collaboration-bundle format is exactly the cryptographic context anchor PoC Provenance needs for dynamic model state and behavior — not a parallel invention.

---

## H-POC-REV-1 — PoC v0.1.0 revision ingested (dual canon)

**Investigation status:** confirmed  
**Effort:** S  
**Pathway:** [`PoC.Canon.IngestSpecRevision@v1`](../poc-pathways/pathways/PoC.Canon.IngestSpecRevision.v1.yaml)  
**PathwayRun:** `pr_poc_canon_ingest_rev`

Both PDF snapshots hashed in [`canon/POC_STANDARD_MANIFEST.yaml`](../canon/POC_STANDARD_MANIFEST.yaml); rev at `assets/canon/poc-standard-architecture-v0.1.0-rev.pdf`.

**Success:** Manifest present; base + rev SHA-256 recorded; `current_reference: rev`.

---

## H-POC-REV-2 — Executive summaries aligned to v0.1.0-rev domain model

**Investigation status:** confirmed  
**Effort:** S  
**Pathway:** [`PoC.Framework.ReconcileDomainModel@v1`](../poc-pathways/pathways/PoC.Framework.ReconcileDomainModel.v1.yaml)  
**PathwayRun:** `pr_poc_domain_reconcile`

**Success:** No executive summary lists Integrity/Boundary/Audit as PoC domains; five domains = Privacy, Portability, Authorization, Security, Identity; delta report linked.

---

## H-POC-REV-3 — Gap matrix reconciled for Authorization shift

**Investigation status:** confirmed  
**Effort:** XS  
**Pathway:** [`PoC.Framework.ReconcileDomainModel@v1`](../poc-pathways/pathways/PoC.Framework.ReconcileDomainModel.v1.yaml)

**Success:** [`poc-gap-matrix.v1.json`](../poc-pathways/data/poc-gap-matrix.v1.json) includes Authorization ↔ gate_profile row; domain rename impact documented.

---

## H-POC-REV-4 — Revision delta report (optional depth)

**Investigation status:** confirmed  
**Effort:** S  
**Pathway:** [`PoC.Analysis.RevisionDelta@v1`](../poc-pathways/pathways/PoC.Analysis.RevisionDelta.v1.yaml)  
**PathwayRun:** `pr_poc_rev_delta`

**Success:** [`sidecars/poc-v0.1.0-revision-delta-report.md`](../sidecars/poc-v0.1.0-revision-delta-report.md) complete with domain delta and stability anchors.

---

Each additional hypothesis below produces standalone value. Effort: XS = hours, S = a day or two.

---

## H-POC1 — Offline Aqua Tree verification of origin exports

**Investigation status:** not_run  
**Effort:** XS  
**Pathway:** PoC.Provenance.MapPathwaysAlignment@v1

Verify `assets/origin/ORIGIN_MANIFEST.yaml` SHA-256 entries against on-disk files. Compare derivative markdown hashes to sealed PDFs.

**Success:** `verify: OK` on all origin files; derivative-to-PDF linkage documented.

---

## H-POC2 — model_update_provenance field mapping

**Investigation status:** not_run  
**Effort:** S  
**Pathway:** Model.Update.Apply@v1

Draft a `model_update_provenance_json` block mapping RIS Appendix C fields to PoC model-update questions (who/what/when/where).

**Success:** YAML schema snippet accepted by one PoC committee reviewer as WD 1.0 input.

---

## H-POC3 — MSID registry substrate

**Investigation status:** not_run  
**Effort:** S  
**Pathway:** Model.Update.Apply@v1  
**Mini-workgroup:** WG-POC-1

Define how externally computed MSID (Merkle over weight shards) binds to PathwayRun provenance_records.

**Success:** One worked example with fake MSID hash in gap matrix row.

---

## H-POC4 — dynamism_band separate from autonomy

**Investigation status:** not_run  
**Effort:** XS  
**Pathway:** PoC.Framework.EvaluateExtension@v1

Document why PoC dynamism (model change rate) must not collapse into Pathways autonomy bands (orchestration oversight).

**Success:** Two-axis table in committee feedback notes.

---

## H-POC5 — Gate-profile manifest for trust disclosure

**Investigation status:** not_run  
**Effort:** S  
**Pathway:** PoC.Framework.EvaluateExtension@v1

Map PoC six-category trust assumptions to gate_profile manifest export format.

**Success:** Sample manifest JSON for one illustrative deployment.

---

## H-POC6 — PoC Evidence Object JSON Schema (JCS)

**Investigation status:** not_run  
**Effort:** S  
**Pathway:** PoC.Provenance.MapPathwaysAlignment@v1  
**Mini-workgroup:** WG-POC-4

Publish draft JSON Schema aligned with Pathways BuildManifest + provenance fields.

**Success:** Schema validates one Strategic Report gap row as evidence object.

---

## H-POC7 — Behavioral-envelope harness stub

**Investigation status:** not_run  
**Effort:** S  
**Pathway:** Model.Verify.Behavioral_Envelope@v1 (seed)

Define inputs/outputs for post-update behavioral verification loop.

**Success:** Pathway YAML stub in poc-pathways.

---

## H-POC8 — Analysis → PathwayRun bridge (bundle-local)

**Investigation status:** not_run  
**Effort:** S  
**Pathway:** PoC.Analysis.SynthesizeStrategicReport@v1  
**Mini-workgroup:** WG-POC-2

Confirm every origin derivative and deliverable PDF maps to a historical PathwayRun in [`pathway-runs/`](../pathway-runs/) with `is_historical: true`.

**Success:** ASSET_PROVENANCE.yaml complete; each deliverable has producing pathway + run.

---

## H-POC9 — Aqua signing for analysis derivatives

**Investigation status:** not_run  
**Effort:** S  
**Pathway:** Collaboration.Attestation.BindAquaTrees@v1  
**Mini-workgroup:** WG-POC-3

Attest one origin derivative with genesis + did:key via bundle Aqua trees (`tools/aqua/make_aqua_trees.js`).

**Success:** `.aqua.json` sidecar present; revision chain verifies offline.

---

## H-POC10 — Joint AAI+Pathways working group feasibility

**Investigation status:** not_run  
**Effort:** XS  
**Pathway:** PoC.Framework.EvaluateExtension@v1

Draft charter outline: scope, deliverables, assessor accreditation meta-pathways.

**Success:** One-page charter outline in committee feedback package.

---

## Bundle seal experiments

See also PC-1/PC-2 patterns in collaboration-pathways/test/ (from technique canon).

**PC-POC-1:** Unilateral — run H-POC1 + bundle verify without AAIS reply.  
**PC-POC-2:** Seal invalidation — modify one origin file post-seal; verify fails.

---

## LCP experiments — emerged in djat-poc-20260602

**Design sidecar:** [`sidecars/lcp-experiment-designs-legal-commons.md`](../sidecars/lcp-experiment-designs-legal-commons.md)  
**Cross-register (MikeOSS):** [`sidecars/convergence-poc-lcp-mikeoss-cross-register.md`](../sidecars/convergence-poc-lcp-mikeoss-cross-register.md)  
**Pathways package:** [`lcp-pathways/`](../lcp-pathways/)  
**Registry:** [`lcp-pathways/data/lcp-experiment-registry.v1.json`](../lcp-pathways/data/lcp-experiment-registry.v1.json)

---

## H-LCP-1 — Triple-hash evidence sandwich

**Investigation status:** design_pending  
**Effort:** XS  
**Pathway:** [`Legal.LCP.TripleHashEvidenceSandwich@v1`](../lcp-pathways/pathways/Legal.LCP.TripleHashEvidenceSandwich@v1.yaml)  
**PathwayRun:** `pr_lcp_experiment_designs`

One transaction cross-references LCP `atrHash`, collaboration `bundle_root_hash`, and run manifest hash; each verifies independently.

**Success:** `triple_hash_cross_reference.json` schema validated; three-domain offline verify documented.

---

## H-LCP-2 — LCP legal_context infusion

**Investigation status:** design_pending  
**Effort:** XS  
**Pathway:** [`Legal.LCP.InfuseLegalContext@v1`](../lcp-pathways/pathways/Legal.LCP.InfuseLegalContext@v1.yaml)

Optional `legal_context` block in collaboration-manifest with discovery URL, terms URL, atrHash, lcp_level.

**Success:** Manifest patch documented; bundle seal unchanged; discovery pattern matches LCP draft.

---

## H-LCP-3 — Authorization gate_profile × LCP level convergence

**Investigation status:** design_pending  
**Effort:** S  
**Pathway:** [`Legal.LCP.ConvergeMultiContext@v1`](../lcp-pathways/pathways/Legal.LCP.ConvergeMultiContext@v1.yaml)

Map PoC Authorization / `gate_profile` to LCP trust levels in gap matrix and convergence sidecar.

**Success:** Matrix or sidecar row links A0–A3 to LCP levels 1–4 without normative merge claim.

---

## H-LCP-4 — Mediation process as LCP terms artifact (flagship)

**Investigation status:** design_pending  
**Effort:** M  
**Pathway:** [`Legal.Commons.LongitudinalOutcomeLearn@v1`](../lcp-pathways/pathways/Legal.Commons.LongitudinalOutcomeLearn@v1.yaml)  
**PathwayRun:** `pr_lcp_experiment_designs`

Context-specific mediation/arbitration process published as hashable LCP JSON; Pathway template fork with attribution.

**Success:** Example process terms JSON + design PathwayRun; atrHash computation documented.

---

## H-LCP-5 — Cross-category legal commons learning

**Investigation status:** design_pending  
**Effort:** M  
**Pathway:** [`Legal.Commons.LongitudinalOutcomeLearn@v1`](../lcp-pathways/pathways/Legal.Commons.LongitudinalOutcomeLearn@v1.yaml)

Longitudinal outcome signals (settlement, duration, compliance) aggregated by `process_atr_hash` + category; fork lineage via Pathways.

**Success:** Registry row with ≥2 dispute categories; no PII in aggregate; fork attribution in PathwayRun ledger.

---

## H-CONVERGE-MO-LCP-1 — MikeOSS assay × PoC provenance × LCP dispute terms

**Investigation status:** design_pending  
**Effort:** M (depends on upstream H-MO3)  
**Pathway:** [`Legal.LCP.ConvergeMultiContext@v1`](../lcp-pathways/pathways/Legal.LCP.ConvergeMultiContext@v1.yaml)  
**PathwayRun:** `pr_lcp_mikeoss_crossregister`

Cross-registered experiment linking upstream `djat-mikeoss-20260528` (`bundle_root_hash` `6a599273094263939be83f4bac2710a68c32715fe6cd5ff26a8af36508d2a4d4`) with PoC context anchor and LCP terms. **Depends on possible outcomes** of H-MO1, H-MO2, H-MO3, H-MO6, H-MO8 (MikeOSS) and H-POC-VALIDATE, H-POC6 (PoC).

**Success (design):** Anchor descriptor + convergence sidecar + registry row *(current)*.  
**Success (convergence):** Attested MikeOSS RunManifest + LCP atrHash + PoC proof cross-linked via TripleHashEvidenceSandwich; multi-dimensional merge without unified seal.

**Tri-context extension:** See **H-CONVERGE-TRI-1** and [`sidecars/convergence-tri-context-weave-poc-mikeoss.md`](../sidecars/convergence-tri-context-weave-poc-mikeoss.md).

---

## H-CONVERGE-TRI-1 — Weave governance × MikeOSS assay × PoC LCP (tri-context)

**Investigation status:** design_pending  
**Effort:** M  
**Pathway:** [`Collaboration.Convergence.RegisterTriContextWeave@v1`](../collaboration-pathways/pathways/Collaboration.Convergence.RegisterTriContextWeave@v1.yaml)  
**Cross-publish:** [`Collaboration.Convergence.CrossPublishSubstrate@v1`](../collaboration-pathways/pathways/Collaboration.Convergence.CrossPublishSubstrate@v1.yaml)  
**PathwayRuns:** `pr_weave_tri_crossregister`, `pr_cross_publish_substrate_protocol`

Three interlocking collaboration contexts (MikeOSS 5th, PoC 6th, Weave genesis 8th) remain independently sealed. Convergence via hash-linked cross-publish of divergence/convergence substrates and hypothesis proof pointers. Reuses Weave `Stream.Weave`, substrate divergence model, and ConvergenceRepository invariants.

**Depends on:** H-WEAVE-001, H-MO3, H-LCP-4; extends H-CONVERGE-MO-LCP-1.

**Success (design):** Tri-context descriptor + Weave anchor + cross-publish protocol *(current)*.  
**Success (convergence):** Peer repos carry cross-published pointers; three-domain+ verify passes; optional composed weave `weave.tri_context_poc_mikeoss_lcp` in Weave ledger.