Browse documentation
From functional programming
Use a deterministic core for decisions and explicit effects for interactions.
Septa separates deterministic computation from environmental interactions. Rust types describe values and outcomes. Effects make operations visible to the runtime; scoped grants control whether they may execute.
Coding agents write within the Rust profile. You can inspect and edit that source directly.
Put the decision in the core
For a stock reservation, positive quantity and sufficient stock can be checked from explicit inputs. Fetching stock or requesting its owner to reserve it is a separate interaction.
Checked integers and exact decimals define core arithmetic. Scale, rounding, range and invalid-input policy still belong to the application. Floating-point work needs an explicit native boundary.
State, permissions and replay
- Actors can own state while running deterministic code. Repeatability depends on the code, inputs and execution contract.
- Effect declarations describe operations. Grants and runtime checks determine permission.
- Replay uses recorded outcomes instead of issuing new external requests.
- Tests and proofs must check the application’s intended behaviour. A repeatable result can still be wrong.
Septa’s compiler tracks typed operations through function calls. The runtime executes those operations and resumes the code waiting for their answers. The profile does not expose continuations to application code or let it define general effect handlers. Effects, handlers and Septa explains these choices and compares them with Unison and OCaml.
Start with the library tutorial. Follow it with determinism and code evidence to inspect how a result relates to its inputs.