Eve library

V9-001 — Source approval and rights authority evidence

Evidence

Revision 1

On this page

Status: the ordinary V9 lesson-generation boundary now requires current, source-bound approval and scoped active rights in addition to exact-byte retrieval; production-approved source bundles remain absent.

Date: 2026-07-27

Gap closed by this increment#

ApprovedGenerationSourcePassage previously required an exact-passage retrieval proof, but its name overstated the authority it carried. A correctly retrieved passage could reach lesson generation without proving either an affirmative source-approval decision or a license authorizing this use.

This increment makes those proof meanings non-substitutable:

  • @oshun/contracts provides canonical constructors for affirmative source_approval and active rights_license_receipt records;
  • approval and rights records bind to the exact sourceId through subjectRef; approval additionally binds through payload.sourceRef;
  • both authority records must have been evaluated under the exact v9.metis.approved-source-generation.v1 policy;
  • the rights receipt must contain the exact scope:v9-lesson-generation grant;
  • retrieval, approval, and rights proofs must be schema-valid, passing, non-future, and unexpired at evaluation time;
  • proof IDs must be unique throughout the source bundle; and
  • approval and rights receipts are consumed as trusted control-plane data and removed before bounded source content is serialized into the untrusted model prompt.

The ordinary generation path invokes this validation while building the first prompt, and the verification-context adapter rechecks it before minting lesson-scoped grounding evidence.

Adversarial proof#

The generation-boundary suite proves that each of the following is rejected before the provider receives a request:

  1. the source approval is absent;
  2. the approval is valid but bound to another source;
  3. the approval is future-dated;
  4. the rights receipt is expired; and
  5. the rights receipt is active but grants only an unrelated scope; and
  6. the rights receipt was issued under an unrelated policy.

The suite also inspects captured provider prompts and proves that proof IDs, rightsholder references, and rights receipts are not disclosed to the model. The existing passage-substitution regression continues to prove that retaining all authority metadata cannot substitute different passage bytes.

Verification#

Verification ran sequentially with one Vitest worker on a 15 GiB host with 31 GiB swap. Available memory remained approximately 12 GiB during the complete Metis test target.

text
Contracts
  proof types + semantic grounding + publication release: 35/35 passed
  contract/persistence alignment manifest: 5/5 passed

Metis LLM client
  focused ordinary/verified lesson boundary: 18/18 passed
  complete package: 26 files, 1,328/1,328 passed

Prompt-injection evaluation
  V8/V9 typed-data and injection boundary: 41/41 passed
  complete TypeScript portfolio: 5 files, 232/232 passed

TypeScript
  contracts production library: passed
  Metis LLM client production library: passed
  prompt-injection evaluation project: passed

Targeted ESLint passed with zero errors after the duplicate public-barrel import was corrected. Prettier and git diff --check passed. The contracts and Metis whole-spec TypeScript configurations still report pre-existing errors in unrelated legacy tests (principally unused imports and readonly/mutable fixture mismatches); neither report identified a changed test file. The complete runtime test targets above pass.

No UI changed, so Playwright, mobile automation, and the frontend workflow are not applicable. No provider, database, source-acquisition, media, or Unreal execution is claimed.

Remaining completion boundary#

The compound V9-001 source-bundle checkbox remains open. Repository fixtures exercise the authority contract but are not production approval decisions, license receipts, acquired source passages, live provider output, or calibrated production entailment evidence. This increment prevents those missing artifacts from being represented by retrieval metadata alone; it does not fabricate them.