The world
Softanza models a thing by asking what it essentially is. An application, stripped of its plumbing, is a living world of meaning: made of a domain, a life and a body, and met from outside by being seen, engaged, tuned and reached.
Made of three things
The domain: its being
The world's things, what is true of them, and how they relate. Things are nodes and relations are edges, so the domain is a graph. Truth is a conscience and not a syntax: each thing declares what should hold, such as a balance that is never below zero, and validity is part of the world's being. Meaning is first-class: an account belongs to a client is written as knowledge.
The life: its becoming
What the world does and what it wants. Its behaviour is how it reacts when something changes. Its purpose is a goal that does not say what to do and says what should become true, with plans that pursue it.
The body: its embodiment
Where the world endures: a graph, files, memory. A world's substance persists as the graph it is. The governed store beneath it is told on its own page.
Strip any of the three and there is no world.
Met from outside in four ways
- Seen. The world has a presence: it can be looked at, in whatever surface.
- Engaged. It has an intent: a person or an AI agent can ask it something and do something with it.
- Tuned. It can be refined: changed under governance, with the change judged before it lands.
- Reached. It has a reach: it appears on a surface, on the web today and elsewhere as the surfaces are built.
Strip these four and the world still lives, headless. That is why one construct can be a business tool, an agent, a game or a simulation.
Built from what already exists
The construct animates organs that exist elsewhere in the library: the graph, the workflow, the reactive engine, the Softanzuter's ladder, goals and plans, data, and the application server. See the Softanzuter and the host.
built The guards judge a world's being and its reactions, and a constellation of worlds has its own guard; the stage of each plane is on the applications page. The design documents say it in the order above: the construct(opens in a new tab), the body(opens in a new tab) and the purpose(opens in a new tab), and a narration builds one: your first app.