Eve library

OSHUN Metis V1 Workstream Tracking

Guide

Revision 1

On this page

Status: Active

Date: April 9, 2026

Owners: OSHUN Product, OSHUN Engineering, OSHUN Platform, OSHUN Safety

Related:

  • docs/releases/v1/specs/program-charter.md
  • docs/releases/v1/reports/metis-v1-scorecard.md
  • docs/releases/v1/specs/metis-mobile-strategy.md
  • docs/releases/v1/runbooks/metis-operator-workflows-runbook.md
  • docs/releases/v1/specs/metis-media-runtime-tiers.md
  • docs/releases/v1/specs/metis-persistence-migration-backfill-plan.md
  • docs/releases/v1/reports/metis-subsystem-ownership-matrix.md
  • docs/releases/v1/specs/studio-launch-readiness-governance-dependency-and-data-contract-map.md
  • docs/releases/v1/specs/todos.md

1. Purpose#

This document makes Metis a first-class tracked workstream inside the canonical OSHUN V1 program model.

It exists to answer three execution questions in one place:

  1. Where does Metis sit in the master dependency map?
  2. What does each V1 milestone require from the Metis workstream?
  3. What must be true for Metis at each release gate?

This is not a replacement for the charter. It is the Metis-specific tracking view that operationalizes the charter.

2. Dependency Map Tracking#

Metis must be tracked as its own workstream across the dependency model rather than being folded into a generic domain bucket.

Metis workstream slice Depends on Blocks or enables Tracking rule
Shell contract integration domain registry, route typing, auth, analytics, notifications, search, BFF adapters six-domain shell truth, continuity, deep links, experimentation, entitlement-aware navigation Track separately from generic shell work because Metis must be both a peer domain and an educational substrate.
Learner product runtime live auth/session, learner APIs, course/tutor/assessment backend, responsive web/mobile shell entry customer completeness, retention-critical study loops, educational handoffs Track as launch-blocking customer scope, not as post-launch domain depth.
Admin and operator runtime admin data truth, review queues, moderation, audit trails, support and incident tooling operator readiness, trust/safety controls, launch-blocker triage Track as launch-blocking admin scope whenever Metis learner or tutoring flows are in release scope.
Grounding and evidence path Sophia source bundles, grounding packs, provenance and citation infrastructure grounded lessons, grounded tutor answers, evidence inspection, release-gate confidence Track as a hard dependency for any grounded educational claim.
Tutoring, memory, and pedagogy path Iris memory, Lilith pedagogy policy, Isis prompt/model execution, Themis integrity policy tutor continuity, mastery progression, high-stakes assistance boundaries Track as one explicit cross-substrate lane; do not let these responsibilities blur into generic “assistant” work.
Media and embodiment path Yemaya asset pipelines, Psyche realtime runtime, consent and safety controls narrated lessons, live voice tutoring, avatar delivery, fallback hierarchy Track separately from text-only Metis work because media/runtime safety and ops criteria differ.
Release and governance operations Metis scorecard, Metis overlay lane, blocker model, approvals, observability, rollback triggers channel promotion decisions, exception handling, post-release monitoring Track in the launch-readiness system as a dedicated Metis lane, not as incidental notes on other lanes.

The canonical split for this lane is defined in docs/releases/v1/specs/metis-media-runtime-tiers.md. Media work is not allowed to collapse prerecorded lecturer, live voice tutor, and live avatar tutor into one generic runtime bucket.

3. Milestone Plan Tracking#

Metis work must be visible in every milestone where it materially affects exit conditions.

Milestone Metis workstream requirement Exit evidence
M0 Program Alignment Metis is explicitly represented in ownership, scorecards, and program tracking artifacts. ownership matrix published, scorecard published, workstream tracking published
M1 Shell Foundations Shell contracts treat Metis as canonical across routing, auth, analytics, notifications, deep links, and entitlement surfaces. completed V1-MET-008 through V1-MET-011; verification evidence attached
M2 Customer Cohesion Metis learner entry, continuity, responsive behavior, reminders, and trust signals are live and automated where customer-critical. learner scorecard lane no worse than Amber; customer automation evidence present
M3 Domain Depth and Grounding Metis learner/tutor/assessment flows, grounded BYOM paths, and educational handoffs are operational. grounded flow evidence, tutor/assessment runtime evidence, cross-domain study flow verification
M4 Operator Readiness Metis admin review, moderation, rights, support, audit, and incident flows are live and operator-grade. admin scorecard lane no worse than Amber; operator automation evidence and published runbook/training present
M5 Launch Readiness Metis has a green or exception-approved launch lane with explicit blocker, approval, and rollback posture. Metis overlay reviewed, scorecard snapshot attached, gate evidence attached, blockers resolved or exception-approved

4. Release-Gate Tracking#

Metis requirements by release channel:

Channel Metis-specific gate requirement
Alpha Metis exists in shell contracts, ownership, scorecards, and dependency tracking with open risks explicitly assigned.
Private Beta learner-critical Metis paths, baseline admin review scope, grounding baseline, and automation baseline exist with blocker tracking.
Public Beta retention-critical learner flows, trust/integrity signals, accessibility/performance posture, and support/on-call readiness pass beta thresholds for Metis scope.
General Availability Metis learner/admin/platform/governance lanes are green or exception-approved, the dedicated Metis overlay is present, and no launch-blocking Metis issue remains without time-bounded approval-backed exception.

5. Launch-Gate Tracking Rules#

  • No release involving Metis learner, tutoring, assessment, or institutional scope may skip the dedicated Metis overlay lane in launch readiness.
  • No GA promotion is valid while the Metis scorecard is absent, stale, or red.
  • Metis blockers must stay visible as first-class release blockers rather than being hidden inside generic customer or admin buckets.
  • Metis release reviews must attach evidence for educational quality, grounding/provenance, rights/integrity, pedagogy, cost/runtime posture, and rollback readiness where applicable.
  • Metis exceptions must be owner-assigned, time-bounded, rationale-backed, and visible in the same launch-governance surface as the scorecard lane.

6. Operational Status Rule#

Whenever the Metis scorecard changes materially, this workstream tracker must be reviewed alongside the charter milestone and gate assumptions.

If the scorecard says Metis is Red or Amber, this tracker must continue to show Metis as an active launch workstream rather than a completed dependency.