# Wosool | The Business Execution Operating System

> Wosool makes businesses executable: describe how your business runs, and every step runs exactly as defined, with every action authorized and recorded.

URL: https://wosool.ai/technology/

Wosool | The Business Execution Operating System - - - - - - - - - - - The Business Execution Operating System

## Businesses, made executable.
Wosool is a Business Execution Operating System. Describe how your business runs, and Wosool turns it into a governed program that executes every step exactly as defined, with every action authorized and recorded.
Explore Wosool See how it works Described A department asks for spare parts. Procurement gets the quotations, cost control approves, and nothing is ordered before that. Example Validated on return reason : budget -> CreatePr max 2 escalate role:project_manager
0 problems found Signed Approve PR Cost control approve Executed, on record Who decided, what, and when - Described How the operation runs
- Validated Checked before it can run
- Signed A named person decides
- Executed, on record The kernel acts and records
The shift

### Software became reliable when it became executable. Businesses are next.
Software became dependable once source code could be compiled into programs that run the same way every time. Businesses never got that step. How a business really runs lives in people's heads, in email, in spreadsheets and in applications nobody connected properly. Nothing checks it, and nothing records it end to end.
Coordination by hand
- People remember how it runs
- Many applications each holds a piece of the truth
- Manual coordination approvals lost in email and chat
- Operations
Undocumented, unaudited, inconsistent.
An executable business
AI, at the edge: proposes
- Business description how it should run
- NIL Script written precisely
- The kernel validate, authorize, execute, record
- Capabilities business verbs with a contract
- External systems behind the capabilities
People sign at every decision. Governance runs across the whole flow.
Written down, checked, authorized and recorded.
What Wosool is

### One environment where a business is defined, governed and executed.
Five parts. Each has one job, and only one of them acts.
The business language

#### NIL Script
How a business runs, written precisely: steps, roles, rules, decisions and approvals, waits with deadlines and escalation to a named role. What cannot run safely is refused before it runs.
The runtime

#### The kernel
Validates, authorizes, executes, commits and records. Nothing else does.
The means of operation

#### Capabilities and connectors
Cycles use business verbs, such as raising a purchase order. Connectors implement them for a specific system. The business definition never names the vendor.
Authority, built into execution

#### Governance
Every effect on a real system is a card a named person signs, and what is signed is what is executed. Every action, refusal and decision is recorded.
Understanding, never acting

#### The AI layer
Understands what a person wants, structures it and proposes: a filled card, a draft, a suggested value. It never signs, never commits, and holds no business state.
AI proposes. People decide. Wosool executes.
Meet NIL Script

### A language for how a business runs.
A cycle is written as a definition, not built as custom software. And the language refuses what cannot run safely. Take one real step and remove its escalation, and see what the checker says.
- Readable by people. Checked by the kernel.
- Refused with reasons, before anything runs.
- Authority lives in the definition, not around it.
Demonstrated: compiled and tested
The purchasing cycle that ran in production, from a need to the price received, is written in the same language.
From a real cycle: the spare part request, version 2.0.
As written Without the escalation 7 cycle SparePartRequest start manual by role:department { 10 label { ar: "طلب قطع غيار" ; en: "Spare part request" } 11 meta { version: "2.0" ; owner : "ops" } ⋮ 68 step ApprovePr { 69 task { 70 title { ar: "اعتماد طلب الشراء" ; en: "Approve PR" } 71 owner role:cost_control 72 outcomes approve , return 73 reasons { budget { ar: "الميزانية" ; en: "Budget" } } 74 shows $req.parts, $q.supplier, $q.quote_value, $pr 75 due previous . completed + 1d 76 } 77 on approve -> CreatePo 78 on return reason : budget -> CreatePr max 2 escalate role:project_manager 79 } ⋮
As written Accepted. The checker found 0 problems.
Without the escalation Refused before it can run. A limit with no one to decide past it is not allowed. ESCALATION_OWNER_REQUIRED a limit `max <n>` needs `escalate <owner>` (line 78, col 44)
- 71 Cost control owns this decision.
- 72 Two answers only: approve, or return.
- 75 Due one day after the previous step.
- 78 Returned for budget at most twice, then the project manager decides.
Built for AI. Governed by people.

### Let AI help. Never let it act alone.
Wosool is where AI can safely come close to a real business, because it can never cross from proposing to executing.
- AI reads the menu of what may be proposed.
- AI submits a structured proposal.
- A person reviews a card that shows exactly what will happen.
- The person signs, and the kernel executes.
- The record keeps who decided what, and when.
AI understands and proposes. It never signs, never commits, never decides.
The gateway through which outside AI agents propose is being built. Today it is not running in production. In development
An open standard

### NIL Script is open. One home for the language.
The language and its protocol are published as an open standard, with their specification, schemas and conformance tests. Wosool's site links to it; it does not copy it.
Read the standard at nilscript.org
The architecture

### One flow. One ledger. One line of authority.
The business is written once, validated, and executed only through declared capabilities. AI stays to the side. Governance runs across everything, and the ledger sits beneath it all.
AI Understands intent proposes a card - Business description How it should run
- NIL Script The business, as a definition
- Validator Refuses what cannot run safely
- Kernel Authorizes, executes, commits
- Capabilities Business verbs with a contract
- Adapters One per system, swappable
- External systems Odoo and Daftra today
Governance Signatures and authority, across the whole flow
The ledger One record of every action, refusal and decision. Everything else is a view of it.

#### Two steps for every change
A proposal first. The kernel commits only what is allowed.
Proven in production

#### A refusal is an answer
When information, identity or permission is missing, the step is declined and nothing changes.
Proven in production on 10 September 2026

#### Unknown risk waits
An action without a declared risk level is treated as high risk and waits for a signature.
Demonstrated: built and tested

#### Nothing is erased
Every proposal, decision and result stays on an append-only record.
Demonstrated: built and tested

### The next generation of businesses will be precise, governed and executable.
Wosool is building the operating system for that. Start with one operation, and see it run.
- A business can be written down precisely and executed, like software.
- AI understands and proposes. It never executes and never decides.
- Every action is authorized, deterministic, and recorded.
One operating system. Every business.
Talk to the team nilscript.org