# Bundle Status Guide — djat-poc-20260602

**Audience:** Tricia Wang, AAIS PoC committee, and any offline verifier  
**Encoding pathway:** [`Collaboration.Meta.EncodeBundleStatus@v1`](collaboration-pathways/pathways/Collaboration.Meta.EncodeBundleStatus.v1.yaml)  
**PathwayRun:** `pr_poc_status_vocabulary_clarity`  
**Pattern:** [`Pattern.CollaborationBundle.StatusVocabulary`](collaboration-pathways/patterns/Pattern.CollaborationBundle.StatusVocabulary.yaml)  
**Canonical machine index:** [`collaboration-pathways/meta/bundle-status.v1.yaml`](collaboration-pathways/meta/bundle-status.v1.yaml)

This bundle uses the word **status** in several independent layers. They must not be conflated.

---

## Status at a glance (this instance)

| Layer | Field | Current value | What it means for you |
|-------|--------|---------------|------------------------|
| **Integrity** | `verify` | Run command below | Bytes match manifest + signature (binary OK / fail) |
| **Bundle lifecycle** | `collaboration_status` | `ASSEMBLED` | Feedback bundle issued; proof experiments still open |
| **Investigation** | `investigation_status` | `pending` | Open questions not yet closed |
| **Hypothesis registry** | `hypothesis_registry_status` | `pre-registered` | All H-POC* filed before proof; none evaluated yet |
| **Reciprocation contract** | `reciprocation_required` | `false` | No return bundle required from AAIS |
| **Policy validation** | `h_poc_validate_status` | `design_pending` | H-POC-VALIDATE loop encoded, not executed; sole signatory has not confirmed |
| **Spec revision ref** | `spec_revision_ref` | `rev` | PoC architecture cite target: v0.1.0-rev ([`canon/POC_STANDARD_MANIFEST.yaml`](canon/POC_STANDARD_MANIFEST.yaml)); base = analysis lineage anchor |

**Verify integrity (anyone):**

```bash
python3 tools/collaboration-bundle/sign_bundle.py verify collaboration/20260602-160000
```

Expected: `verify: OK` — this does **not** mean the committee endorsed the feedback.

---

## Layer 1 — Verify (binary, cryptographic)

| Result | Meaning |
|--------|---------|
| `verify: OK` | Every file matches SHA-256 in `CONTENT_MANIFEST.yaml`; Ed25519 signature over `bundle_root_hash` checks out |
| verify fails | Tampering, drift, or incomplete manifest — do not trust contents |

- **Authority:** none — any reader with `python3`
- **Proves:** byte integrity since last seal
- **Does not prove:** claims are true, experiments ran, committee acceptance, or intent

Aligns with the PoC draft **verification-vs-validation** boundary ([`executive-summaries/PoC_Standard_v0.1.md`](executive-summaries/PoC_Standard_v0.1.md)): cryptography cannot prove intent.

**Pathway:** [`Collaboration.Bundle.VerifyBundle@v1`](collaboration-pathways/pathways/Collaboration.Bundle.VerifyBundle.v1.yaml)

---

## Layer 2 — Hypothesis registry (`pre-registered`)

All experiments in [`collaboration-pathways/test/HYPOTHESES.md`](collaboration-pathways/test/HYPOTHESES.md) are **written before proof runs** — success criteria fixed in advance.

| Registry state | Meaning |
|----------------|---------|
| `pre-registered` | Filed; investigations not yet run (now) |
| (per hypothesis) `not_run` | See [`proof-results/index.yaml`](proof-results/index.yaml) |

**Pathway:** [`Collaboration.Investigation.PreRegisterHypotheses@v1`](collaboration-pathways/pathways/Collaboration.Investigation.PreRegisterHypotheses.v1.yaml)

**Note:** `pre-registered` ≠ bundle `ASSEMBLED` ≠ `verify: OK`.

---

## Layer 3 — Investigate hypotheses (graded, per experiment)

Each H-POC* is a falsifiable experiment. Outcomes are **per hypothesis**, not one bundle-wide binary.

| Outcome | Meaning | Recorded in |
|---------|---------|-------------|
| `not_run` | Not yet executed | [`proof-results/index.yaml`](proof-results/index.yaml) |
| `confirmed` | Success criteria met | `proof-results/unilateral/<id>.yaml` |
| `falsified` | Structural failure | same; may drive `INVALIDATED` |
| `inconclusive` | Reciprocal-only or blocked | same; never `INVALIDATED` for invitation bundles |
| `design_pending` | Encoded but not executed (H-POC-VALIDATE) | hypothesis + PathwayRun `DESIGNED` |

**Authority:** **unilateral** — Originator or any party may run experiments and publish proof without counterparty permission.

**Pathways:** [`Collaboration.Proof.RunUnilateralExperiment@v1`](collaboration-pathways/pathways/Collaboration.Proof.RunUnilateralExperiment.v1.yaml) → [`Collaboration.Investigation.SealOrInvalidateBundle@v1`](collaboration-pathways/pathways/Collaboration.Investigation.SealOrInvalidateBundle.v1.yaml)

---

## Layer 4 — Validate the bundle (policy sense)

**H-POC-VALIDATE** is a stronger claim than `verify: OK` or confirming individual H-POC1..10:

> The collaboration-bundle format works as a **cryptographic context anchor** for dynamic model updates.

| Step | Evidence | Authority |
|------|----------|-----------|
| Dynamic update loop | [`assets/validation-proof/`](assets/validation-proof/) | Technical execution + PathwayRuns |
| Re-seal | `verify: OK` on enlarged bundle | Anyone can check |
| **Confirm validation** | `sole-signatory-confirmation.json` | **Tricia Wang** only — see [`bundle-validation-policy.v1.yaml`](collaboration-pathways/meta/bundle-validation-policy.v1.yaml) |

**Today:** loop is `design_pending` — integrity-verifiable, **not yet policy-validated**.

**Pathways:** [`Collaboration.Validation.DynamicUpdateProofLoop@v1`](collaboration-pathways/pathways/Collaboration.Validation.DynamicUpdateProofLoop.v1.yaml), [`Collaboration.Validation.SoleSignatoryConfirm@v1`](collaboration-pathways/pathways/Collaboration.Validation.SoleSignatoryConfirm.v1.yaml)

Policy changes only via recorded PathwayRun (`non_delegable_acts: change_sole_signatory`).

---

## Layer 5 — Bundle lifecycle (aggregate fate)

| `collaboration_status` | Meaning |
|------------------------|---------|
| `ASSEMBLED` | Repo complete; investigations open (**now**) |
| `SEALED` | Sufficient unilateral hypotheses confirmed; investigation resolved |
| `INVALIDATED` | A structural falsifier fired |
| `INCONCLUSIVE` | Reciprocal-only hypotheses unanswered — **not a failure** |

For this feedback bundle: **`SEALED` is reachable without any AAIS reply**; missing reciprocation never yields `INVALIDATED`.

**Pathway:** [`Collaboration.Investigation.SealOrInvalidateBundle@v1`](collaboration-pathways/pathways/Collaboration.Investigation.SealOrInvalidateBundle.v1.yaml)

---

## Reciprocation contract

**`reciprocation_required: false`** — AAIS is not required to assemble a return bundle. Reading, verifying, and optionally running unilateral experiments is enough. A reciprocal reply is welcome but optional ([`Collaboration.Reciprocation.AssembleReturnBundle@v1`](collaboration-pathways/pathways/Collaboration.Reciprocation.AssembleReturnBundle.v1.yaml)).

**Journey:** [`Experience.Collaboration.OpenInvitation@v1`](collaboration-pathways/pathways/Experience.Collaboration.OpenInvitation.v1.yaml)

---

## Authority boundary matrix

| Question | Who may assert it | Mechanism | Delegable? |
|----------|-------------------|-----------|------------|
| Are the bytes intact? | Anyone | `sign_bundle.py verify` | N/A |
| Did hypothesis H-POC*N* succeed? | Investigator (unilateral) | `proof-results/unilateral/H-POC*.yaml` | Yes |
| Is the context-anchor thesis demonstrated? | Executor + evidence | H-POC-VALIDATE + `assets/validation-proof/` | Per gate profile |
| Is the bundle **considered validated** for AAIS? | **Sole signatory only** | policy + confirmation artifact | **No** |
| Who may change validation policy? | Sole signatory (or successor) | PathwayRun SoleSignatoryConfirm | **No** |
| Does AAIS owe a return bundle? | Contract | `reciprocation_required: false` | N/A |

### Explicit non-claims

- `verify: OK` does **not** mean Tricia endorsed the feedback
- Confirming H-POC1 does **not** mean H-POC-VALIDATE ran
- Sole-signatory confirmation is **validation of acceptance criteria**, not a substitute for cryptographic verify

Formal encoding: Pathways `gate_profile` / `non_delegable_acts` (RIS §4.8) in [`Collaboration.Validation.SoleSignatoryConfirm@v1`](collaboration-pathways/pathways/Collaboration.Validation.SoleSignatoryConfirm.v1.yaml).

---

## Layer 6 — Spec revision reference (`spec_revision_ref`)

PoC architecture exists in two **v0.1.0** snapshots (same version label; not a version bump):

| Value | PDF | Use when |
|-------|-----|----------|
| `rev` | [`assets/canon/poc-standard-architecture-v0.1.0-rev.pdf`](assets/canon/poc-standard-architecture-v0.1.0-rev.pdf) | **Current reference** for forward edits and executive summaries |
| `base` | [`assets/origin/documents/074ca8a4-7b74-47b3-928c-4b29f89dc99c.pdf`](assets/origin/documents/074ca8a4-7b74-47b3-928c-4b29f89dc99c.pdf) | **Analysis lineage anchor** — comprehensive/strategic PDFs remain valid against base |

Canonical index: [`canon/POC_STANDARD_MANIFEST.yaml`](canon/POC_STANDARD_MANIFEST.yaml). Delta: [`sidecars/poc-v0.1.0-revision-delta-report.md`](sidecars/poc-v0.1.0-revision-delta-report.md).

**Pathways:** H-POC-REV-1..4 in [`collaboration-pathways/test/HYPOTHESES.md`](collaboration-pathways/test/HYPOTHESES.md).

---

## Proof slots (two directories)

| Directory | Purpose |
|-----------|---------|
| [`proof-results/`](proof-results/) | Per-hypothesis unilateral investigation returns (H-POC1..10, PC-POC-*) |
| [`assets/validation-proof/`](assets/validation-proof/) | H-POC-VALIDATE dynamic-update loop proof (policy validation) |

---

## Lifecycle diagram

```
ASSEMBLED → SEALED | INVALIDATED | INCONCLUSIVE
     ↑
  (issue bundle — now)
```

Investigations feed fate via [`proof-results/index.yaml`](proof-results/index.yaml) and seal evaluation pathway.

---

*Instance playbook: [`collaboration-pathways/APPLICATION_PLAYBOOK_POC_INSTANCE.md`](collaboration-pathways/APPLICATION_PLAYBOOK_POC_INSTANCE.md)*