Implementation baseline: b418a8d555171b458cd68037f3b936d6cc670449.
Visual thesis: retain the cream field guide, Georgia claims, Arial detail and terracotta emphasis. Show the actual rendered media, then use a cast map, score record, arrival decision tree, choreography state diagram, cadence timeline and delivery sequence to explain the feature. A diagram must name its input, output and current implementation boundary.
Content plan: introduce the intended sit and current delivery, then the four synthetic mentors, lineage/voice rules, settings, arrivals, postures and score validation. Follow a worked score through structural overrides, session behavior, breath timing, tone evaluation, release evidence, rendering, private media, storage and analytics. Finish with the actual web/mobile consumers, fallback, disclosure and unresolved connections. This source family needs more than its existing overview mention.
Interaction thesis: use the established keyboard navigation, narration, source disclosures and image inspection. Keep reduced-motion behavior and a complete PDF. Do not introduce a separate animation system merely to decorate the guide.
Executed cases and source review establish these distinctions:
- The CPU render path produces a contemplative gradient and luminous band; its current frame inputs do not consume the mentor mesh, voice, setting scene or posture. Registered avatar assets are declarations rather than rendered proof.
- The capability response reports the cast's missing release evidence, while the render route and player check different conditions. A not-ready release report must not be described as an enforced render stop without that link.
- Score validation runs before arrival resolution. An incompatible requested arrival may be refused before a resolver can replace it.
- Both component requests use a generic guided score with null session, cadence, context and mood. The web component uses session state for status copy; the APNG is a separate media clock.
- The native artwork component exists, but the bounded search of the mobile application source found its symbol only in its definition and owning tests. Native delivery therefore needs a caller trace rather than a test-only claim.
- Disclosure threshold helpers and release dossiers are distinct from measured runtime visibility, rendered rehearsal evidence and human signoff.
The delivery receipt records 43 final slides, 27 source cases, ten unmodified owning web tests, twelve browser characterizations and a scoped axe scan with no violations. All pages receive desktop, narrow, embedded and PDF review, with four enlarged-text cases and four rejected missing-content controls. Twelve complete source units are bound to current slide fingerprints. All 982 earlier slides and recordings are preserved; 62.8 minutes of new narration are delivered. The initial review exposed two excessive slide heights and a small capture; claims and image composition were refined, and the score was moved before its constraints.
The source pin is 1ceae52c7896a59ac74a4429d410f3218f0b91c6; all 52 inspected
or executed source files match the implementation baseline. The BFF HTTP route,
production signing, native-device behavior and human acceptance are not executed
here. The browser uses explicit responses and a two-second actual development
APNG for the web component's four-second request. The default cast remains
drafted. Product gaps are characterized, not repaired. The full V1 audit stays
active.