# V8-001 evidence pack — current contract/document drift integrity

## Work-package charter

- **Task ID:** `V8-001`
- **Owner:** Yemaya case-contract and portfolio audit-integrity maintainers;
  implementation owner: Elikem Agudogo
- **Accountable product:** V8 Ariadne/Yemaya
- **Priority:** P0
- **Target milestone:** 2026-07-15 SOTA gap-closure program
- **Risk tier:** High contract/runtime and generated-document drift risk
- **Dependencies:** Current V5 public headers, the V8 target generator, V8
  documentation drift verifier, and the case-contract/engine/compiler/verifier
  packages
- **Affected schemas and content slots:** Generated V5 target TypeScript
  contract and V8 documentation gate semantics; no production content slot or
  placed artifact changed
- **Rollout strategy:** Regenerate from the authoritative headers, inspect the
  semantic diff, and admit the result only when the drift verifier and all
  dependent package tests pass
- **Rollback strategy:** Revert the generator and generated target together;
  never retain a generated file that differs from a clean generator run
- **Evidence-pack location:** This file

## Closure mapping

The original regeneration ran at repository HEAD
`a0bf7555000895ff3df5d3f68bfda5588533c4be` on `Elikems-MacBook-Air.local`. The
observed difference was only the generator's `/* eslint-disable */` banner; enum
and type semantics were identical. Commit
`9e25809ac2ccb1f704bebec200e05d919761fe8b` recorded that disposition, and commit
`9ef6f5768c3fde41a4c6104a646d3edd94f77390` made the generator output lint-stable
so a commit hook could not recreate permanent drift.

The package therefore closes the four ledger requirements without claiming an
Unreal execution:

1. the authoritative generator ran and the semantic diff was reviewed;
2. the docs-drift gate plus all four dependent package suites passed;
3. only the intended, semantics-preserving generated output was committed; and
4. the command, source identity, host, generator identity, and outputs are
   retained here and in the two implementation commits.

V8 has no standalone `.uproject`, so no owning UE project was inferred and no
engine, cook, placement, or media evidence is claimed.

## Current verification record

The refresh ran against source commit `649ae21ae3c44c9c8e259067674348e9ad51b205`
on `app-dev-server`, Linux `6.8.0-134-generic` x86_64, Node.js `v24.15.0`, pnpm
`10.25.0`, Git `2.43.0`, and Vitest `4.1.7`. It used no model/provider
credentials.

| UTC interval                                      | Exit | Command and result                                                                                                                                                                                                                                                           |
| ------------------------------------------------- | ---: | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| 2026-07-29T11:09:19.776Z–2026-07-29T11:09:25.736Z |    0 | `pnpm --dir libs/yemaya/case-contracts exec vitest run --config vitest.config.ts --maxWorkers=1` (18/18), then the equivalent package-local commands for `case-engine` (22/22), `case-compiler` (11/11), and `case-verifier` (28/28)                                         |
| 2026-07-29T11:09:09.425Z diagnostic               |    1 | The first root-CWD package-test attempt found no files because these configs resolve `src/**` from their package directory. The corrected package-local commands above are the admitted results; the failed discovery attempt is not hidden or counted as a product failure. |

`node scripts/verify-v8-docs-drift.mjs` also passed in the first refresh,
reporting that contracts, package graph, and gate semantics were intact. The
final evidence-admission verification reruns that command and records the
publication result in this change's Git/CI history.

## Adversarial, artifact, and authority evidence

- The drift verifier compares regenerated output and rejects source/header
  mismatch. The historical lint-hook oscillation is the negative fixture: the
  old banner-producing generator could not remain clean after lint, while the
  corrected generator is idempotent.
- Dependent contract, engine, compiler, and verifier suites provide unit,
  contract, and integration coverage. E2E UI, accessibility, performance,
  provider, and Unreal avenues are inapplicable because this package changes no
  runtime route, user flow, provider request, or placed engine artifact.
- No policy requires a human release signature for a semantics-preserving
  generated-contract repair. The named implementation owner performed the
  semantic review; no independent human approval is fabricated.
- No task-local external blocker remains. Broader V8 authored-quality,
  real-provider, Unreal placement, player-study, and canary claims remain owned
  by V8-004/V8-005.

| Current artifact                                        | SHA-256                                                            |
| ------------------------------------------------------- | ------------------------------------------------------------------ |
| `libs/yemaya/case-contracts/tools/gen-v5-target.mjs`    | `ddc8c157fc478ed2c3bf0e3bda870263205a9eddc58b45ac0f9d48935902c185` |
| `libs/yemaya/case-contracts/src/v5-target.generated.ts` | `ce808f3dcc834dba3a1bba607ca5309e7abf5f04d9d7b8d46c150981563d5c73` |
| `scripts/verify-v8-docs-drift.mjs`                      | `91f0bbc02e9a265680774991acd8114aeebe660cf555041a76d82a7510b3cdda` |

No source/canon/policy/rubric version, release verdict, screenshot, runtime
placement, or media artifact changed in this evidence-only publication. The new
completed-work-package admission verifier derives the package's evidence status
from the checked ledger state and this task-specific path; no generated green
status was hand-authored.
