--- status: reconciled-partial coverage_depth: deep-for-shipped-independent-seams last_walked: 2026-05-29 last_reconciled: 2026-07-20 specs: - apps/oshun/web/e2e/metis-lessons-session.spec.ts - apps/oshun/web/e2e/metis-lesson-completion.spec.ts - apps/oshun/web/e2e/metis-assessment-submit.spec.ts - apps/oshun/web/e2e/metis-tutor-session.spec.ts --- # Journey: Metis lesson specimen, assessment integrity, and tutor handoff The current customer flow joins navigation, not learner state. A BFF-backed schoolroom can show owned course proposals and separately recorded tutor memory; a dev/test-only backlog supplies the lessons index and today's session; all course and lesson ids then land on one authored reader. Quiz and assessment replay live in localStorage, the assessment can receive a durability-bound Themis response, and the displayed tutor queues text only in the browser. No shared authority records lesson completion or projects it into Home, the schoolroom, the library, or another device. ## Personas - **Returning learner** — enters from Home, the Metis schoolroom, the lessons index, or today's session. - **First-run learner** — needs honest no-progress and no-assessment states. - **Assessment learner** — clears the client rubric gate and sees integrity evidence with an appeal handoff when applicable. - **Source-conscious learner** — follows authored tutor citations into Nisaba. ## Pre-conditions - The customer web pages are opened through an authenticated shell. - `/metis` can read `GET /v1/metis/room`; the route combines caller-owned course proposals, a curated catalog, honest zero progress, and any separately stored tutor-memory summaries. - In development/test only, `GET /v1/metis/lessons` returns three fixed backlog rows. The production guard returns `503 not_configured`; the route has no account-scoped lesson source. - `getMetisLesson()`, `getMetisAssessment()`, and `getMetisTutor()` return authored fixtures from `metis-depth.ts`. - `POST /v1/metis/assessment-submissions` is reachable with a Metis-scoped bearer. Its verdict, appeal, gradebook consequence, and notification intent share one required, acknowledgement-bound operation snapshot in production. ## Steps ### 1. Enter from Home or the schoolroom - Home's Metis continuation exposes a live/fallback state and **Browse courses**, opening `/domains/metis` with `origin=home` and a course-path hint. - `/metis` reads `/v1/metis/room`. A learner without a real lesson cursor sees **Begin your first lesson**, zero lesson/assessment stats, and no open assessment rather than invented progress. - Owned course proposals are prepended to three curated catalog cards. Every card links to the shared reader with a `course` query. - The tutor nudge can quote a topic from a separately created tutor memory, but the card has no link or resume action. ### 2. Inspect lessons or today's session - `/metis/lessons` groups the development/test backlog fixture by course and exposes course-level `courseId` links plus lesson-level `id` links. - `/metis/session` selects the first row whose `assessmentReady` flag is true, otherwise the first row, and lists the next two fixture rows. It does not read dates, mastery, enrollment, due work, or a learner cursor. - The lessons endpoint is shared fixture data without an auth pre-handler and fails closed in production. A failed server read is rendered as the same empty state used for an account with no lessons. ### 3. Open a course or lesson link - Schoolroom cards preserve `?course=`, course groups preserve `?courseId=`, and individual rows preserve `?id=`. - The URL retains the query, but `MetisLessonPage` does not read it. The page always calls `getMetisLessonFixture()` and renders the same PHL.102 Stoic ethics section. - There is no per-course/per-lesson server lookup, authorization check, or mismatch response at the destination. ### 4. Read and answer the lesson quiz - `/metis/lesson` renders an authored passage, five static source rows, and a four-option multi-select quiz. - Answers are unmarked until submit. The client reveals the score and per-option results, supports **Try again**, and restores `{ picked, phase }` after reload from `oshun.metis.lesson-quiz.v1`. - The key is not scoped by tenant, account, course, lesson, assessment version, or attempt. Storage errors are ignored. - Previous/next section buttons have no target or handler and write no progress. ### 5. Compose an assessment answer - `/metis/assessment` renders an authored prompt, fixed due copy, four fixture rubric bars, and a client editor. - The editor requires 180–220 words and at least one citation-like token before enabling submit. **Insert citation** appends a placeholder; **Save draft** and every change write to `oshun.metis.assessment.draft.v1.`. - The request body uses the page's assessment id and hard-codes `courseId: phl-102`; it does not derive identity from a selected lesson. ### 6. Submit for integrity review - A valid answer posts to `POST /v1/metis/assessment-submissions` with Metis scope. The BFF derives deterministic integrity signals, adjudicates them with the canonical Themis bridge, persists the operation and gradebook consequence before publication, and returns the verdict evidence. - The browser locks the editor and shows verdict class, severity, signal count, recommended action, source of record, and appeal availability. - The browser stores that reduced response in localStorage. Reloading the submitted card is browser replay, not a submission/audit/gradebook GET. - The browser suite forwards assessment and integrity requests with a test-authored bearer, so it proves the UI and route seams but not untouched production browser authorization. ### 7. Follow an appealable verdict - A suspicious answer can return a violation with a canonical `/integrity/:verdictId/appeal` link. - In the browser run's same BFF process, the appeal page reads the verdict's signal count, rationale, and excerpt and exposes the appeal form. - Production hydrates the `metis-academic-records` ledger before traffic. Unit and PostgreSQL integration tests cover restart restoration, failure rollback, export, erasure fencing, and retention; this four-case browser suite does not itself restart the service. ### 8. Inspect the tutor specimen - `/metis/tutor` renders six fixture messages, three authored assistant turns, two citation chips, four fixed context rows, a disclosure, and an authored end-of-session note. - Citation chips genuinely navigate to `/nisaba?passage=&from=metis-tutor&ref=