Open specification · GegoLabs
AgencyDomains
Architecture of the Agentive World
The agentic world coexists with applications; the agentive one collapses them. Only the latter makes the real-time enterprise possible — the one that stopped using people as infrastructure. Three books map the transition: the destination, the route, the architecture.
The trilogy
- IThe Real-Time Enterprise · The Agentive World Where are we going? — the destinationbook · ~2 h · PDF · agents
The Real-Time Enterprise · in 2 minutes
In every organization, people hold two jobs at once. The visible one is what their title says: deciding, creating, selling, leading. The invisible one is infrastructure: moving information — reading and forwarding, meeting to find out, reporting what someone else already wrote, chasing replies, staying available just in case. That second job is the reason the day falls short — and it is exactly the one an AI agent can do whole.
The Real-Time Enterprise portrays the organization that acted on this. Its first half is a film in prose: an ordinary Tuesday of Elena, chief operating officer of an energy company, narrated hour by hour — no jargon, almost no explanations. Its second half is the director's commentary: the four faces of that world — the quantum leap in knowledge, Postchat in communication, the General Staff in coordination, the guard in availability —, the door you enter through (the agentive mode, optional and reversible), and the intelligent organization that emerges when the four operate together. Every chapter closes with the essentials; the book, with the agenda to start on Monday.
It is Book I of the Agentive World Trilogy, written for those who lead — no technical background required. The transformation path has its own book — AURA — and the architecture its own — AgencyDomains. This one shows the destination: the enterprise that stopped using its people as the wire — and the end of the day that exists again.
- IIAURA · The Agentive Path Which way? — the routebook · ~4 h · PDF · agents
AURA · in 2 minutes
Every major consultancy has its maturity instrument: the model it uses to measure where a client stands at a given moment, set its evolution targets, and chart the transformation plan. AURA — Agentive Unified Reference Architecture — is that instrument for the agentive era, and it is published.
Its organizing thesis: the agentive transformation advances along two axes that do not move together. KNOWING — turning data into actionable intelligence — and DOING — executing processes with growing autonomy. An organization can know a lot and do little: impeccable dashboards, bottled-up decisions. Or do a lot and know little: blind automation over data nobody governs. AURA operationalizes both axes in two diagnostic models — IRIS, the ten stages of knowing; MOTOR, the seven levels of doing — and accompanies them with the instruments to advance: Data Canon for data governance in the era when agents are the consumers, Wingmap to reconstruct the organization's real processes without interviews, from the digital traces its operation already produces, and the Portfolio method to turn a diagnosis into a prioritized casebook — illustrated with a real portfolio of one hundred cases.
AURA is diagnostic, not prescriptive: it says where an organization stands and what standing there means. The destination has its own book — The Real-Time Enterprise — and the architecture its own — AgencyDomains. This one is for those who have to cross — and, before anything else, for those who need to know where they stand.
- IIIAgencyDomains · Agentive Architecture How do we get there? — the vehiclereference · ~9 h · PDF · agents
AgencyDomains · in 2 minutes
The industry names the horizon — agents, copilots, autonomous workflows — but builds on loose language: plenty of marketing, little architecture. AgencyDomains is the missing specification: the formal architecture of the Agentive World, written with the discipline by which technical categories are established.
It starts from the paradigm — the Nadella Line, the question that divides the two worlds — and builds out its full consequences: a four-layer architecture under the Agent First principle; the eight primitives that inhabit it — from the AgencyDomain to the Botlet, from the Capability to the Agentlet —; the transversal Trust Infrastructure that makes autonomy governable; the two-dimensional map of the AI value chain, to position any player in the market; the canonical application of real-time knowledge; and a reference implementation: Vergis.
It is not an implementation manual — it is the specification a manual should respect. For architects, CTOs, strategists, and engineers building, evaluating, or governing productive agentive systems.
- IVVergis · Agentive Technology What do I start with today? — the keys code · GitHub · AGPL-3.0