Causet turns fragile workflows into replayable timelines.
Causet sits beside your existing app. It does not replace your frontend, database, queue, or services. Your app submits intents. Causet records events. Projections and queries expose current state. The timeline can be inspected, forked, replayed, or repaired.
Choose your path
Three distinct ways to start. Pick one — you do not need the interactive learning environment first.
State, intents, events, projections, queries, timelines, and replay — in plain developer language.
Learn the Causet modelInstall the CLI, start Docker, create the wallet demo, submit an intent, inspect the timeline.
Run the local quickstartKeep your API. Move one fragile workflow into Causet without rewriting the system.
Retrofit an endpoint| Path | Best when | Start |
|---|---|---|
| Learn the model | You want the mental model before tooling | Mental model |
| Run locally | You want a real runtime in ~5 minutes | Local quickstart |
| Retrofit | You already have an API / service | Retrofit overview |
The interactive learning environment (browser) teaches the model without Docker. It is not equivalent to the local runtime. Prefer the local quickstart to validate a real integration.
What runs today?
Causet has a supported production core, a local development stack, and capabilities in controlled early access. Replay operations are distinct — timeline inspection, projection rebuild, forking, and snapshot rehydration re-apply recorded patches without re-running DSL rules. Forensic replay check, recovery stream replay, and repair execution are Preview sandbox tooling.
See What runs today? for environment-specific production support and Support policy.
Docs map
| Section | Start with |
|---|---|
| Start here | What runs today? · Install · CLI |
| Core concepts | Mental model · State · Intents · Events |
| Integrate | SDKs · Webhooks |
| Operate | Debugging · Replay · Deployments |
| AI | AI in Causet — additive, not the only use case |
| Reference | DSL · Compiler errors |
| Examples | Examples |
You still own
Frontend, API contracts, primary database, queues, workers, vector DB, and third-party clients. Causet is the deterministic state layer for workflows where correctness, auditability, replay, and repair matter.
Next step
New to Causet? See What runs today?, then Run the local quickstart.