CIVITAS

Products

Civitas currently presents two primary product lines. Sanctuary Core is the adaptive and controlled local workspace line. EPI Rail is the portable evidence-pack, verification, and reviewer-ready delivery line.

Portfolio root

Choose the line first, then the supporting system depth

This route is the portfolio root, not a components catalog. Start by choosing the product line. Sanctuary Core is for serious local agent work with visible authority and bounded proof. EPI Rail is for portable reviewer-ready evidence packs with deterministic outputs and local verification.

Primary product lines

Primary product line

Sanctuary Core

Serious local workspace and agent-system line for persistent work, explicit authority, visible provenance, and a bounded path from adaptive daily use into controlled reviewable work.

  • Adaptive Workspace for continuity, recent artifacts, and useful local work without leading with compliance-heavy framing.
  • Controlled Workspace when work must be traceable, inspectable, and defensible across handoff or later challenge.
  • Trust-aware boundary: query stays advisory, authority stays explicit, provenance stays visible.

Sanctuary Core is now a first-class line on this route. It is not positioned as a hidden internal artifact or a loose side surface.

Open Sanctuary Core
Primary product line

EPI Rail

Portable evidence-pack and verification line for teams preparing concrete reviewer-ready material across pinned library baselines, with deterministic outputs and local verification.

  • Bundled local Windows runtime with offline generation, portable review artifacts, and local verification.
  • Proof-first posture: public proof, local verify, and packaged purchase paths remain the clearest support routes.
  • Packaged Duo is still the direct-buy path; Rail Core and Pro remain narrower supporting lanes.

EPI Rail remains a major product line, but it no longer has to carry the whole portfolio route by itself.

Buy EPI Rail
Supporting routes

Proof, verify, and purchase remain important orientation routes, but they sit beneath the product-line decision instead of replacing it.

Purchase
Direct packaged EPI Rail path for the current live commercial entry.
Proof
Public proof previews and current verification posture for the evidence-pack line.
Verify
Local verification model and inspectable boundary for reviewer-ready artifacts.
Scoped engagement routes

Need a bounded delivery path instead of a packaged product path?

If neither primary product line is the immediate fit, use the scoped engagement routes for fixed-scope delivery work or custom intake.

Review Solutions
See fixed-scope routes for diligence response, trust audit, and governance support.
Request intake
Start the email-led path for custom packs, library questions, and scoped commercial follow-up.

Included system components

Modules deepen the system; they are not the portfolio root

Cupola, AEGIS, LEO, EPI Viewer, and EPI CLI sit below the product lines as included system components. They explain how the evidence-pack line is assembled and how supporting interfaces remain inspectable.

Keep the hierarchy honest: choose Sanctuary Core or EPI Rail first; drop into component depth only when you need system shape, bundle composition, or interface detail.

Orchestrator
LEO
Builds deterministic evidence packs from scoped inputs.
Pack compiler
AEGIS
Compiles reviewer-ready outputs from validated artifacts.
Evidence engine
Cupola
Included engine for provenance indexing and retrieval.
Verifier
EPI CLI
Verifies integrity and manifests locally with tamper-evident checks.
Review UI
EPI Viewer
Displays structured evidence for reviewer workflow.
Interface
Contracts/v1
Compatibility contract for module interoperability.

Public mirror of the interface used by the toolchain.