CEO Directive — April 2026 North Star
Status: ACTIVE. This issue is the single roll-up of everything that must ship for V1 launch. Every team lead reads this and follows the link for their repo.
Where we are (as of 2026-04-19)
The organisation has too many repos, too many copies of "the same thing", and a lot of half-finished scaffolds. Wave 4 of the April 2026 consolidation closed that out at the strategic layer:
- 5 strategic decisions are now DECIDED in
PRODUCT-VISION.md (no more open questions on what we are building).
- 4 dead A2A repos archived.
schemas/team.schema.json shipped — one binding contract for all 17 team manifests.- All 17 teams have live
team.json downstream.
docs/CANONICAL-REPOS.md names the only 4 code repos that matter for the product: OpenSIN-Code, OpenSIN-backend, OpenSIN-WebApp, Infra-SIN-OpenCode-Stack.docs/FOLLOWUPS.md has the surgical follow-on tickets (CP1 code merge, S2 scaffold triage, M2 aggregator, C1 registry regen).
What is now expected of every team: deliver your Launch Gate. One ticket per repo. Checklist. No ambiguity.
The 4 product surfaces
From PRODUCT-VISION § UI-Schichtung:
No surface does anyone else's job. No auth chrome on my.opensin.ai. No pricing/checkout on opensin.ai. No marketing hero on chat.opensin.ai.
Platform Launch Gates
The 3 code repos that every surface depends on:
Biggest known platform blocker: CP1 — merging Core-SIN-Control-Plane into OpenSIN-backend. Tracked: OpenSIN-backend#1171 + Core-SIN-Control-Plane#17.
Second biggest: R1 — OpenSIN-Code vs opensin-ai-cli merge/split decision. Tracked: OpenSIN-Code#1116.
V1 Agent Fleet
V1 does not ship all 80 agents. V1 ships 3 flagships that work end-to-end through chat.opensin.ai on launch day. Everything else stays listed in the marketplace but is labelled "coming soon" until its team cuts its own quality gate later.
Fleet hygiene (blocks nothing, but do it before V1)
OpenSIN-overview#39 — 20+ duplicate "Governance Contract Adoption" issues + test-spam across 12 repos. 15-20 minutes of gh issue close work. Script-able.
What I am NOT asking for right now
- No new repos until V1 ships. We already have 200.
- No new agents in the marketplace beyond the 3 flagships until they each cut their own quality gate (template:
A2A-SIN-MiroFish#147).
- No design-system re-design. Epic #115 (website-opensin.ai) / #67 (website-my.opensin.ai) decides which existing system wins and applies it to both. No third system gets invented.
- No archival votes on the 6
A2A-SIN-Code-* scaffolds until R1 (#1116) is decided. Their fate is coupled to that decision.
Delegation table — who owns what
How progress is tracked
- Each Launch Gate / Quality Gate above is a GitHub issue with a checklist.
- Weekly: each owner ticks their boxes. No status reports required, the checkbox state IS the status.
- When every checkbox is green, V1 ships.
If you land on this issue and your team is not in the table: you are not on the V1 critical path. Your work is valuable but does not block launch. Keep doing it, but do not expect cross-team attention before V1.
All prior ad-hoc "Big Boss" / Governance Adoption / Roadmap issues across the fleet are superseded by this one. If the acceptance criteria of one of those overlaps this, close it and link here.
Co-authored-by: v0[bot] <v0[bot]@users.noreply.github.com>
CEO Directive — April 2026 North Star
Where we are (as of 2026-04-19)
The organisation has too many repos, too many copies of "the same thing", and a lot of half-finished scaffolds. Wave 4 of the April 2026 consolidation closed that out at the strategic layer:
PRODUCT-VISION.md(no more open questions on what we are building).schemas/team.schema.jsonshipped — one binding contract for all 17 team manifests.team.jsondownstream.docs/CANONICAL-REPOS.mdnames the only 4 code repos that matter for the product:OpenSIN-Code,OpenSIN-backend,OpenSIN-WebApp,Infra-SIN-OpenCode-Stack.docs/FOLLOWUPS.mdhas the surgical follow-on tickets (CP1 code merge, S2 scaffold triage, M2 aggregator, C1 registry regen).What is now expected of every team: deliver your Launch Gate. One ticket per repo. Checklist. No ambiguity.
The 4 product surfaces
From PRODUCT-VISION § UI-Schichtung:
opensin.aiwebsite-opensin.ai#128my.opensin.aiwebsite-my.opensin.ai#81chat.opensin.aiOpenSIN-WebApp#14docs.opensin.aiOpenSIN-documentation#135No surface does anyone else's job. No auth chrome on
my.opensin.ai. No pricing/checkout onopensin.ai. No marketing hero onchat.opensin.ai.Platform Launch Gates
The 3 code repos that every surface depends on:
OpenSIN-Codecurl | shexperience)OpenSIN-backendOpenSIN-WebAppchat.opensin.aiapp (same as the surface row above)Biggest known platform blocker: CP1 — merging
Core-SIN-Control-PlaneintoOpenSIN-backend. Tracked:OpenSIN-backend#1171+Core-SIN-Control-Plane#17.Second biggest: R1 —
OpenSIN-Codevsopensin-ai-climerge/split decision. Tracked:OpenSIN-Code#1116.V1 Agent Fleet
V1 does not ship all 80 agents. V1 ships 3 flagships that work end-to-end through
chat.opensin.aion launch day. Everything else stays listed in the marketplace but is labelled "coming soon" until its team cuts its own quality gate later.A2A-SIN-MiroFishA2A-SIN-X-TwitterTeam-SIN-SocialA2A-SIN-DiscordTeam-SIN-MessagingFleet hygiene (blocks nothing, but do it before V1)
OpenSIN-overview#39— 20+ duplicate "Governance Contract Adoption" issues + test-spam across 12 repos. 15-20 minutes ofgh issue closework. Script-able.What I am NOT asking for right now
A2A-SIN-MiroFish#147).A2A-SIN-Code-*scaffolds until R1 (#1116) is decided. Their fate is coupled to that decision.Delegation table — who owns what
opensin.ailaunchwebsite-opensin.aimaintainermy.opensin.ailaunchwebsite-my.opensin.aimaintainerchat.opensin.ailaunchOpenSIN-WebAppmaintainerdocs.opensin.ailaunchOpenSIN-documentationmaintainerOpenSIN-CodemaintainerOpenSIN-backendmaintainerTeam-SIN-SocialTeam-SIN-MessagingHow progress is tracked
If you land on this issue and your team is not in the table: you are not on the V1 critical path. Your work is valuable but does not block launch. Keep doing it, but do not expect cross-team attention before V1.
All prior ad-hoc "Big Boss" / Governance Adoption / Roadmap issues across the fleet are superseded by this one. If the acceptance criteria of one of those overlaps this, close it and link here.
Co-authored-by: v0[bot] <v0[bot]@users.noreply.github.com>