zava-constellation

Fork an agentic substrate into a customer-flavoured digital clone using an org-brief YAML (from research-company) + the matching industry primer. Clones the substrate to a sibling repo, rebrands literal tokens, repacks the data-fabric generators against the brief's subsidiaries + named ELT, swaps the Kuzu entity-kind tables per the primer, extends the domain registry with the primer's workflow library, generates personae (ELT named from the brief, archetypes from the primer), seeds cadenced rituals + narrative arcs, and scaffolds Node MCP mocks for the brief's stack overrides. Local-only fork by default; no GitHub push. Refuses dirty trees, idempotent re-runnable. USE FOR: fork the substrate for a named customer (Telco, FSI, Airline, Retail, OEM, …), produce a digital-clone-grade demo repo. DO NOT USE FOR: incrementally adding one domain (use compose-domain inside the fork — planned, not yet available), authoring a new substrate from scratch, pitch decks.

Emit a thin org-brief YAML profiling a target organisation — the company-specific overlay that pairs with an industry primer to drive a digital-clone-grade substrate fork. The brief captures only what the vertical can't infer: identity, ownership, size, geography, ~10 subsidiaries, the named ELT, 3–5 strategic themes, and any stack overrides the company publicly disclosed. Function tree, regulator set, entity kinds, proposed-domain library, rituals, KPIs all come from the matching industry primer. Four-phase procedure; claims carry confidence + sources[]; gaps go in uncertainties[], never invented. USE FOR: profile a company before a customer pilot, generate an org-brief, prepare a customer-flavoured demo fork. DO NOT USE FOR: single-process design (use threadlight-design), pitch-deck authoring, code generation, exhaustive personae harvest (compose-org expands archetypes via faker at fork time).

Deploy the Zava agentic-org control plane to Azure Container Apps via azd (Azure Developer CLI). Single uvicorn process: FastAPI backend (462 files, 38 domains, 48 routes, 46 MCP tools, 62 agent graphs, 19 ambient agents, KuzuDB entity graph, working memory, AGT governance) + 3 React/Vite SPAs served via Starlette StaticFiles. Bicep infra plugs into existing shared resources (ACR, App Insights, Citadel APIM). UAMI + RBAC — keyless everywhere. USE FOR: deploy Zava, Zava workspace, Zava control plane, Zava ACA, Zava azd, Zava container, Zava to Azure, Zava Citadel, agentic org deploy, zava-control-plane, deploy control plane, Zava demo deploy, Zava cloud, Zava APIM, azd up zava. DO NOT USE FOR: Threadlight agent deploy (use threadlight-deploy), Threadlight workspace UI (use threadlight-workspace-ui), Citadel hub setup (use citadel-hub-deploy), Foundry agent deploy (use foundry-hosted-agents).