For an architect

Where to start

How Softanza is built, from the engine to the folders.

Your path

Every step carries its stage, in the words of the Estate page: built, in construction, specification, designed, named.

You declare a platform floor by floor, from the machine up to the organisation, and every floor is a text file you own with a judge beside it. This is the journey that crosses the whole vertical.

1. Write the guarantee sheet: five systems the solution answers to (technical, social, ecological, economic, cultural), and the standing promises to the people. No solution has a five-row sheet yet. designed · see: Platform of platforms
2. Model the solution and its targets, and write feature code in a deployment scope that refuses what the target forbids. built · see: From Dev to Deploy Without Leaving Your Editor
3. Declare the machines and the cloud: a file per box, a file for the links and the one way between them. Built and emulated; the cloud is two and a half steps of six. built · see: Sovereignty
4. Declare the data: an insert-only log, a chain verified on open, facts over time, a write as a proposal. Two rungs are built. specification · see: The estate, stage by stage
5. Declare the governance and the security: the regime, the lattice of capabilities, the secret store, the guarantees each tied to a guard. built · see: Security
6. Declare the worlds and the constellation in the organisation's own words: a world per person and device, the commons, the bonds, the norms, the roles. Built in the library; customers run it on web stacks. built · see: Platform of platforms
7. Rehearse the whole and commit it: emulate on the twin, then deploy to production through a plan with rollback, by an actor that may commit. Live hosts are gated by infrastructure. built · see: Deploying to the Target Sites
8. Put the agent in: its declaration, the knowledge file as its world, the empty effect set for a model. The agents are built; Aïcha is a name. built · see: Agents That Cannot Hurt You
9. Operate and evolve: two slots so an update is a trial before a commitment. The witness that checks every machine's record is ahead, and assurance behind it is a name. built · see: Sovereignty

The site, from where you stand

Platform

• Architecture · The core, base and max layers, the Zig engine beneath them, and the road to one executable.
• Lanes, cores, GPU, nodes · Lanes, cores, the graphics card and nodes under one measured dispatch.
• The host · The application host: the server, the live back end, the scale plane.
• From the editor to the device · From the editor to the device: a plan, a twin and a rollback.
• Safe agents · The agent proposes, a court judges, only a governed actor commits.

Vision

• Vision · The 2020 architecture drawing, read band by band against 2026.
• Sovereignty · Technically and educationally yours, and honest about lock-in.

Learn

• Writing · How Softanza code is written, so you can read what your teams write.

Reference

• Docs · The whole documentation: the reference of every area, and the narrations.

Adopt

• The estate, stage by stage · Every part of the estate, with its stage.
• Compared · Softanza against .NET, Python, Wolfram and the JVM across thirty domains.

What Softanza offers you

What you declare and what you get, with an example run: the “team that ships an application” door of the Adopt page.

The positioning sentence

Four floors are built with guards, two are built and only emulated, one is a specification with two rungs built, one is a name and one has no instance. A journey page may ship with its stage at every step, and this one does.