# V9-004 V7 Metis creator-education bridge

Date: 2026-07-27

## Outcome

V7 now has a governed creator-education boundary at
`libs/v7/metis-creator-education-bridge`. It admits exact released Metis lessons
through `@metis/game-bridge-contract` and projects them into a deterministic
`v7.metis-creator-education-manifest`.

The bridge is ordered around five existing V7 implementation authorities:

1. `evaluate_supply_chain_publish` for signed manifests, content-addressed
   artifacts, pinned lock files, and re-publish step-up;
2. `verify_sandbox_tier` for declared-versus-observed executable capabilities;
3. `scan_artifact` plus `evaluate_distribution_gate` for complete clean scans
   before fetchability;
4. `createPublishingVersion` plus `transitionPublishingVersion` for the Draft →
   Submitted → InModeration → Published/Rejected lifecycle; and
5. `publishCrossPlatformCatalogArtifact` for catalog and per-console
   authorization decisions.

Tests read the actual Sekhmet Rust and Abundantia TypeScript production sources
and require every named symbol to remain present. Each workflow phase maps to
one unique released Metis module and retains the named V7 authority, expected
proof, source path, and explicit limitation.

## Critical authority separation

Metis teaches a human creator how to prepare for V7 gates. It is not one of
those gates.

The request rejects publication, moderation, scanner, sandbox-runtime,
governance-execution, and payout-settlement invocation contexts before any Metis
read. It also rejects artifacts and executable bytes; manifests and lock files;
step-up receipts; scan reports and attestations; distribution decisions; sandbox
tiers and capability grants; publishing versions and decisions; console
authorizations and catalog records; governance proposals and votes; and payout,
earnings, revenue-share, KYC, and tax-interview data.

The output makes all denied authority explicit. It cannot scan or attest an
artifact, select a sandbox tier, grant a capability, moderate or publish,
authorize a console, distribute content, govern, set policy, calculate a payout,
or settle one. Sekhmet and Abundantia remain required for every operational
decision.

## Provider admission

The shared contract requires exact released publication and lesson versions,
operator approval, cleared rights, verified provenance, approved
Sophia-source-of-record grounding, learner disclosure, accessibility and
fallback readiness, and safe labeled media.

## Automated verification

Focused verification passed:

- V7 bridge production and test typechecks;
- V7 bridge Vitest — 1 file, 20 tests;
- V7 bridge lint and build;
- canonical Metis contract generation check;
- Nx project discovery and root module-boundary lint;
- lockfile importer parse and exact workspace-link validation; and
- targeted formatting validation.

The repository-wide frozen-lockfile command remains blocked by a pre-existing
root importer mismatch: the lock retains removed `@changesets/cli` and records
`@fastify/cors` as `11.2.0` while the root manifest uses `catalog:`. This
increment does not rewrite that unrelated user-owned lockfile work. Its new V7
importer was parsed independently and its exact Metis workspace links were
validated.

Coverage includes real source-symbol binding, exact workflow order,
deterministic output, every denied authority flag, operational-payload
stripping, twelve forbidden invocation/payload cases before I/O, incomplete
mappings, unreleased packages, and cross-phase lesson binding.

## Scope boundary

This closes the actionable V7 canonical-provider admission seam. It does not
claim a rendered V7 creator UI, runtime authentication, a scanned artifact, a
catalog publication, console certification, or creator payout. V8 and
game-runtime consumption remain open, so the composite V9-004 checkbox remains
open.
