Oshun V1 Content Bundles

Per-domain content bundle specifications for the V1 launch. Each domain ships a minimum-viable bundle required for GA, an expanded launch-quality bundle that defines the actual customer-perceived quality bar at launch day, and (where the domain offers a paid tier) a premium bundle.

Every bundle is gated by the per-domain review checklist, the accessibility plan, the locale plan, and the seed-data manifest below. Per-domain content can only be promoted to the customer-visible cohort once all gates pass per docs/launch/go-no-go.md.

Bundle table per domain#

Counts above are launch-day targets. Counts below the minimum-viable column are GA blockers; counts above are launch-quality stretch.

Per-domain review checklist#

Every item entering a bundle passes every line of the checklist below. Reviewers are trained per docs/training/oshun-v1-reviewers.md.

Tara (rituals, lineage, reflection)#

• Lineage attribution verified against the certified teacher source.
• Tone alignment with the Tara archetype (calm, embodied, never coercive).
• Reduced-motion alternative captured for any motion-heavy ritual cue.
• Audio captions and transcripts present.
• Crisis-content disclosure on rituals that touch grief, loss, ending.
• Locale: ritual copy localized for every launch locale; cultural-fit review for ar and he.

Veritas (briefings, claims, sources)#

• Every claim bound to a source via the Sophia binding tool.
• Retraction/correction fixtures present for the source set; the retraction-cascade validator passes.
• Confidence band assigned per claim with the canonical bands.
• AI-disclosure copy attached; counterclaim view rendered before publish.
• Locale: launch-quality coverage for en-US and fr-FR; minimum-viable coverage for es-US, de-DE, ar, he, ja-JP, and pt-BR per the launch-locale coverage table.
• Rights: external quotes within fair-use limits; longer extracts require explicit rights agreement.

Nyx (sky events)#

• Astronomical data verified against the IAU and IERS feeds for the event window.
• Observation window calculated against the customer's locale and timezone; accessibility summary captured for screen-reader use.
• Weather and visibility context generated against the canonical provider; fallback copy if the provider is unavailable.
• Calendar export tested across Apple/Google/iCal; reminder fire verified.

Arete (habits, goals, routines)#

• Coaching copy aligned with the Lilith-certified coach personas; identity disclosure surfaced if persona changes.
• Crisis-content disclosure on prompts that touch self-harm or major life stress; crisis-routing path verified.
• Reduced-motion variant of any animated check-in.
• Locale: launch-quality coverage for en-US, es-US, and pt-BR; minimum-viable coverage for fr-FR, de-DE, ar, he, and ja-JP.

Nisaba (passages, editions, translations)#

• Rights confirmed for every manuscript scan (public-domain or licensed with confirmed rights).
• Edition lineage captured (which manuscript, which edition, which scholar).
• Translation lineage captured (translator, edition, year, license).
• Provenance manifest generated and signed.
• Locale: passage metadata localized; passage text follows the canonical edition; transliteration provided where appropriate.

Metis (courses, tutor sessions, assessments)#

• Source bundle reviewed for accuracy and rights.
• Pedagogy band (introductory, intermediate, advanced) assigned and evaluation-pipeline-tested.
• Tutor persona certified per docs/training/oshun-v1-persona-operators.md.
• Assessment evidence packs include rubric, correct answers, and alternative correct answers where applicable.
• Mastery-tracking event coverage verified against assistant-taxonomy.ts.

Accessibility plan per bundle#

Every customer-facing item in every bundle meets the cross-cutting accessibility plan below. The plan binds to the docs/oshun/ia-and-experience-quality.md QA checklist.

Locale-specific notes:

• RTL (ar, he): mirror layout; line-break review; ligature support verified.
• Text expansion: de and fr strings sized for 30% expansion against en baseline.

Seed data inventory#

Seed and fixture artifacts that back the launch-quality bundles are surfaced through libs/oshun/analytics/src/v1-launch-readiness-manifest.ts and libs/oshun/analytics/src/v1-32-content-localization-documentation.ts (mandates V1-CONT-010..015) and locked by __tests__/v1-launch-readiness-manifest.test.ts and __tests__/v1-32-content-localization-documentation.test.ts, which fail if any referenced source path drifts off disk. Canonical fixture-bearing locations:

Every fixture is referenced by at least one test in the matching library or app and by an entry in v1-launch-readiness-manifest.ts. Fixtures that lack referencing tests are dropped before GA; the manifest test asserts every declared sourcePath exists on disk.

Bundle release gate#

A domain's bundle is GA-ready when:

1. Minimum-viable column items are 100% present and reviewed.
2. Launch-quality column items are ≥ 90% present and reviewed.
3. The per-domain review checklist is 100% green for in-scope items.
4. The accessibility plan rows are 100% green for in-scope surfaces.
5. The locale plan minimums are met per docs/launch/locale-coverage.md.
6. Seed-data fixtures are referenced by their matching tests.
7. The compliance operator verifies the bundle release record in the audit packet.

A domain that fails any of (1), (3), (4), (5), or (7) blocks GA for that domain. A domain that fails only (2) launches at minimum-viable with a public commitment to fill within the post-launch hyper-care window.