Reference: PRODUCT-VISION.md § Offene strategische Entscheidungen and STATE-OF-THE-UNION.md.
These five are blocking the next marketplace launch and the next marketing push. Each is a "one decision + one PR"-sized thing, not a sprint. All five together are 5-6 days of focused work.
1. UI-layer role conflict — who does login + billing?
Today website-my.opensin.ai and OpenSIN-WebApp both describe themselves as the user-login + billing surface.
Proposed split (PRODUCT-VISION.md § UI-Schichtung):
2. Marketplace mechanic — are Team-SIN-* code packages or metadata manifests?
All 17 Team-SIN-* repos are 26-35 kb — too small for real code, too big for pure metadata.
Proposed answer: Option A — metadata manifests. Agent logic stays in A2A-SIN-*, teams are team.json + marketing copy + pricing.json. SSOT registry is the existing oh-my-sin.json in Infra-SIN-OpenCode-Stack.
3. OpenSIN-backend vs Core-SIN-Control-Plane — naming disambiguation
Both have "control plane" in the description. Either merge, or give them non-overlapping names and docstrings.
4. Team-SIN-Code-Core integrity check
57 kb after consolidating 3 repos is suspicious. Either Wave-1 lost code during the squash-merge, or the monorepo is still a skeleton waiting for content transfer.
5. Scaffold + dead repo audit
Evidence in STATE-OF-THE-UNION.md:
Close this issue when all five sub-bullets are DONE.
Reference: PRODUCT-VISION.md § Offene strategische Entscheidungen and STATE-OF-THE-UNION.md.
These five are blocking the next marketplace launch and the next marketing push. Each is a "one decision + one PR"-sized thing, not a sprint. All five together are 5-6 days of focused work.
1. UI-layer role conflict — who does login + billing?
Today
website-my.opensin.aiandOpenSIN-WebAppboth describe themselves as the user-login + billing surface.Proposed split (PRODUCT-VISION.md § UI-Schichtung):
website-my.opensin.ai→ marketing + Stripe checkout (unauthenticated)OpenSIN-WebApp→ authenticated dashboard atchat.opensin.ai(Stripe customer portal)Decision documented in PRODUCT-VISION.md
website-my.opensin.aiREADME updatedOpenSIN-WebAppREADME updated2. Marketplace mechanic — are Team-SIN-* code packages or metadata manifests?
All 17
Team-SIN-*repos are 26-35 kb — too small for real code, too big for pure metadata.Proposed answer: Option A — metadata manifests. Agent logic stays in
A2A-SIN-*, teams areteam.json+ marketing copy +pricing.json. SSOT registry is the existingoh-my-sin.jsoninInfra-SIN-OpenCode-Stack.team.jsonschema written3.
OpenSIN-backendvsCore-SIN-Control-Plane— naming disambiguationBoth have "control plane" in the description. Either merge, or give them non-overlapping names and docstrings.
START-HERE.md+CANONICAL-REPOS.mdreflect the split4.
Team-SIN-Code-Coreintegrity check57 kb after consolidating 3 repos is suspicious. Either Wave-1 lost code during the squash-merge, or the monorepo is still a skeleton waiting for content transfer.
5. Scaffold + dead repo audit
Evidence in STATE-OF-THE-UNION.md:
4 repos at 0 kb (
A2A-SIN-Facebook,-Mattermost,-RocketChat,-Slack)6 repos at 9 kb (
A2A-SIN-Code-Backend,-Command,-Frontend,-Fullstack,-Plugin,-Tool)17 Team-SIN-* at 26-35 kb
Audit script in
scripts/Output committed as
registry/SCAFFOLD_AUDIT.mdDead repos archived (4 confirmed)
Scaffold repos either promoted or archived
Close this issue when all five sub-bullets are DONE.