Status: reframed — work in flight in a separate Claude Code session
This issue is documentation of the canonical stack, not a task list. Execution is happening in a separate session against the Nyuchi Console monorepo.
The correct stack (updated for 4.1.x DNA helix)
The central platform is the Nyuchi Console, a monorepo at platform.nyuchi.com consisting of:
- SvelteKit app on Vercel (the Console UI)
- FastAPI servers (the platform APIs)
- Cloudflare Workers baked in as components — workers are parts of the Console, not the Console itself
There is no mukoko-edge. Earlier issues that referenced mukoko-edge as a standalone Cloudflare Worker gateway were based on a pre-4.1.x topology that no longer applies. The gateway role lives inside the Nyuchi Console monorepo.
NYUCHI CONSOLE — platform.nyuchi.com (monorepo)
├── SvelteKit on Vercel Console UI
├── FastAPI servers Platform APIs
└── Cloudflare Workers (baked in) Edge components
DESIGN PORTAL — design.nyuchi.com
├── SvelteKit on Vercel Live, existing
└── consumes Mzizi registry via the canonical DB function set
CANONICAL DB — nyuchi_design_db (Supabase: grjsboqkaywpwatvrzmy)
├── component_documents 2,132 docs across 52 named collections
├── versions collection beside it 4,865 entries (one document-format store)
├── 5 event tables usage, observability, chaos, healing, issues
└── legacy schema 48 deprecated tables, scheduled for DROP after cutover
CLI
└── @nyuchi/mzizi-cli (in development — see FRD-30)
What changed since this issue was first written
| Then (v4.0.33–v4.0.44) |
Now (4.1.x DNA helix) |
mukoko-edge Cloudflare Worker as standalone gateway |
Nyuchi Console monorepo (platform.nyuchi.com) — workers are components within it |
architecture_layer (text) |
ecosystem_node (int) — superseded again by named collections in 4.1.0 |
n0–n10 numbered nodes |
named collections (primitives, styling, accessibility, …) |
| 66-function legacy SQL surface |
~12-function canonical set: read_documents, put_document, read_versions, query_events, emit_*, log_release, record_doctrine_change, get_system_counts, schema.org/JSON-LD via read_documents_jsonld |
Reference data duplicated across brand_* / architecture_* / ubuntu_* tables AND component_documents |
Single source of truth: component_documents only; old tables in legacy schema |
Related current work
Action
No execution work remaining on this issue. Reframed as historical record + current-state documentation.
Status: reframed — work in flight in a separate Claude Code session
This issue is documentation of the canonical stack, not a task list. Execution is happening in a separate session against the Nyuchi Console monorepo.
The correct stack (updated for 4.1.x DNA helix)
The central platform is the Nyuchi Console, a monorepo at
platform.nyuchi.comconsisting of:There is no
mukoko-edge. Earlier issues that referencedmukoko-edgeas a standalone Cloudflare Worker gateway were based on a pre-4.1.x topology that no longer applies. The gateway role lives inside the Nyuchi Console monorepo.What changed since this issue was first written
mukoko-edgeCloudflare Worker as standalone gatewayplatform.nyuchi.com) — workers are components within itarchitecture_layer(text)ecosystem_node(int) — superseded again by named collections in 4.1.0n0–n10numbered nodesprimitives,styling,accessibility, …)read_documents,put_document,read_versions,query_events,emit_*,log_release,record_doctrine_change,get_system_counts, schema.org/JSON-LD viaread_documents_jsonldbrand_*/architecture_*/ubuntu_*tables ANDcomponent_documentscomponent_documentsonly; old tables inlegacyschemaRelated current work
Action
No execution work remaining on this issue. Reframed as historical record + current-state documentation.