Orchestrata Ultimate / Table of contents

Table of Contents

Every family of orchestrata-ultimate pages, in the order a newcomer should read them: the whole story first, the detail last. If you have five minutes, read Orchestrata, explained and stop. If you are here to change code, work down the list. The hub has the same families with a short explanation of each; the module docs index is the alphabetical lookup of packages.

1 · Start here

Orchestrata, explained: what orchestrata is, its concepts, layers, request lifecycle, data, environments, tooling, workflow, specs and RTM, and the components cut-over.
Project hub: one section per page family, and the per-package table.
Starting context: the first-hour orientation; the rules that bind hourly.
Glossary: every term, each linked to its page.
Project overview: the former one-page tour, now a pointer to the overview.

2 · Architecture

Architecture: the six layers, the packages, the runtime pieces, persistence rules.
Architecture diagram: the full-size system diagram.
Component DAG: the ten component packages and their edges.
Runtime services: the runtime view; every host unit, why it exists, what breaks without it.
The volks: the agent roles, prompt suites and handoffs.
Architecture ontology · AST diagram: package dependencies · Architecture migration 2026-09
Messaging and the kernel: gRPC retirement (cxpt) · Pipeline-event convergence · Kernel dispatch-reply hardening · Kernel fd leak and env ownership · SessionHandler split
Governance and Prolog: Free-threaded Prolog (the POC page points there) · Governed action classification (SPEC-034) · The Prolog layer does not learn · Ruleset engine: complete picture · Ruleset design review · Ruleset build inventory
Graphs: Semantic graph · KG migration to orchgraph · Graph engine analysis · Graph DB best practices · Graph browser

3 · Code reference

Code reference index: generated, one page per module, at revision 8a2cb42ad.
- orchestrata_ultimate: package pages at /projects/orchestrata-ultimate/reference/orchestrata_ultimate/<pkg>/index, module pages at .../<pkg>/<module>.
- Component packages · orchestrata_ast · orchestrata_tools · scripts
Module docs index: the curated package narratives under modules/: agents · context · core · cxp · di · domaingen · drivers · factory · gateway · governance · harness · integrations · kernel · knowledge_graph · llm · memory · openspec · orchestrator · planning · plugin · postman · promotion · providers · refactor · semantic_graph · session · tools · verification

4 · Workflow & gates

Workflow · Workflow improvements
Gates master index: every gate, one page each.
Bug fixes · Bug-fix log
How we work (process and delivery) · Tool approval gate · Silent-failure classes

5 · Deployment & operations

Deployment · Ship and deploy · Deployment sequence · Deployment inventory · Runtime services
Isolated test fleet · Reproducibility and IaC
Runbooks · Replicate the environment · Blockers

6 · Tests & reports

7 · Specs, RTM & briefs

Specs index, with one page per spec at /projects/orchestrata-ultimate/specs/<spec-dir> (for example 000-orchestrata-cli and 001-kernel).
Requirements traceability matrix
Briefs: how briefs are written, and the templates · Dispatch ledger
Spec word cloud

8 · Decisions & plans

Decisions · Open decisions · Rulings canon
ADR index (a page per factory ADR, relations, counts) · Rulings overview (enforcement, citing ADRs, gate pages)
Plans · Upcoming work
Components refactor status 2026-10-17 · The components swarm and the deterministic pivot
Measurement retention and rule induction · Org-mode rejection (ADR-021)

9 · Sessions, tasks & research

10 · Tooling & Claude Code

11 · FAQ

Elsewhere in the wiki

Rulings canon · Glossary · Prolog atlas
Concepts: A checker must prove it looked · Gates must separate the artifact from its description · Semantic graph
Infrastructure: Gateway · Kernel · Redis · Memgraph cluster · Memgraph HA cluster reference · Incus containers
Reference: URLs and ports · Container IPs · Environment variables · Commands