# V1-001 — Accountable V1 generation-surface coverage

Status: **selected V1 launch scope declared, registered, and scheduled; external
shipped-scope observation remains open**.

Implementation source: the task-scoped commit containing this evidence, the
strict contracts, the authoritative manifest, the deterministic generators, and
their generated records.

## Work-package charter

- **Task ID:** `V1-001`
- **Owner:** `team:oshun-v1-content`; source authority:
  `team:oshun-source-authority`; rights authority:
  `team:oshun-rights-authority`; provider authority:
  `team:oshun-model-operations`
- **Accountable product:** V1
- **Priority / milestone:** P0 selected-launch-scope accountability
- **Risk tier:** high false-coverage, unknown-content, rights, placement, and
  release-readiness risk
- **Dependencies:** COV-001 canonical slots, COV-002 seed registry, COV-003
  canonical director, COV-004 inventory, and COV-005 release reconciliation
- **Rollout:** consumers regenerate the seed, inventory, and V1 launch-coverage
  outputs. Tool surfaces remain non-content; generation remains deferred until
  the scheduled prerequisite frontier is satisfied.
- **Rollback:** revert the task-scoped implementation commit. The generated
  records are deterministic consequences of the reverted source.
- **Evidence pack:** this file and
  `content-coverage/v1-launch-coverage-report.md`

## Requirement disposition

| Ledger requirement                                                            | Implemented control surface                                                                                                                                                                                                                                                                                                                                                           | Closure state                                                       |
| ----------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------- |
| Map all 28 surfaces to actual required slots and full policy/lifecycle fields | All 28 frozen Isis entries have explicit `tool-access` mappings with `mappedSlotIds: []`; none is silently omitted or promoted to content. The separate selected-scope manifest declares the four actual launch slots with owner, modality, locale, quantity, freshness, accessibility, source/autonomy policy, placement, pipeline, gates, rights policy, risk, cost, and cycle cap. | **Closed by manifest, generated mapping, strict schema, and tests** |
| Identify and link tool/access paths without counting them as filled artifacts | Each entry retains its exact capability, tier, shell, allowlist source, and `countsAsContentRequirement: false` classification.                                                                                                                                                                                                                                                       | **Closed by contract, generated records, and tests**                |
| Register every remaining V1 launch requirement and blocker                    | `manifest:v1-selected-launch-content-v1` declares the exact four live autonomy categories as the complete selected scope. Each slot has source, rights, and provider blockers with a distinct accountable owner and executor.                                                                                                                                                         | **Closed for the selected launch scope**                            |
| Schedule missing/stale work through the canonical director                    | The generated dependency graph passes the canonical COV-003 scheduler. It schedules 12 prerequisite leaf jobs and defers all four generation jobs behind them.                                                                                                                                                                                                                        | **Closed by deterministic director plan and tests**                 |
| Prove zero unknown shipped V1 content at selected launch scope                | The repository has no independently authorized complete runtime/shipped observation. The release probe refuses to substitute an empty observation and COV-005 rejects an observed unknown artifact.                                                                                                                                                                                   | **Open pending external observation**                               |

The first four V1-001 checkboxes are closed for the explicitly selected scope.
This does not claim that a provider ran, an artifact shipped, or production has
zero unknown content.

## Authoritative selected scope

`apps/oshun/bff/src/content-coverage/v1-launch-content-scope.ts` is the
source-controlled authority. Its strict manifest has
`completeness: complete-selected-launch-scope` and is cross-checked against the
live autonomy-category source so category drift fails generation.

| Category                  | Canonical slot                                   | Locale  | Required | Autonomy      | Blockers |
| ------------------------- | ------------------------------------------------ | ------- | -------: | ------------- | -------: |
| `veritas.story-explainer` | `cslot_614444ee8d9f8463a4b35676906f29912e29ec6d` | `en-US` |        1 | approval      |        3 |
| `nyx.sky-event-brief`     | `cslot_25dadc068f1eb7d4f1482f06c1d1764dc5ad47bd` | `en-US` |        1 | review-window |        3 |
| `nisaba.study-passage`    | `cslot_a7bbe7b2735b6954eea1999dcdfa506b670faac9` | `en-US` |        1 | approval      |        3 |
| `tara.seasonal-ritual`    | `cslot_c076bf285da052fe9806c667bb999529ab207450` | `en-US` |        1 | approval      |        3 |

The seed registry now records four complete selected-scope rows rather than
incomplete candidates. The inventory carries the same canonical slot IDs,
records each as `missing`, and reports required/missing/blocked quantity `1`
with current/stale `0`. It does not inherit the unrelated eight-locale customer
message catalog: the selected slot locale is explicitly `en-US`, while the 28
tool surfaces keep their unknown quantities and undeclared locales.

## Canonical director frontier

Each slot depends on one source, one rights, and one provider node. The
canonical director schedules:

- 4 critical `source-refresh` jobs,
- 4 critical rights `evidence-remediation` jobs, and
- 4 high-priority provider-calibration `evidence-remediation` jobs.

All four generation nodes are deferred. The plan therefore registers and
schedules missing work without fabricating provider execution, work receipts,
review decisions, artifacts, placement receipts, or release evidence.

## Fail-closed shipped-scope boundary

`probeV1LaunchRelease` accepts only a caller-supplied COV-005
`complete-snapshot` observation. The generated package deliberately contains a
`missing-authorized-complete-shipped-observation` gap, sets
`releaseEligible: false`, and records `unknownShippedProof: not-proven`.
Negative tests prove that an unknown observed artifact blocks reconciliation.
This is the remaining V1-001 acceptance item.

## Automated verification

Verification ran on 2026-07-27 UTC. Every completed command below exited 0:

```text
pnpm verify:content-coverage:seed-registry
  targeted ESLint and TypeScript passed
  11/11 tests passed
  deterministic generated-output check passed

pnpm verify:content-coverage:inventory
  targeted ESLint and TypeScript passed
  10/10 tests passed
  deterministic generated-output check passed

pnpm verify:content-coverage:v1-launch
  targeted ESLint and TypeScript passed
  6/6 tests passed
  deterministic generated-output check passed

pnpm verify:contracts:content-slot
  17/17 tests passed; targeted ESLint and contracts TypeScript passed

pnpm verify:contracts:content-dependency-graph
  32/32 tests passed; targeted ESLint and contracts TypeScript passed

pnpm verify:contracts:content-release-closure
  21/21 tests passed; targeted ESLint and contracts TypeScript passed

git diff --check
  passed
```

The V1 tests freeze the exact four-category authority, all required COV-001
fields, 28 explicit empty tool mappings, 12 scheduled blockers, four deferred
generation nodes, and the missing external observation. Negative cases reject
runtime-category drift, duplicate authority declarations, absent observations,
and unknown shipped artifacts.

The host has approximately 15 GiB RAM and 31 GiB swap. Verification was targeted
and sequential; no broad Nx sweep or combined build matrix ran. This change
defines backend contracts and generated coverage records, not user-facing UI, so
Playwright/mobile automation is inapplicable.

## Remaining evidence required for closure

An independently authorized, complete observation of the actual selected V1
shipped scope must be supplied to the COV-005 release probe. It must reconcile
all observed artifacts to the four declared slots and contain no unknown
artifact. Until that real observation exists and passes, V1-001 remains
partially open and no zero-unknown production claim is permitted.
