# v-harness Adoption Ledger

This ledger separates upstream observation from internal adoption. An entry is
not `adopted` until the named internal project contains implementation evidence.
Source-version usage is intentionally tracked in `VERSION_PROJECT_MATRIX.md`;
an `executed` or `vendored` source relationship does not automatically make
every mechanism in that source `adopted`.

| Upstream mechanism | Status | Internal target | Evidence / difference |
| --- | --- | --- | --- |
| Blind GLM orchestrator with vision delegated to atomic operations | observed | VeriHarness V0.2 research design | Useful separation of reasoning and perception; no internal implementation in this task. |
| `grep / inspect / transcribe / align / diff / inpaint` operation surface | observed | Verification Loop V3 and future VeriHarness versions | Existing internal tools overlap conceptually, but names and contracts are not imported. |
| Deterministic epoch-level geometry + visual gate | observed | VeriHarness evidence/controller design | Recorded as an upstream gate design, not proof that the same policy should be adopted. |
| Model-specific behavior in a skill, invariant perception kernel | observed | Future multi-artifact harness work | Candidate modularity principle; no image2svg/image2pptx expansion here. |
| Versioned run archive and workbook DB/debug/timeline surfaces | observed | Internal trajectory viewers | The deployed upstream workbook remains separate from internal normalized viewers. |
| Five-dimension frontend evidence package | observed | Future trajectory-management implementation | The separate frontend study covers overall data management, single-case detail, comparison, epoch detail and HTML replay; it contains no internal viewer code. |
| Event-driven HTML process replay | observed | Future trajectory-management implementation | v-harness events/frames/epochs are useful inputs, but the audited run proves they are not one-to-one; immutable identity and explicit event↔frame alignment are prerequisites. |
| Protected runtime wrapper and Quick Tunnel operations | adopted | v-harness upstream manager | Deployment-only local overlay; it does not change the upstream harness. |

Allowed status values are `observed`, `adopted`, `modified`, and `rejected`.