Eve library

V1–V10 content-coverage seed registry report

Other

Revision 1

On this page

Generated mechanically from repository source under COV-002 on 2026-07-27. This report is a source-backed seed with complete canonical slots for the selected V1 launch scope. It is not a claim of full portfolio coverage.

Day-one registration truth#

  • Registry rows: 7549
  • Registered source facts: 69
  • Unregistered rows requiring migration: 7480
  • Complete canonical COV-001 slots: 4
  • Incomplete scheduled-slot candidates: 0
  • Reviewed V1 surface classifications: 28
  • Tool/access paths: 28; content requirements derived from that catalog: 0
  • Unresolved rows: 7480; owner assigned: 7480; owner missing: 0

The 28 frozen V1 generation surfaces are entitlement-backed tool/access facts. Each is linked to its exact generation-surface capability, introducing tier, product shell, and allowlist source. None counts as a filled content artifact or as evidence that V1 has zero content requirements. The four live V1 autonomy categories are bound to the authoritative selected-launch manifest and complete canonical slots. They are the selected V1 content scope, not full portfolio coverage or proof that any artifact is generated, reviewed, placed, or shipped.

Extracted ledger requirements#

Product Included Launch/bootstrap Checked launch Unchecked Blocked
V1 1694 1694 1677 2 15
V2 2256 2219 2023 92 141
V3 520 520 480 6 34
V4 1235 1229 1201 2 32
V5 999 994 844 124 31
V6 224 223 215 1 8
V7 130 129 54 24 52
V8 84 84 81 0 3
V9 42 34 31 7 4
V10 282 282 241 11 30

All P0/bootstrap and P1/launch checkboxes are included, even when checked. Every unchecked or blocked checkbox is included regardless of phase. Checked post-launch rows outside that scope are intentionally excluded.

V8/V9 contracts and product placement#

  • Gate-contract rows: 29 (canonical and implementation-alternate contracts are both retained).
  • Required-artifact rows: 16.
  • Placement-target rows: 6.
  • Exact duplicate groups: 11; contradiction/migration groups: 3.

The reviewed gate migration rule resolves the V8/V9 ordinal conflicts by semantic name/component, not gate number. It does not delete either source.

Ownership and claim boundary#

Every unresolved or unregistered row is assigned to team:oshun-content-coverage-migration with escalation oncall:oshun-platform. That is migration accountability, not an invented product-content owner. Canonical slot owner, locale, audience, quantity, freshness, pipeline, rights, accessibility, placement, risk, and lifecycle values remain missing until an authoritative source supplies them.