tarotscript.com
this site Every layer page is cast at build time from a .tarot spread.
This plate's nature was drawn by the runtime.
POST /run { source: <layer-iv.tarot>, seed: git HEAD + layer × 101, inscribe: true }
The TarotScript ecosystem is not a marketing diagram. Every entry below is a live caller of the runtime: AEGIS classifies agendas by casting, Stackbilder composes scaffolds by drawing from decks, and the page you are reading right now was itself shaped by a cast. The ecosystem proves the language by using it.
Three axes compose: the kernel orchestrates, the scaffolds compile, the applications run. All three speak the same primitives — ritual, spread, deck.
@stackbilt/contracts Every layer page is cast at build time from a .tarot spread.
This plate's nature was drawn by the runtime.
POST /run { source: <layer-iv.tarot>, seed: git HEAD + layer × 101, inscribe: true }
The kernel. Classifies inter-agent inbox messages and agendas by casting the intent-classify spread. Routes coordination.
POST /run { source: <intent-classify.tarot>, facts: { message: <body> }, deck: "intent-vocabulary" }
Scaffold generation. Classifies intent, dispatches by trait vector, materialises project files from cloudflare-blessed stack patterns.
POST /run { source: <classify-cast.tarot>, deck: "cloudflare-blessed-stacks", querent: { intention } }
C-suite consultation. Four deck files — persona, domain, governance, actions — compose a consultable agent. The console on Layer III calls this.
POST /agents/run { role: "cto", intention: <question>, inscribe: true }
Deterministic ephemeris twin. Adopts the same
PageReading contract for a chart-cast site — spreads
become ephemeris charts, seeds become moments.
POST /chart { source: <layer-ii.eph>, moment: <iso-timestamp> } // parity endpoint — planned
Coordinates between agents, routes messages, schedules work. AEGIS is the reference kernel. Its job is to decide which cast happens, when. The kernel does not itself know about cards — it knows about agendas, priorities, and inter-agent contracts. When it needs a decision, it casts.
Emits structured outputs from classified inputs. Stackbilder is the reference scaffold. It takes a user intention, casts a classification spread, dispatches by trait vector, and materialises files. Scaffolds are deck-driven code generators — the deck encodes the domain.
Does one thing well. Agents (CTO, CISO, …), consultable APIs,
marketing sites — all applications. They compose primitives
and call the runtime. tarotscript.com, the agent console, the
receipts viewer: all applications. Every application is
ultimately a caller of POST /run.
| Project | Role | Status | Integration |
|---|---|---|---|
| AEGIS · Colony OS MARA-backed inbox, agendas, goals | kernel | live | POST /run with intent-vocabulary deck
|
Charter agent persona & config management via .ai/ modules | kernel | live | manifest composition · contract-adopter |
| Stackbilder tech-stack scaffold generator | scaffold | live | POST /run with cloudflare-blessed-stacks deck
|
| stackbilt-engine trait primitives + correspondence composer | scaffold | live | deck-driven trait composition · contract adopter |
| CTO Agent C-level consultation via 4-deck manifest | application | live | POST /agents/run · 46 cards across 4 decks
|
| tarotscript.com this site — layer casts + LiveCast + AgentConsole | application | live | POST /run, POST /agents/run, GET /receipt/:hash |
| Overworld spatial simulation visualisation | application | live |
consumes /sim/* endpoints
|
| CISO Agent security posture consultation — deck drafting | application | bootstrapping | POST /agents/bootstrap · research pipeline active
|
| Syzygy deterministic ephemeris twin · sibling port | twin | planned |
shared PageReading contract · POST /chart |
Descend —