AI Patterns · Work

On-ramps

An organization has a right way to handle many requests, but people and agents find it only if they already know it exists.

How it works

Each process lists, in its own record, the requests that start it. One index of processes is built from those lists, never by hand, and every agent checks it before acting, says which process it is following, and follows it in order. A request that matches nothing, and keeps coming back, is proposed as a new process.

Where we use it

GSSF's agents check its processes this way, since October 2026 (Building Agentic Organizations, chapters 8 and 17).

Status: Early · Origin: Builds on standard operating procedures, on process modeling's start events, and on Nonaka and Takeuchi's externalization, turning what people know how to do into something written (credited in Building Agentic Organizations, chapters 8 and 17). Keeping the trigger in each process's own record, building the index from it for agents, and listing what matches nothing is how we apply them

Sources

Mike Lee, Building Agentic Organizations: How to Build an Organization of People and Agents (GSSF Press, 2026), chapter 8, “From Strategy to Execution”, section 6
Mike Lee, Building Agentic Organizations: How to Build an Organization of People and Agents (GSSF Press, 2026), chapter 17, “How the Organization Improves Itself”, section 4
“Standard operating procedure,” Wikipedia
“Business Process Model and Notation,” Wikipedia
Ikujiro Nonaka and Hirotaka Takeuchi, The Knowledge-Creating Company: How Japanese Companies Create the Dynamics of Innovation (Oxford University Press, 1995)

See something wrong? Report an error.