Semantic Capability Compiler
Whatever framework your agent runs on, this is the layer between it and your company. It turns your data and systems into a guide the agent understands; defines permissions and limits; binds processes into contracts; verifies every agent step against the contract and records it.
Agents are capable, companies are not boundless
The agent does not know your system
The model does not know what each endpoint of your ERP does; it guesses. In production a guess is a wrong record.
Permission is not inside the model
Who may do what is not solved by a prompt sentence. The boundary must live outside the model and independent of it.
HTTP 200 is not success
Legacy systems may accept a request and change nothing. Without verification the agent believes it succeeded and the job stays half done.
Five layers between the agent and the company
The agent's intelligence is not yours; the boundary, the guide and the evidence must be. The compiler produces them.
- 1
Data map
Reads your tables, API definition and files; gives columns business meaning, records relations, operations risk classes. The company's user manual for the agent.
- 2
Permission and limits
Role × risk × threshold. Who may do what, where a human must approve. Out-of-bounds requests never reach the system.
- 3
Process and contract
An execution contract for every task: which steps, in what order, what counts as success, how to roll back.
- 4
Supervision
Every agent step is checked against the contract: the record is read before and after the call, HTTP 200 is not trusted, unverified steps are rolled back.
- 5
Evidence
Who, what, why, outcome. Every decision in a timestamped audit log, ready for GDPR/KVKK and internal audit.
Your system in, the agent's contract out
- OpenAPI 3.x definition
- PostgreSQL / MySQL schema, Excel and CSV exports
- Role matrix and approval thresholds
- Capability graph: business meaning, risk class, read-back, postcondition, rollback
- Policy: role × risk × threshold
- Task contracts and MCP tool definitions
- Audit log: who, what, why, outcome
- OpenClaw, LangChain, MCP clients, your own framework
- Autonomous AI Staff (on the roadmap)
See six things with your own eyes
- 1Unauthorised role: zero calls to the system
- 2Silent failure: HTTP 200 but record unchanged, caught
- 3Rollback in a multi-step task: due date +15 days → −15 days
- 4Human approval above a threshold
- 5Every step verified separately
- 6Cited answers: table and row
Tested, documented, auditable
The compiler is protected by automated tests; every output it produces becomes a readable document.
The compiler is protected by 12 and the read engine by 13 automated tests: compilation, policy, planning, silent failure, rollback, selective recompilation, MCP publishing, scanning and masking. The website demo runs end to end with browser scenarios on every build.
The compiler's four outputs in one document: capability graph, policy matrix, contract-bound task records and audit log. Real output produced from the fictional ERP; the same format is produced from your API definition.
Download the sample output (PDF)Licensable today, matured together
Beta customers shape the roadmap. The price is fixed for the whole beta and every update is included.
- On-premise installation and a capability graph from your OpenAPI definition
- Role and threshold policy built with you
- The first five tasks bound into contracts and verified
- Audit log and MCP tool publishing
- Beta support commitment: reply within 1 business day, priority on critical bugs, monthly updates, a direct engineering channel
- Fixed price and all updates during the beta
- Sources: systems with an OpenAPI 3.x definition; PostgreSQL and MySQL data maps
- First installation scope: one system, one OpenAPI definition, up to 60 endpoints; larger definitions after a scoping call
- Model choice is yours: an on-premise open model or your own provider; in local mode no data leaves
- Support comes directly from the team that writes the product; a contractual service level arrives with the licensed release
- Adaptation for systems without a ready connector is quoted separately
What comes next
- 1Autonomous AI Staff performing tasks under the compiler
- 2Ready connectors for common Turkish ERPs
- 3Our own model: no dependency on an external provider
- 4A contract language: defining business rules without code
Frequently asked
Which agents does it work with?
It publishes capabilities as MCP tool definitions; any MCP client and any agent that can call OpenAPI can use them. The agent's model and framework stay yours.
Does my data leave?
In a deployment the model runs on-premise or at the provider you choose; in local mode no record leaves. In the website demo an external model only sees masked, matching chunks.
What does beta mean, what is the scope?
The licensed release of a working MVP. First installation: one system, one OpenAPI 3.x definition, up to 60 endpoints; PostgreSQL and MySQL data maps; role and threshold policy; silent-failure detection and rollback. Larger definitions follow a scoping call. Beta customers shape the roadmap; support comes directly from the team that writes the product, and a contractual service level arrives with the licensed release.
What happens with an operation that has no postcondition?
The compiler marks write operations without a read-back or postcondition as 'unverifiable' and leaves them out of MCP publishing; the agent cannot call them. During installation we add the conditions to the API definition together (x-postcondition); all 15 capabilities in the demo were made verifiable this way.
How is it different from Autonomous AI Staff?
Autonomous AI Staff is a read-only product sold today that connects to your data and answers with citations. The compiler is the layer that keeps any agent inside its boundary while it performs tasks. The goal is the staff working under the compiler; today they are separate products.
How does the process work?
A free first call, booked online or by phone; a capability graph and policy draft from your OpenAPI definition; on-premise installation; the first five tasks bound into contracts. Adaptation for systems without a ready connector is quoted separately.
Let's review your OpenAPI definition together
First call free, no data sharing needed. Book a call or phone 0 850 304 4758.
Book a call