Standalone release object
Sanctuary Core
Sanctuary Core is the adaptive-first shell and proof path for Sanctuary. It exposes a bounded local agent workspace with visible continuity, explicit authority, and a clean path from daily work into higher-scrutiny controlled work.
Adaptive Workspace
The broad public wedge. Start here for daily persistent work, recent artifacts, recall, and a useful local workflow without leading with compliance-heavy framing.
Controlled Workspace
The higher-scrutiny mode. Use it when work must be reviewable, defensible, and traceable across handoff, challenge, or later inspection.
Shared trust substrate
Both workspaces sit on the same core law: query stays advisory, exact continuity id stays authoritative, packs stay frozen, provenance stays visible, and the runtime stays bounded.
Quickstart
This is the shortest truthful local path to a working Sanctuary Core demo and proof viewer on the current system.
cd E:\Sanctuary\products\civitas-analytica python -m tools.agents.shell.cli doctor python -m tools.agents.shell.cli demo python -m tools.agents.shell.cli viewer --latest python -m tools.agents.shell.cli recent
Buyer-legible demo path
- 1.Run `doctor` to confirm the local environment is ready for the governed demo path.
- 2.Run `demo` to materialize one compact Sanctuary Core demo bundle over the known-good bounded path.
- 3.Run `viewer --latest` to render the current static proof viewer without looking up raw bundle directories.
- 4.Run `recent` to inspect the latest demo bundle, viewer, proposal, pack, and trace artifacts in one place.
Current live status
Observed at
16 Apr 2026, 18:23
Doctor
unavailable / pass 0 / warn 0 / fail 0
Latest demo bundle
No demo bundle yet
Run `python -m tools.agents.shell.cli demo` to materialize the current proof bundle.
Latest viewer
No viewer yet
Run `python -m tools.agents.shell.cli viewer --latest` to render the current static viewer.
Curated proof path
The current public proof path is summary-first: doctor status, advisory query result, proposal, selected authority, why/trace, and artifact paths. It is designed to be inspectable without hidden memory claims.
The operator prototype remains a local bridge-facing surface. It is useful for the current build, but it is not the public release object.
Standalone release boundary
Inside now
- bounded shell commands and the Sanctuary Core shell lane under `tools/agents/shell/`
- the public proof viewer route under `/api/sanctuary-core/viewer`
- the release-facing public route under `/products/sanctuary-core`
- the release README under `sanctuary-core/README.md`
- the current TS bridge that reads shell JSON contracts for the public and local Sanctuary Core surfaces
Bridge-facing for now
- runtime and loader machinery still physically hosted in the Civitas repo
- current site wrapper and Civitas locale routing
- the local operator prototype under `/command-center/sanctuary-core`
Outside release object
- EPI Rail product, purchase, proof, and verification surfaces
- team or enterprise operator layers
- connector packs, domain packs, and customer-specific integrations
- future Tauri packaging and future enterprise distribution work
Public vs premium boundary
- Public/open shell: shell commands, proof flow, static viewer, release README, trust semantics, and the current public release route.
- Premium/proprietary later: curated workspace packs, higher-value connectors, team/operator surfaces, enterprise controls, and customer-specific hardening.
What Sanctuary Core is not
- Not a compliance-only product.
- Not a hidden-memory chatbot.
- Not an unbounded autonomous swarm.
- Not a team or enterprise operator suite yet.
- Not Tauri-packaged yet.