Status: Accepted v1.0
Date: March 23, 2026
Owners: OSHUN Product, OSHUN Growth, OSHUN Web, OSHUN Mobile, OSHUN Design
Related:
docs/releases/v1/specs/program-charter.mddocs/releases/v1/specs/todos.mddocs/releases/v1/runbooks/launch-runbook.mddocs/releases/v1/scope/mvp-scope.mdapps/tara/docs/marketing/README.mdapps/tara/docs/IOS_APP_STORE_CHECKLIST.mdapps/tara/docs/GOOGLE_PLAY_CHECKLIST.md
1. Purpose#
This document is the canonical governance tracker for OSHUN V1 public-web, App Store, Play Store, and deep-link distribution work.
It exists to close V1-GOV-029: the repo already contained distribution
artifacts and backlog items, but it did not yet state clearly in one place that
public website readiness, mobile store readiness, and external-entry deep-link
distribution are launch-blocking workstreams for OSHUN V1.
This document closes V1-GOV-029. It does not close the detailed execution
items in V1-PUB-001 through V1-PUB-011 or the release exit gate
V1-EXIT-058.
2. Repo-Informed Current State#
The current repo already shows meaningful distribution work in multiple places:
docs/releases/v1/scope/mvp-scope.mdalready treats the public website and installable PWA as in-scope product surfaces.docs/releases/v1/runbooks/launch-runbook.mdalready includes App Store Connect, Google Play Console, and production web deployment steps.- Tara already has reusable seed artifacts for store marketing and review
readiness in
apps/tara/docs/marketing/README.md,apps/tara/docs/IOS_APP_STORE_CHECKLIST.md, andapps/tara/docs/GOOGLE_PLAY_CHECKLIST.md. - the V1 backlog already contains a dedicated distribution section (
V1-PUB-001throughV1-PUB-011) plus an exit gate (V1-EXIT-058).
The missing piece was governance clarity: these items must be treated as launch-blocking release work, not as optional growth or post-launch marketing tasks.
3. Governing Decision#
For OSHUN V1, the following are hard launch-blocking workstreams:
- the public marketing website and conversion funnel
- Apple App Store submission readiness
- Google Play Store submission readiness
- Universal Links / App Links and external deep-link routing
- beta-track distribution readiness through TestFlight and Play Console
These are product-distribution responsibilities, not optional launch enhancements.
GA is not considered achievable while any of these workstreams is untracked, ownerless, or missing acceptance evidence.
4. Canonical Workstream Tracker#
| Backlog Item | Workstream | Why It Blocks Launch | Required Evidence |
|---|---|---|---|
V1-PUB-001 |
Public marketing website | OSHUN needs a production public entry surface with product positioning and acquisition CTA. | live or production-ready web experience with approved positioning |
V1-PUB-002 |
SEO and metadata fundamentals | Launch distribution depends on discoverability and correct crawler/social metadata. | sitemap, robots, semantic metadata, OG/Twitter previews |
V1-PUB-003 |
Public-to-authenticated conversion funnel | Website value is incomplete without a trackable handoff into signup and first-run app entry. | verified CTA path, signup handoff, analytics instrumentation |
V1-PUB-004 |
Social sharing metadata | Shared Oshun content needs governed preview rendering and attribution. | preview specs, rendering rules, and validated metadata |
V1-PUB-005 |
Public-web Playwright coverage | Launch-critical public entry flows must be automated, not manually trusted. | passing browser automation for landing, conversion, and deep-link entry |
V1-PUB-006 |
Apple App Store submission assets | iOS launch requires finalized listing copy, screenshots, privacy labels, and review notes. | App Store Connect-ready submission package |
V1-PUB-007 |
Google Play Store submission assets | Android launch requires listing copy, screenshots, data safety, and ratings metadata. | Play Console-ready submission package |
V1-PUB-008 |
Universal Links / App Links | External traffic must land in the right mobile experience instead of fragmenting into dead links or wrong routes. | validated iOS and Android association/deep-link configuration |
V1-PUB-009 |
Beta distribution tracks | Pre-launch rollout and review require TestFlight and Play internal/beta tracks. | active test tracks with owner and release notes |
V1-PUB-010 |
App update strategy | Store launch needs version-floor, force-update, and prompt strategy defined before production drift begins. | approved update policy and in-app prompt plan |
V1-PUB-011 |
External deep-link E2E coverage | Email, web, notification, and social entry paths are launch-critical distribution behavior. | automated end-to-end deep-link routing coverage |
5. Existing Seed Artifacts and Reuse Guidance#
The current repo already contains artifacts that should be reused rather than recreated from scratch:
docs/releases/v1/runbooks/launch-runbook.mdfor store submission sequencing and rollout operations- Tara marketing/store documents as seed templates for listing copy, asset specs, and store-review checklist structure
libs/oshun/navigationand domain launch contracts for deep-link normalization- existing mobile and audit docs that identify hardcoded domain-specific deep links requiring Oshun-level consolidation
These seed artifacts do not mean OSHUN V1 distribution is complete. They mean the workstream now has traceable starting points and should be executed as a first-class launch program.
6. Tracking Rules#
The following tracking rules apply immediately:
V1-PUB-001throughV1-PUB-011are launch-blocking backlog items.- No public launch checklist may mark OSHUN V1 ready while those items are still implicitly treated as optional marketing follow-up.
- Release signoff must include evidence for website readiness, store readiness, deep-link routing, and beta-distribution readiness.
V1-EXIT-058remains open until the public website, store listings, and deep-link routing are all verified.
7. Acceptance Record#
The OSHUN V1 program accepts the following:
- the public website is a launch-critical product surface
- App Store and Play Store submission readiness are launch-critical distribution responsibilities
- deep-link distribution from web, email, push, and social entry points is launch-critical behavior
- the
V1-PUB-001throughV1-PUB-011backlog section is the canonical execution tracker for this workstream
This acceptance closes V1-GOV-029.