A tentacular platform where meaning, intention and consequence become executable, traceable and reversible processes.
Mission profile
- Coordinate independent creative and technical systems through a stable control plane.
- Compile high-level intention into explicit, inspectable execution graphs.
- Preserve causality, provenance, state transitions and rollback boundaries.
- Connect Field Horizon, Cathedral, Necropolis and the Black Archive.
- Scale from local services to AWS without rewriting the conceptual model.
Architecture
Stated limits
What this project is not, written here so nobody has to discover it later.
- There is no repository behind this page. Nothing described here is implemented.
- The named modules, the causal ledger and any cloud topology are design intent, not running systems.
- Field Horizon and Pomegranate Command already do, locally and concretely, a fraction of what this architecture describes in the abstract. That is the honest comparison.
- This page is kept because the vocabulary is useful, not because a product is being announced.
The nervous system
Abracas means Axiomatic Branching and Ritualized Agentic Causal Architecture System. It is the control plane that translates intent into bounded, auditable action rather than letting agents wander through prose and hope for the best.
A federation, not a monolith
Each module keeps a distinct responsibility. Field Horizon handles meaning. Cathedral shapes doctrine and ritual structures. Necropolis manages decay, dead states and aftermath. The Black Archive preserves evidence. Leviathan turns their decisions into consequences.
Deployment doctrine
The first phase deliberately avoids Kubernetes, dedicated GPU fleets and graph databases unless proven necessary. Step Functions, ECS Fargate, S3 and Aurora PostgreSQL provide a sane cloud path, while local adapters preserve autonomy.