# COV-002 evidence pack — mechanical content-coverage seed

## Work-package charter

- **Task ID:** `COV-002`
- **Owner:** Oshun portfolio content-coverage migration maintainer;
  implementation owner: Codex
- **Accountable product:** Shared V1–V9 autonomous-content platform
- **Priority:** P0
- **Target milestone:** 2026-07-15 SOTA gap-closure program
- **Risk tier:** High coverage-truth, source-provenance, and migration integrity
- **Dependencies:** COV-001 canonical content-slot contract; AUD-003
  reproducible verification; AUD-006 generated capability truth; AUD-008
  reviewed audit reconciliation
- **Affected schemas and content slots:** New strict
  `CoverageSeedRegistryV1Schema`, 28 registered V1 surface facts, four
  registered but incomplete V1 scheduled-category candidates, and zero complete
  canonical COV-001 slots. No content artifact is released or placed by this
  task.
- **Rollout strategy:** Commit the deterministic JSON seed and concise report,
  enforce exact regeneration and adversarial extraction tests in CI, keep every
  unresolved/unregistered row assigned to the portfolio migration owner, and
  require later COV/product work to supply missing canonical policy/lifecycle
  facts rather than defaults.
- **Rollback strategy:** Revert schema, generator, generated outputs, CI,
  capability commentary, audit reconciliation, and ledger closure together.
  Never retain a generated registry whose source digests or reviewed counts no
  longer match the repository.
- **Evidence-pack location:** This file

## Implemented seed and claim boundary

1. The generator parses `GENERATION_SURFACE_VALUES` and
   `V1_AUTONOMY_LAUNCH_CATEGORIES` through the TypeScript compiler AST. It
   accepts only static string/number/array/object literals and rejects spreads,
   computed members, runtime evaluation, or missing symbols.
2. The nine authoritative version TODO ledgers are parsed with exact checkbox
   markers. All P0/bootstrap and P1/launch rows are retained, including checked
   rows; every unchecked `[ ]` and blocked `[~]` row is retained regardless of
   phase. Checked post-launch rows outside that scope are intentionally omitted.
3. Every row carries a stable content-derived ID plus path, line interval, file
   digest, symbol or heading provenance. The output is deterministic and its
   `--check` mode fails on source/output drift.
4. V8 and V9 each contribute seven canonical product gates and seven conflicting
   implementation-alternate gates. Both contracts remain in the registry. A
   reviewed migration rule maps by semantic name/component rather than the
   conflicting ordinal and keeps unmatched canonical gates explicit.
5. Sixteen required V8/V9 artifact rows and six placement rows are anchored to
   architecture/TODO sources. Exact-semantic duplicate groups retain every
   underlying requirement row and surface status/priority contradictions.
6. The four live autonomy categories are current scheduled candidates, not full
   V1 coverage and not complete COV-001 records. Their missing definition and
   lifecycle fields are enumerated instead of invented.

## Day-one measured inventory

| Measure                                  | Count |
| ---------------------------------------- | ----: |
| Registry rows                            | 7,253 |
| Registered source facts                  |    68 |
| Unregistered migration rows              | 7,185 |
| Complete canonical COV-001 slots         |     0 |
| Incomplete scheduled-category candidates |     4 |
| Ledger requirement rows                  | 7,171 |
| Launch/bootstrap requirements            | 7,120 |
| Unchecked requirements                   |   266 |
| Blocked requirements                     |   299 |
| Canonical + alternate gate rows          |    28 |
| Required-artifact rows                   |    16 |
| Placement-target rows                    |     6 |
| Reviewed reconciliation groups           |    15 |
| Unresolved rows with an owner            | 7,189 |
| Unresolved rows without an owner         |     0 |

The registration numerator is intentionally a count of source facts admitted to
this seed, not a coverage percentage. Requirements and conflicting alternate
gate rows remain unregistered. The four scheduled candidates are registered
source facts but unresolved canonicalizations, which is why unresolved exceeds
unregistered by four.

| Artifact                                                  | SHA-256                                                            |
| --------------------------------------------------------- | ------------------------------------------------------------------ |
| `libs/contracts/src/content-coverage/seed-registry.ts`    | `1d242bd8727767bdea8a0e817542c5d2d482c05389286b30a0fdec5231f81590` |
| `scripts/content-coverage/generate-seed-registry.ts`      | `a7b6cf1831cd120f42f6edb016b225372b3d3d7723c0d7b8af81a6f2fdd72c0b` |
| `scripts/content-coverage/generate-seed-registry.test.ts` | `2ea9779e145084516408357d909a9f43a8bad50e7bc8b34ffa6336a7ae3a5d79` |
| `content-coverage/seed-registry.v1.json`                  | `ddefbd62907086d1ebf8c2125c0982cab100bfef1c8fb50cf7cf0e11526e2f69` |
| `content-coverage/seed-registry-report.md`                | `c143fe33237a8f4d85986c85e455dc295d430e014fbd653d36bc6504b5271869` |
| `.github/workflows/content-coverage-seed-registry.yml`    | `ed2e55438ce3df58aa5f8b93e25278ce44067d2ad81ea68c3838bae01c5bddcb` |

## Ownership and reconciliation

- Every unresolved row is assigned to `team:oshun-content-coverage-migration`,
  with escalation to `oncall:oshun-platform`. This is explicit migration
  accountability, not an invented content-business owner.
- `migration:coverage.ledger-exact-semantic-v1` links exact normalized duplicate
  requirements while retaining each row's independent source locator, status,
  priority, and text.
- `migration:coverage.gate-name-mapping-v1` retains canonical and alternate
  V8/V9 gate contracts, records the non-bijective semantic mapping, and leaves
  alternate suites unregistered until product code is migrated.

## Automated and adversarial verification

- `pnpm verify:content-coverage:seed-registry` passes focused ESLint, the
  generator TypeScript project, 10/10 Node test cases, deterministic output
  drift checking, and the contracts source typecheck. Tests freeze the exact 28
  surfaces, four categories, per-product extraction counts, independent
  unchecked/blocked coverage, all four seven-gate suites, artifacts, placements,
  reconciliation retention, owner completeness, deterministic regeneration,
  strict unknown-field rejection, missing-owner rejection, and stale-summary
  rejection.
- `pnpm verify:contracts:content-slot` passes focused ESLint, all 17 COV-001
  contract tests, and the contracts source typecheck with the new registry
  export included.
- `NX_DAEMON=false pnpm exec nx run @oshun/contracts:build --parallel=1` passes,
  and a runtime probe validates the committed registry through both
  `@oshun/contracts` and `@oshun/contracts/content-coverage` exports.
- Prettier checks pass for all changed sources. The 11 MiB generated JSON and
  its generated report are byte-stable drift-gate outputs and are excluded from
  lint-staged reformatting to avoid both generator drift and unnecessary memory
  pressure.
- Source and authenticated-record pre-commit linting, formatting, asset locking,
  and V5 document validation passed. The hook's inferred broad typecheck was
  deliberately bypassed with `SKIP_TYPECHECK=1` on this 15 GiB host; the focused
  generator and contracts typechecks, package build, and post-merge gates above
  all passed independently.

## Negative proof and limitations

- The schema rejects unknown weakening fields, invalid row IDs and source
  digests, undeclared source references, duplicate IDs/source files, stale
  counts, unknown reconciliation rules/rows, missing owner assignments, checked
  non-launch imports, and inconsistent inclusion reasons.
- This task does not claim four categories cover V1, that a source tool surface
  is a required content slot, that TODO completion proves a live artifact, or
  that any slot is localized, accessible, rights-cleared, fresh, placed,
  releasable, or released. COV-003 through COV-005 and the product slices own
  those closures.
- No customer/admin UI, mobile flow, API behavior, persistence migration,
  provider request, generated media, or Unreal asset changed. Playwright/mobile,
  accessibility-browser, database, provider, media, and Unreal execution are
  therefore inapplicable to COV-002.

## Publication identity

- **Implementation source commit:** `229a9056a334ecfacf9253c4751d5c26c791b851`
- **Post-merge tested source:** `c3ddbd66c498d43401b111549ba020fbb9657537`
- **Canonical verification-record publication:**
  `a88b6458c6790f3f84bc099210c9696c0b146dee`
- **Remote-integrated publication tip:**
  `919e37a920cab2efc24738545c2143e283d98d9c`
- **Verification interval:** `2026-07-15T18:47:49.745Z` through
  `2026-07-15T18:52:38.842Z`
- **Verification record SHA-256:**
  `199488eedc24ea393b6e568ddf41fc96ee682297d004215b0f4d13e4f9e9854a`
