# Tri-Context Convergence — Weave × PoC × MikeOSS

**Type:** tri-context cross-register design  
**Emerged in:** `djat-poc-20260602` (`djat_x_poc`)  
**Machine-readable:** [`collaboration-pathways/meta/tri-context-cross-register.v1.yaml`](../collaboration-pathways/meta/tri-context-cross-register.v1.yaml)  
**Cross-publish protocol:** [`Collaboration.Convergence.CrossPublishSubstrate@v1`](../collaboration-pathways/pathways/Collaboration.Convergence.CrossPublishSubstrate@v1.yaml)  
**Flagship hypothesis:** **H-CONVERGE-TRI-1**

Related: [`convergence-poc-lcp-mikeoss-cross-register.md`](convergence-poc-lcp-mikeoss-cross-register.md) (PoC × MikeOSS × LCP two-up) · [`lcp-experiment-designs-legal-commons.md`](lcp-experiment-designs-legal-commons.md)

---

## The three interlocking contexts

Three collaboration bundles form an **interlocking triangle**: each is a sealed (or dual-domain) convergence repository; none subsumes the others. Convergence is **multi-dimensional** and **hash-linked**.

| Context | Channel | Repo | Lineage | Primary contribution |
|---------|---------|------|---------|----------------------|
| **MikeOSS** | `djat-mikeoss-20260528` | `djat_x_mikeoss` | 5th instance | Legal-AI **assay**: citation verify-first, reproducible benchmark, attested RunManifest |
| **PoC feedback** | `djat-poc-20260602` | `djat_x_poc` | 6th instance | AAIS PoC feedback, **dynamic update proof loop**, **LCP emergence** (`lcp-pathways/`), context anchor thesis |
| **Weave genesis** | `project-weave-genesis-20260620` | `djat_kevintriplett_hierophantos` | 8th instance | Cross-project **governance**, substrate **divergence/convergence**, composed **weaves**, dual-domain seal+ledger |

Weave's manifest explicitly lists MikeOSS and PoC as parent bundles. PoC cross-registers MikeOSS for assay×LCP convergence and now cross-registers Weave for governance and substrate patterns. MikeOSS remains the **assay invitation** anchor; Weave is the **multi-repo coordination** anchor; PoC is where **LCP + tri-context encoding emerged**.

---

## Interlock diagram

```mermaid
flowchart TB
  subgraph MO [MikeOSS — assay]
    MO1[H-MO1 Citation]
    MO3[H-MO3 RunManifest]
    MO6[H-MO6 gate_profile crosswalk]
  end

  subgraph POC [PoC — provenance + LCP]
    VAL[H-POC-VALIDATE]
    LCP[lcp-pathways]
    TRI[tri-context descriptor]
    XREF[TripleHashEvidenceSandwich]
  end

  subgraph WV [Weave — governance + substrate]
    W001[H-WEAVE-001 substrate divergence]
    STREAM[Weave.Stream.Weave]
    QUERY[Weave.Query.Convergence]
    DUAL[dual-domain compact + ledger]
  end

  MO3 --> XREF
  LCP --> XREF
  VAL --> TRI
  W001 --> STREAM
  STREAM --> TRI
  QUERY --> TRI
  MO6 --> LCP
  DUAL -.->|informs live cross-publish| TRI
```

**Reading the diagram:** Solid arrows are evidence-type dependencies. The dashed line from Weave dual-domain policy to tri-context is **operational**: live session ledgers (Weave) and single-domain seals (PoC, MikeOSS) can coexist if cross-publish uses pointers + optional verbatim copies, not seal merge.

---

## Weave overlap and reuse (what PoC adopts)

### 1. Convergence Repository (`Pattern.ProjectCollaboration.ConvergenceRepository`)

**Weave inherits; PoC inherits; MikeOSS originated reference impl.**

Invariants reused everywhere:

- `copy_only_no_symlinks` — cross-published substrates are verbatim copies or pointer stubs
- `pre_registered_hypotheses_before_proof` — H-* filed before proof artifacts
- `bundle_sealed_or_invalidated_not_ambiguous` — no "maybe sealed" state

PoC **emerged** `Collaboration.Convergence.CrossPublishSubstrate@v1` as the minimal formal encoding of cross-repo substrate sharing under these invariants.

### 2. Substrate divergence vs convergence (notes-emergence model)

Weave documents **substrate-divergent** vs **identical-instantiation** pathways in `assets/notes-emergence-report.md` (Python vs Node PERSONAL_NOTES builds). Same crystal, different runtime substrates, shared canon candidates.

**PoC reuse:**

| Weave substrate concept | PoC / LCP analogue |
|-------------------------|-------------------|
| Substrate-divergent pathways | Legal-commons **process template forks** (H-LCP-4/5) |
| Identical-instantiation canon | Shared Pathway templates across dispute categories |
| Emergence compare report | `Weave.Report.Emergence.Compare` → future commons cohort compare |
| Plurality hedge belief | Multiple mediation process variants without premature merge |

### 3. Composed weaves (`Weave.Stream.Weave` + `Weave.Query.Convergence`)

Weave composes cross-project streams (e.g. `weave.notes_python_node_siblings`, `weave.seal_ledger_dual_domain_resolution`).

**PoC reuse:** Tri-context is a **composed weave** at design time:

- **Stream ID:** `weave.tri_context_poc_mikeoss_lcp`
- **Streams merged:** MikeOSS assay manifest + PoC LCP experiment registry + Weave governance patterns
- **Query:** `Weave.Query.CrossDomain@v1` — registry facet across three channels

Encoded formally in `Collaboration.Convergence.RegisterTriContextWeave@v1`, not by re-sealing Weave content into PoC.

### 4. Dual-domain hash policy (Weave-specific enhancement)

Weave separates **compact seal** (immutable technique + sidecars) from **ledger annex** (mutable session PathwayRuns). Kevin Triplett surfaced this tension; David Thomson encoded `dual-domain-hash-policy.v1.yaml`.

**PoC implication for cross-publish:**

- PoC and MikeOSS use **single-domain** seals today.
- Cross-publishing **convergence substrates** into Weave should target `sidecars/cross-published/` (compact) or pointer stubs, not mutable ledger annex, unless the substrate *is* a session PathwayRun.
- When a hypothesis **confirms**, publish proof pointer to compact domain; Weave collaborators append session runs separately.

### 5. Shared workspace session ledger

Weave mandates `Collaboration.WorkSession.Record@v1` per session. PoC does not require this yet but **benefits** when cross-domain work is live: record tri-context registration as a PathwayRun in each repo's ledger convention.

---

## Cross-publish protocol (best practice, minimally formal)

Assume collaborators **cross-publish** into each peer repository:

### When to publish

| Trigger | Substrate kind | What to publish |
|---------|----------------|-----------------|
| New divergence documented | `divergence` | Emergence report excerpt, experiment variant, substrate-divergent PathwayRun |
| Convergence sidecar or composed weave | `convergence` | Sidecar + `tri-context-cross-register.v1.yaml` or pointer stub |
| Hypothesis moves to `confirmed` | `hypothesis_proof` | `proof-results` row + artifact SHA-256 list |

### Where to publish (peer layout)

```
sidecars/cross-published/{source_channel}/pointer.v1.yaml   # minimal hash-linked stub
assets/cross-published/{source_channel}/                    # optional verbatim copies
proof-results/cross-published/{source_channel}/{H-ID}.yaml  # successful hypothesis pointer
```

### Minimal pointer stub schema

```yaml
schema: cross_publish_pointer.v1
source_channel: djat-poc-20260602
source_bundle_root_hash: "<hex at publish time>"
substrate_kind: convergence
published_at: "2026-06-11"
artifacts:
  - path: sidecars/convergence-tri-context-weave-poc-mikeoss.md
    sha256: "<computed at copy>"
hypothesis: H-CONVERGE-TRI-1
verify_command: "python3 tools/collaboration-bundle/sign_bundle.py verify <snapshot>"
```

### What we do **not** do

- Merge `bundle_root_hash` values into one super-hash
- Symlink peer repos into the sealed tree
- Claim Weave dual-domain verify satisfies PoC single-domain verify (or vice versa)

Pathway: [`Collaboration.Convergence.CrossPublishSubstrate@v1`](../collaboration-pathways/pathways/Collaboration.Convergence.CrossPublishSubstrate@v1.yaml)

---

## H-CONVERGE-TRI-1 — Flagship tri-context hypothesis

**When** Weave substrate convergence (H-WEAVE-001), MikeOSS attested RunManifest (H-MO3), and LCP-bound dispute process terms (H-LCP-4) each produce independently verifiable artifacts,

**and** each peer repo carries hash-linked cross-published substrates per CrossPublishSubstrate,

**then** an assessor can traverse three collaboration contexts and verify assay behavior, governance provenance, and legal terms **without** a unified seal or merged trust domain.

**Status:** `design_pending`  
**Depends on:** H-WEAVE-001, H-MO3, H-LCP-4, H-POC-VALIDATE (optional fourth dimension)  
**Extends:** H-CONVERGE-MO-LCP-1 (PoC × MikeOSS × LCP two-up)

---

## Anchor hashes (verify offline)

| Context | Verify command | `bundle_root_hash` |
|---------|----------------|-------------------|
| MikeOSS | `verify collaboration/20260528-130500` | `6a599273094263939be83f4bac2710a68c32715fe6cd5ff26a8af36508d2a4d4` |
| PoC | `verify collaboration/20260602-160000` | *(at seal)* |
| Weave compact | `verify collaboration/20260620-120000` | `a576d3f751c9e11e6317bcccf1b50b731d5268c8731d5951a06a61afa9647e94` |
| Weave ledger | `verify ... --mode ledger` | `ledger_head_hash: 83c7256ac34c0567358bc71620db032d072b838067619f3c5739e15c0d24114c` |

Descriptors: [`upstream-mikeoss-anchor.v1.yaml`](../collaboration-pathways/meta/upstream-mikeoss-anchor.v1.yaml) · [`upstream-weave-anchor.v1.yaml`](../collaboration-pathways/meta/upstream-weave-anchor.v1.yaml)

---

## Cross-publish actions (this encoding)

| Target repo | Action | Artifacts |
|-------------|--------|-----------|
| `djat_x_poc` | **Origin** (this document) | Full sidecar + pathways + meta descriptor |
| `djat_x_mikeoss` | Pointer stub (best practice) | `sidecars/cross-published/djat-poc-20260602/` |
| `djat_kevintriplett_hierophantos` | Pointer stub (best practice) | `sidecars/cross-published/djat-poc-20260602/` |

PoC verify does not require peer stubs; they are **social integrity + discoverability** layers consistent with ConvergenceRepository.

---

## Read order within tri-context work

1. This sidecar (triangle overview)
2. [`convergence-poc-lcp-mikeoss-cross-register.md`](convergence-poc-lcp-mikeoss-cross-register.md) — LCP × assay two-up
3. [`lcp-experiment-designs-legal-commons.md`](lcp-experiment-designs-legal-commons.md) — LCP experiment suite
4. Weave: `sidecars/seal-ledger-dual-domain.md`, `assets/notes-emergence-report.md` (upstream repo)
5. [`lcp-pathways/APPLICATION_PLAYBOOK_LCP.md`](../lcp-pathways/APPLICATION_PLAYBOOK_LCP.md)

---

*Pathway runs: `pr_weave_tri_crossregister`, `pr_cross_publish_substrate_protocol` · emerged in djat-poc-20260602*