Questions people actually ask
Why is the core free?
Because a manifesto you have to pay to practice isn't a manifesto, it's a paywall. The cores are small, auditable, and dependency-free on purpose. Fleet persistence, registries, and dashboards are roadmap work that will be priced only if and when they become a real service.
What counts as "one system"?
One deployed application with its own seam, ontology, and memory — however many models it calls. A monorepo with three products is three systems; one product with five model providers is one.
Do erasure receipts satisfy GDPR/right-to-be-forgotten?
Receipts are evidence of deletion, not legal advice — your counsel maps them to your obligations. What the design provides: predicate erasure with per-store receipts today; a durable release registry and auditor-readable exports are design-partner roadmap, not shipping software. On Canopy, deletion SLAs are contractual.
Can I pilot just one organ?
Yes. A design-partner conversation can focus on one boundary—ambiguity, ontology drift, or erasure—without implying that a hosted product already exists.