
- DOCUMENTSProcedures, reports and minutes go into Knowledge, or the description is pasted into the conversation.
- MAPNumbered steps with who does it, what goes in, what comes out and the system used.source cited
- BOTTLENECKSWaiting, rework or manual handoffs, each with the passage that shows it.passage cited
- PROPOSALSImprovement steps tied to each bottleneck, with no made-up time or gains.nothing made up
- VALIDATIONThe people who run the process confirm the map and decide what changes.human decision
How it works
During setup, procedures, reports and meeting minutes go into Knowledge; the person can also paste the process description into the conversation. The analyst builds the current map in numbered steps (who does it, what goes in, what comes out and the system used, when the document says), points out bottlenecks such as waiting, rework, repeated approvals or manual handoffs between systems, each with the passage that shows it, and proposes improvement steps tied to each bottleneck, with who needs to validate them. What the document does not say is marked "not stated"; without a passage, it does not become a bottleneck, it becomes a question for the team. Studio evaluates every agent version before publishing.



