--- status: reconciled-partial coverage_depth: deep-for-separated-hub-catalog-player-reciprocal-and-recommendation-seams last_walked: 2026-05-29 last_reconciled: 2026-07-21 specs: - apps/oshun/web/e2e/nyx-event-pages.spec.ts source: WALKTHROUGH/journeys/nyx-to-tara-bridge.md --- # Journey result: Nyx → Tara — curated navigation, no shared handoff record - **Walked**: 2026-05-29 at `3678298cd3`. The retained result cited an ephemeral `/tmp/claude-oshun-lt-2-walkthrough/walk.mjs`, reported one Tara link on `/nyx`, and treated a 200 from `/v1/cross-domain/recommendations` as bridge evidence. It retained no DOM, href, source event id, resolver output, Tara practice id, analytics record, session receipt, completion record, return target, member identity, or service trace. - **Reconciled**: 2026-07-21 against the live and unavailable `/nyx` mappers, all fixed event models, the Nyx → Tara relationship resolver and card, shell route hydration, Tara player and reciprocal suggestion builders, local theme-continuity storage, auth cleanup, the BFF recommendation route, focused unit suites, and the named Playwright file. This is repository evidence, not a production analytics sink, real audio stream, personalized policy evaluation, cross-device session, or service-level trace. - **Verdict**: **partial / deep for the separated shipped seams** — every fixed rich Nyx event receives one deterministic Tara card; the real link opens the intended Tara timer player; completion exposes a generic reciprocal Nyx suggestion and a 12-hour browser-local theme snapshot. The `/nyx` hub's conditional Tara slot is not populated, the event id stops at the source link's DOM attributes, the telemetry markers have no emitter, audio is wired to the wrong shape/path, and no owner-scoped handoff or completion record joins Nyx to Tara. - **Current authority**: [`WALKTHROUGH/journeys/nyx-to-tara-bridge.md`](../journeys/nyx-to-tara-bridge.md) now walks the implemented fixed-catalog path and names the hub, API, telemetry, media, identity, and persistence boundaries explicitly. ## Result at a glance | Interaction | Proof · limit | | ------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Historical walk | **Proof:** a prior browser walk reported a visible Tara link and a successful recommendation response. **Limit:** its temporary script and artifacts are gone, so neither claim retains inspectable identity or network evidence. | | `/nyx` hub | **Proof:** `NyxRoom` contains a conditional **Ground with Tara** link when `data.taraGroundingCue` exists. **Limit:** neither `mapNyxTonightToNyxData` nor `nyxUnavailable` supplies that optional field, so both live and unavailable hub states omit the link. | | Fixed event relationship | **Proof:** every record returned by `listNyxEventPageModels` receives exactly one relationship from a static resolver. Event type plus authored `highlightFrame` and `audience` select awe, lunar, meteor, seasonal, or cosmic-perspective copy and a Tara path. **Limit:** `audience` describes the content; no member, preference, lineage, crisis, history, time, or location enters the resolver. | | Event-detail card | **Proof:** the card renders reason, relationship, mode, ritual moment, subtype, title, summary, and a real `/domains/tara?origin=...&stack=nyx&path=...` link. It exposes source event, practice, and relationship ids as DOM attributes. **Limit:** the href itself contains only shell origin, domain stack, and practice path; Tara receives no event id or event envelope. | | Tara destination | **Proof:** the hydrated path launches `SessionPlayer`; a Nyx-final stack labels the Play control `surface=nyx_event_handoff`, and the timer, seek, pause, transcript, completion, and reflection UI are functional local state. **Limit:** the surface label is derived only from `stack.at(-1) === 'nyx'`; it does not validate the source event or a server-issued handoff. | | Tara audio | **Proof:** the player remains usable when media fails and explicitly reports timer mode. **Limit:** its hidden audio source uses `/api/v1/sessions//audio`, while the Next rewrite proxies `/v1/*`; the BFF endpoint returns a JSON metadata envelope whose `tracks.primary.url` is the actual media locator. The audited element neither reaches that route nor resolves the track URL. | | Completion | **Proof:** reaching `totalSec` or seeking to it renders the completion surface, appends `taraSessionState=complete` to browser history, and writes a theme snapshot. **Limit:** no Tara session completion POST, Nyx observation, Iris memory, shared trace, or durable receipt occurs. The URL flag can reopen completion without proving elapsed practice. | | Reciprocal Nyx suggestion | **Proof:** the completed player builds a Tara → Nyx relationship from the generic launched session and routes to `/nightly-highlights` or `/sky-map` with a `ref`. **Limit:** `march-equinox` and every other originating event id are absent; the destination cannot return to the exact event. | | Theme continuity | **Proof:** `oshun.tara.theme-continuity.v1` stores session taxonomy and expires reads after 12 hours. **Limit:** the key is browser global, is not cleared by normal auth cleanup, and is consumed by Home recommendation ordering—not as a Nyx/Tara handoff record. | | Telemetry contract | **Proof:** the Nyx link exposes `nyx_event_tara_recommendation_opened`; the Tara Play control switches among `tara_sit_started`, paused, and resumed attributes and labels the inferred surface. **Limit:** the audited controls only mutate UI/navigation; no delegated handler or direct analytics call consumes those attributes. | | BFF recommendations | **Proof:** the authenticated route can rank and return member-scoped source candidates, partial-failure metadata, cache headers, attribution, and server-side served telemetry. **Limit:** its target union is only Nisaba or Metis. Its Nyx builders produce Nyx → Nisaba and Nyx → Metis items, and no Nyx event-detail or Tara player component calls the route. | | Named automation | **Proof:** `nyx-event-pages.spec.ts` contains 15 browser cases. One case crosses `march-equinox` → Tara timer → generic Nyx return; another checks five relationship buckets, while component/domain tests pin the builders and attributes. **Limit:** the browser case accelerates completion with repeated 15-second seek dispatches, asserts DOM telemetry rather than delivery, and does not inspect a server completion receipt because none exists. | ## Evidence map Solid arrows are implemented navigation or local state transitions. Dashed arrows are dormant render branches, identity loss, or unrelated authorities. The central lane is the only working Nyx → Tara path. ```mermaid flowchart TB B[Nyx to Tara bridge] --> H[Nyx hub
live or unavailable mapper] B --> E[Fixed Nyx event detail] B --> X[BFF cross-domain recommendations] H -. taraGroundingCue never supplied .-> G[Dormant Ground with Tara slot] E --> R[Static relationship resolver
content fields only] R --> C[Tara recommendation card
event id stays in DOM] C --> P[Tara timer player
origin · stack · practice path] P --> L[Local completion
URL flag + 12-hour theme snapshot] L --> N[Generic Nyx suggestion
nightly highlights or sky map] C -. no emitted analytics .-> A[Analytics receipt] P -. no event or session envelope .-> D[Durable cross-domain record] N -. no originating event id .-> E X --> M[Nisaba or Metis targets only] ``` ## Proven observations ### The retained hub pass no longer matches the data path - `NyxRoom` still contains the exact conditional block that can render **Ground with Tara**, but its input type makes `taraGroundingCue` optional. The live `mapNyxTonightToNyxData` mapper copies the ephemeris fields and adds only the Nisaba canon link. `nyxUnavailable` does the same for the empty state. A repository-wide source search finds no producer for the optional Tara field. - This makes the branch dormant in both normal `/nyx` outcomes. The older result's statement that the hub "ships" the link is not supported by current source or mapper tests. The working customer bridge moved to the fixed rich event surface under `/events/` and `/domains/nyx?...path=/events/...`. - The hub is fed by `/v1/nyx/tonight`, while the event-detail bridge is built from `NYX_WEB_EVENT_RECORDS`. Their adjacency in Nyx does not make a missing hub cue evidence for the fixed catalog path. ### Every fixed event receives one authored classification, not a member recommendation - `buildNyxTaraRecommendations` always returns a one-element array for a valid fixed event. Six event ids have explicit `highlightFrame` and `audience` configurations; remaining event types fall through authored awe, symbolic, seasonal, observer, or educational rules. The domain resolver then defaults any unmatched input to `nightly_awe`. - The web test explicitly asserts that every fixed event has a Tara recommendation. There is no shipped "no relationship" branch for a valid fixed record, no score or abstention threshold, and no runtime service call. - Resolver inputs include event title and object names, but its decision logic does not read them. The decisive fields are `ritualMoment`, highlight frame, event type, source kind, and the content-level audience enum. The output is a descriptor from `NYX_TARA_RELATIONSHIPS`, including generic copy and one of the fixed practice paths. - `audience: 'general' | 'student' | 'observer' | 'mixed'` is authored metadata for the event model. No authenticated subject id, member profile, selected tradition, preference, prior practice, accessibility need, or distress input is available. Authentication gets the user into the shell; it does not make this resolver personalized or crisis aware. ### The real link carries a practice choice but drops event identity - The event card retains excellent inspectable source metadata: `data-telemetry-event-id`, `data-telemetry-practice-id`, relationship kind, reason, display mode, ritual moment, and subtype. The March equinox case maps to `tara-morning-opening` and a seasonal-opening relationship. - `buildHydratedWebDomainRoutePath` encodes only the destination path plus `origin` and `stack`. The March equinox href is therefore `/domains/tara?origin=explore&stack=nyx&path=%2Fmeditate%2Fritual%2Ftara-morning-opening`. Neither `eventId=march-equinox` nor a handoff id crosses the anchor. - `TaraSurface` parses the path, converts the final segment into a generic session id, labels ritual paths **Guided ritual**, and creates companion prompts from that generic Tara session. It does not read the source anchor's DOM attributes after navigation. The `nyx_event_handoff` player surface is inferred solely from the last stack entry. - Browser history preserves the broad shell context and later the `taraSessionState=complete` flag. Those are useful navigation affordances, but they neither assert that the correct event created the launch nor bind a completion to that event. ### The player is a timer experience; its current audio source cannot consume the BFF contract - The timer advances once per second, supports seek controls, and completes when elapsed time reaches the generated duration. The E2E helper dispatches the 15-second forward control repeatedly until completion, so it proves player state and the completion surface without waiting for a full practice. - The hidden `