A rationale before it is a bridge

Seven languages, one door

A solution has layers, and each layer has a language that is best at it. Softanza chose seven, and one that orchestrates them. This page tells why each was chosen, how the door to them works, and what its own record cannot yet say.

The rationale

The door was never a way to run anything. It is a position: a solution has layers, each layer has a language best at it, seven were chosen and one orchestrates, and a programmer of any of the seven enters through the layer they know.

System performance: C. Low-level operations and performance-critical algorithms.
Event-driven systems: NodeJS. Asynchronous processing, real-time flows, API orchestration.
Scientific computing: Julia. Mathematical modelling and numerical simulation.
Statistical analysis: R. Data transformation, statistical modelling, plotting.
Logical reasoning: SWI-Prolog. Rule-based systems, knowledge representation, backtracking.
Machine learning: Python. Model training and the data-science ecosystem.
AI reasoning: the model. Natural-language understanding and knowledge synthesis, as a faculty and never the definition of the mind.
Solution integration: Softanza's own language. Business-logic orchestration and cross-domain data transformation.

The enemy it names is orchestration friction: developers spending a large part of their effort on the plumbing between languages. The answer for the agentic age is to neither force a developer to master every domain nor surrender to code generated for them, but to craft abstractions that expose each domain's power through simple functions.

Two doors

Run foreign code where it lives

The code is written to a file, the runtime is run as a process, and the result is read back and converted. The verbs are to set the code, execute it, read the result, read the duration of the last call, and read the trace of the calls. The runtimes are found by paths from the configuration.

Paste foreign code where you are

Find a solution on the internet in another language, paste its code, and make little changes. Shims exist for C, C#, JavaScript, Perl, PHP, Python and SQL.

Two things will carry the word language, and they must not be confused. A facet of Haro is a surface: one grammar, judged by one court, worn in another syntax, so a programmer writes Softanza in a syntax they already know. A door is a runtime: real Python with its libraries, real R, real Prolog, reached from the solution and returning its result into the world. The facet brings the programmer. The door brings the ecosystem. They meet in the same person.

named Haro's planned facets, in the author's statement of 2026-10-07, are its present face today and, planned, Python and JavaScript. The language's charter does not name them yet, so this page records the plan as the author's and not as a specification.

The honest state

in construction The door is process-based today: it runs by spawning and by files. An engine bridge that would handle marshalling and process management is planned, and its list of languages (five) does not match the rationale's (eight). The door has fifty-eight guard files, with a run script per language. The last recorded run of them shows thirty-eight failures and no pass, and several of their promises cannot match by construction, because they name a random temporary file or a duration. So the run record does not say whether the door works, and this page runs nothing: it will not show a run that its own guards cannot confirm.

The door's performance was set against the field in an article of the library, which publishes the host's losses: a million numbers sorted took far longer through the host than in Python. That measurement predates the present runtime and is owed a re-run, and a loss that stands will be published as it stands.

Sources: the articles polyglot programming, domain-driven polyglot programming and the performance battle, whose code mostly does not run in this site's runner for lack of the runtimes. The record was read from the library's files by an outside assessment on 2026-10-07; nothing was run for this page.