# v-harness Version ↔ Project Matrix

This is the human-readable authority for which internal project used which
v-harness source version. `versions.json` carries the same positive
relationships for navigation and validation.

## Relationship Vocabulary

| Relationship | Meaning |
| --- | --- |
| `executed` | The project completed experiment runs using the pinned source line. |
| `vendored` | The project copied or derived a fixed subset of code/data; it does not import upstream at runtime. |
| `prepared_only` | The source was registered, audited or configured, but no confirmed completed run is claimed. |
| `deployment_only` | The version was deployed and acceptance-tested; this is not internal algorithm adoption. |
| `visualized` | Existing run evidence was normalized into a static viewer; no new experiment is implied. |
| `no direct dependency` | The project does not directly import, copy or bind to a v-harness source version. |

These labels describe source/evidence relationships. They are separate from the
`observed / adopted / modified / rejected` mechanism statuses in
`ADOPTION_LEDGER.md`.

## Version Timeline

| Version | Fixed source | Main tool-policy distinction | Lifecycle |
| --- | --- | --- | --- |
| Atomic Actions · v2.2 | `image2code-v2.2@e224610753529d5eae9a9589bd7485363f5ff1b6` | MCP perception plus explicit MCP `render/write/crop/snapshot/revert` doing actions | historical experiment source |
| Native Claude · v2.3 | `image2code-v2.3@e9c04d4b382beaa18dc96f1e1fded91eb942dd76` | MCP perception retained; mutation returns to native Claude `Bash/Write/Edit/Read` | historical research baseline |
| GLM v1 · v2.3.2 | `image2code-glm-v1@249c2bceedaf3c04f76ae3a899d91acbf8dc2641` | GLM-5.2 blind orchestration, Gemini perception and deterministic gate | active protected deployment |

## By Version

| Version | Project | Relationship | Evidence |
| --- | --- | --- | --- |
| Atomic Actions · v2.2 | Verification Loop V2 | `executed` | `../20260701-vdiff-image2code-v2-harness-comparison/README.md` and its completed L3 run records |
| Atomic Actions · v2.2 | v-harness Visual Trajectory Viewer | `visualized` | `../20260704-vdiff-vharness-visual-trajectory-viewer/README.md`; 13-case static package |
| Native Claude · v2.3 | Verification Loop V2 | `prepared_only` | `../20260701-vdiff-image2code-v2-harness-comparison/sources/registry.json`; source/condition prepared, no completed V2 v2.3 run claimed |
| Native Claude · v2.3 | Verification Loop V3 | `executed` | `../20260709-vdiff-image2code-v3-gate-score-evaluation/README.md`; 30 L3 cells and 180 audited L3 epochs |
| Native Claude · v2.3 | VeriHarness V0.1 | `vendored` | `../20260712-veriharness-v0-1/SOURCE_LINEAGE.md`; gate/config/backends and 13 cases copied at the fixed pin |
| GLM v1 · v2.3.2 | v-harness Upstream Manager | `deployment_only` | `README.md#acceptance-canary`; protected service and complete case9 canary artifacts |

## By Internal Project

| Internal project | Version relationship | Correct interpretation |
| --- | --- | --- |
| Verification Loop V2 | Atomic Actions v2.2 `executed`; Native Claude v2.3 `prepared_only` | V2 result pages are v2.2 experiments. A v2.3 registry entry is not a completed v2.3 experiment. |
| Verification Loop V3 | Native Claude v2.3 `executed` | V3 extra-hard and stability evidence is pinned to `e9c04d4b…`. |
| VeriHarness V0.1 | Native Claude v2.3 `vendored` | V0.1 is an independent internal harness with a documented fixed-source subset. |
| VeriHarness V0.2 | `no direct dependency` | V0.2 inherits research context only; it does not import v-harness prompt/config/code/data/artifacts. |
| Core Verification Loop V1 | `no direct dependency` | This line predates the versioned v-harness adoption mapping and is not assigned a v-harness source. |

## GLM Adoption Boundary

GLM v1 has a real protected workbook and a complete deployment canary, but no
Verification Loop or VeriHarness experiment currently binds to that source.
Blind orchestration, atomic perception and the deterministic gate remain
`observed` mechanisms unless an internal project records implementation or
experiment evidence in the adoption ledger.

## Maintenance Rule

When adding a version, add a new `versions.json` entry and update both directions
of this matrix. Never rewrite an old project's source identity merely because an
upstream branch moved. Every positive relationship must have a repository-local
evidence link.