The Registry
The register: every entry shows its numbers
In the register, organisations publish a process together with the numbers behind it — running cost, deployments, assessment. The first entry is our own, under the same rules as anybody else's.
No entry has been recorded on this instance. The structure below is the real one; the numbers are absent, and they are named as absent rather than estimated.
Where the entry hangs
Every capability tree starts at the running deployment itself. The entry is not a brochure page beside the product — it is the root node of the tree the product grows.
- Node
- procesos-instance
- Tier
- 0
- Unlocks
- procesos-workspace
- Entry
- not recorded yet
- Verification
- not recorded yet
- Passport
- not recorded yet
An entry without a Passport is listed on equal terms — not every solution needs one, and many produce evidence first.
The figures, and where each one comes from
- Running not recorded yet no figure recorded
- Deployments not recorded yet no figure recorded
- Overall not recorded yet no figure recorded
The same amount stands in the price list further down this page. A figure you can check against another chapter of the same document is a stronger claim than a link into a diagram.
How it is calculated
Task duration × the lane's hourly rate + task costs + system costs from the CMDB.
There is no public drill-down to individual tasks, and there will not be one: purchase prices and hourly rates do not leave the provider's workspace. What is shown is the method. What is shown as numbers is what each provider chooses to publish.
A payback period cannot be derived from public data at all — it needs the costs. What is public instead is how often the process has been rolled out.
Six dimensions, read off the processes
Assessors may add manual evidence. Nothing replaces the process data.
- Socio-economic impact not recorded yet everyone
- Environmental sustainability not recorded yet own instance
- Community engagement not recorded yet everyone
- Transparency & accountability not recorded yet own instance
- Scalability & replicability not recorded yet own instance
- Financial sustainability not recorded yet everyone
Three of the six dimensions read data from the systems beneath the process. An organisation that does not run those systems simply does not have the inputs — that is a missing basis for measurement, not a lower mark.
Sustainable Impact AIFOD Subcommittee 4 — FAIR Sustainable Impact Scoring Aligned with GRI, B Corp, the SDGs, ESG reporting and the EU AI Act.
Three levels of verification
A self-published entry standing on the lowest rung is not a flaw. It is the proof that the rungs are real.
- Community Published by anyone, unverified.
- University Verified by a partner university or a regional branch.
- National Nationally certified and carried into the national solutions register.
Two operating forms, each with its own path
Two questions that have nothing to do with each other: who runs the technology, and who does the work inside the workspace? The more an organisation takes on itself, the cheaper it gets.
Instance
Who operates the infrastructure
- Managed Operations sit with us.
- Co-managed Operations are shared.
- Sovereign Your infrastructure, your keys — and the cheapest of the three.
Still open: an instance's operating mode is not read automatically yet.
Workspace
Who does the work — mapping, governance, upskilling
- Stewarded A consultancy or partner places an engineer alongside you who maps the processes step by step. The way in: somebody else does it for you.
- Co-managed Usually a company with its regular managed service provider. The stated goal a stewarded workspace grows into.
- Sovereign Mapping, governance and upskilling sit in-house. The destination — and the cheapest form.
Still open: a workspace's operating mode is not read automatically yet either.
Four phases, four references
Each phase has a diagram of its own on the entry. Setup and Run are required, Change and Retire optional — and where they are missing, the slot stays visibly empty.
- Setup bound From nothing to running: systems, licences, roles, schedule.
- Run bound Operating the approved target state.
- Change bound Rebuilding while running: one approved state is replaced by the next approved state.
- Retire bound Winding a capability down because it is no longer needed.
These four phases are not a second cycle. The six-step cycle is what happens inside the Change phase — look at the six steps
Entries fork, and a fork keeps its origin
An entry adapted for another region stays attached to the one it came from. Certification is not the end of the line: other places take an entry over, adapt it, and certify it themselves.
- Origin
- not recorded yet
- Depth in the chain
- not recorded yet
- Adaptations
- not recorded yet