Activate
A schema does not run a business. The third phase of the CORTX method puts the agent into the daily life of the organization.
From schema to operations.
The Vertical Spec describes how work should happen. Activate is the work of making it happen.
Activation is not a software install. There is no kickoff meeting where the system goes live and everyone is trained. Activation is a series of small, observable changes inside the organization, week by week, until the agent has taken over the work that the spec described.
The operators in the building rarely notice the moment the agent started running their workflow. They notice only that the work got easier.
Flow is where work happens.
Each operator gets a cockpit. The cockpit is a single page that shows them the current task, the cases they're responsible for, and a chat with the agent.
They do not learn a new system. They do not log into anything new. The cockpit is open in their browser; they look at it the same way they look at email. When the agent has work for them, the agent says so. When they finish, they tell the agent.
The cockpit is called Flow. It is the only surface most operators ever see.
Instruct. Execute. Verify.
The agent tells the operator what to do, in plain language, with the specific values needed (the customer ID, the amount, the next step). The instruction is generated from the active workflow, not from a script.
The operator does the thing. They click the button, fill the form, make the call. The agent does not do this part. The human is still the actor.
Before the task is marked done, the agent independently checks that the result is real. It calls the API, reads the screen, queries the database. If the verification fails, the task stays open. The agent does not take the operator's word for it.
This loop is the difference between an automation and an agent.
From first interview to live operations.
- Week 1 Listening session. One vertical, one operator. Transcript only.
- Weeks 2–3 Decode. Vertical Spec drafted, reviewed, corrected.
- Weeks 4–8 Wizard runs with the operators. The spec gets corrected from the inside. Tools and integrations come online one by one.
- Weeks 9–12 The agent is doing the work. The implementer becomes invisible. The vertical is live.
What you actually see.
- Tasks appearing in the cockpit, addressed to specific operators, with the right values pre-filled.
- Alerts when something needs attention now — a missed deadline, a rejected claim, a deviation from the expected.
- Dashboards showing volume, throughput, and bottlenecks per vertical, updated in real time.
- KPIs that the owner cares about — money in, time saved, percent automated, cases open and closed — visible on a single screen.
The system gets better while you use it.
Every conversation between an operator and the agent goes back into the Employee MCP. Every exception that gets resolved goes back into the Org MCP. Every pattern that recurs across organizations gets considered for promotion to the Vertical MCP.
The system you have in month six is not the system you had in month one. It is the same architecture, deepened by every interaction it has handled.