Aïcha
The Softanza AI agent: shipped with the foundation, shippable in any solution by giving it a knowledge base, and conversational wherever Softanza is. This page says what exists of it under other names, and what does not exist yet.
The definition
Aïcha is the Softanza agent, in the author's definition. It ships natively with the foundation. It is shippable in any solution by providing a knowledge base, and any customer can rebrand it as their own agent. It is omnipresent in Softanza as a first-class conversational interface to talk to or about the library and the applications built on it. And it is itself a programmable sovereign AI that anyone can make quickly, even without Softanza, from text files, a folder and one lightweight binary on any platform.
named No product ships under that name today. There is no binary named after it, no folder contract in force, no surface a person types into, no charter, and no packaging. What follows separates the organs that exist from the product that does not.
The folder that would make an agent
my-agent/ agent.pia who it is: name, kind, coverage, reversibility, schedule, governance, skills knowledge/*.zknw what it knows: facts, relations, an ontology, rules skills/*.pia what it can do: precondition, act, verification, effect charter.pset what it refuses to become: a signed predicate set persona/ how it speaks: name, languages, tone, the brand lexicon/*.zdlm the domain's own voice, when forged models/ optional local models and their checksums memory/ what it learns, as a governed graph with provenance transcripts/ the conversations, as records
The folder is written, not run. The binary that reads it would judge every file at load, answer from knowledge first with its reason, propose with a local AI model when one is present, never commit an effect without a governed actor, and leave a transcript.
What exists, under other names
The agent file and the folder as the deployment (built)
An agent is declared in its own file and a folder is its deployment. See the agent's journey.
Governance and the workbench (built)
An agent proposes, the workbench rehearses on a twin, and only a governed actor commits. See the agentic page.
The knowledge file and the domain's voice (built)
One knowledge file of entities, relations and rules; a deterministic model of the domain that answers from the graph with its reason. See wise coding.
The conversational door (built)
A governed conversation that generates its next question from a gap. See conversations.
Ask, HowTo and Explain (built)
The library answers questions about itself with no AI model. See ask the library.
The runner as one static binary (built)
The command-line runner that Softanza's tools already use.
The coding agent, refinement first
designed The industry's coding agents have good hands and the diff as their unit. A Softanza coding agent would change the unit: a typed refinement on a declared point, reviewed through the cascade it causes, shown before it lands; a five-stage gate; a workbench that holds the proposed version, so that only a governed actor commits; and the library's own knowledge, Ask and HowTo, instead of guessing, with the scenario guards as the court. An AI language model inside it would be one faculty, local, budgeted, and without the capability to act. The coding agents page calls this door decided and not built, and it still is.
Three conversations, one agent, once it exists: about the library, with and about an application, and as a customer's own agent.