Clear boundaries.
Room to build.
As agents write more of our software, people need better ways to understand the systems taking shape.
Code is easier to produce than ever. Understanding what that code may do, how its parts communicate and what happens when something fails is still a human responsibility. Septa brings those questions into the development model.
A system people can guide
Agents are the primary code authors. People define intent, shape architecture, set boundaries and assess behaviour. Durable actors with typed contracts, explicit effects and precisely scoped capabilities give both a common language.
That model should stay connected to the code and its execution evidence. A diagram should help you inspect a real contract. A test should identify the code it checked. An operation should have a clear source of authority.
Rust, with a different development experience
Septa is a new way to build with Rust. A carefully defined profile brings Rust into a deterministic core and a development loop without a native build on every supported edit. Checking and lowering still happen; the feedback is part of the loop.
Native Rust remains available through explicit integration interfaces. That boundary lets you connect existing systems and specialised capabilities while keeping their build process, authority and recovery behaviour visible.
Safety before speed
We value safety and security over speed. An optimisation earns its place through evidence that the relevant contracts still hold. Tests, replay, benchmarks and formal proofs answer different questions; each needs a clear scope and set of assumptions.
A deterministic core and explicit interactions make behaviour easier to examine. They do not make business requirements correct by themselves. The person reviewing the result still has a vital role.
A foundation others can build on
Applications are one use. Libraries, databases and frameworks belong here too. A shared execution model makes it possible to build a domain workflow—or the reusable infrastructure beneath it—without assembling a new set of conventions for every layer.
Why Septa
Septa are the cross-walls that divide fungal filaments into compartments. Pores allow passage between them; in some fungi, specialised structures can close those pores after damage.
That is the idea behind the name: distinct parts, deliberate connections and limits on the spread of failure. It is a useful inspiration for the design. The actual software guarantees come from contracts, runtime checks and evidence.