Date: 2026-07-27
Repository result#
Metis Mobile now invokes the authenticated tutoring-session boundary before it
records either the avatar-request or explicit text-tutor action. Both requests
name the exact lesson topic and source package, require approved sources, retain
teach integrity mode, and ask the server to resolve the delivery
representation.
The client accepts a session only when all of the following are true:
- the returned session owner is the currently authenticated learner;
- source status is exactly
approved; - the requested and active modes occur in one internally consistent fallback chain;
- the representation kind matches the active avatar, voice, or text mode;
- release status is
approved, disclosure is ready, consent is granted or not required, and operator review is not pending; and - a live voice/avatar representation is explicitly provisionable.
Malformed or substituted response fields fail closed. A denied source or
representation never records the learner action or emits the subsequent xAPI
statement. The API now turns the existing source/representation ValueError
boundary into a structured HTTP 400 governance denial instead of an accidental
server error.
The Tutor surface renders the server-selected representation name, fallback summary, synthetic-media disclosure, and consent summary. Its initial static copy no longer claims that voice delivery is active before the governed request has completed.
Automated verification#
pnpm --dir apps/metis/mobile test --runInBand: 7 suites, 49 tests passed.pnpm --dir apps/metis/mobile lint: passed.pnpm --dir apps/metis/mobile typecheck: passed.PYTHONPATH=src pytest -q tests/test_tutoring_api_contract.py: 5 tests passed, including the exact mobile avatar request and structured source-denial contract.- Ruff check and format verification passed for the changed API and contract test.
pnpm metis:contracts:check: canonical OpenAPI and generated TypeScript freshness passed.- All five Metis Maestro YAML flows parsed successfully.
pnpm --dir apps/metis/mobile build: Expo web export passed with 1,277 modules.
Rendered and native boundary#
The frontend skill's interactive js_repl tool remains unavailable. A
Playwright Chromium equivalent therefore exercised the exported app with
intercepted authenticated service contracts:
- at 390×844, an approved avatar request visibly fell back to the approved voice representation, showed disclosure and consent, then emitted xAPI progress;
- at 320×700, a structured source denial showed the blocked action and emitted no xAPI request; and
- both cases had zero horizontal overflow.
The checked-in tutor-governance-expo-go.yaml covers the same credentialed
native path. It was not executed because METIS_E2E_EMAIL and
METIS_E2E_PASSWORD are unset and no stable attached Android target or verified
core-six-source-set-v1 package exists on this host.
This increment proves the governed mobile handoff, not a live face renderer or media runtime. It does not provision a real voice socket, render avatar frames, measure lip sync/fidelity, demonstrate consent withdrawal, or supply production source/provider/device evidence. Embodied-face launch completion therefore remains open.