Features
What Cassiel actually does.
Four capability spines. Each is load-bearing. Each is built by people who know what a real trial looks like at hour nine of a release cut.
Long-form feature pages — one per capability — are next on the roadmap. Today this page is a table of contents; the substance lives in product documentation and demos.
Schema-driven authoring.
Every study is a structured data object with governed edits. The Studio UI, the CLI, the REST API, and the MCP agent all write through the same versioned draft model. A site coordinator clicks; an agent scripts; the audit log tells the same story either way.
Signed, durable release pipelines.
Every published release is a Cloudflare Workflow run: ten deterministic steps, artifact signed with HMAC-SHA256, written to an R2 bucket with indefinite retention. Study workers verify signatures before serving. Rollback is a pointer swap, not a redeploy.
Translation as a governance primitive.
Paraglide-typed catalogs across every locale Cassiel supports. When the source locale publishes, every other locale flags stale-vs-source. Translators see what changed; operators see who's caught up.
Themes that are designed, not configured.
Three themes ship in the catalog today — Clearwater (narrative), Meridian (editorial), Foundry (utility). Customers choose a theme and configure it within declared knobs; they don't build one from a form. The catalog grows by curated additions.
Want to go deeper?
The architecture doc, the API reference, and the MCP tool surface are all available on request. Send a note to hello@cassiel.app.