01 / THE REQUIREMENT
What the system must handle
A product agent must understand the user and current product state, then act without gaining broad or ambiguous access.
02 / THE ARCHITECTURE
How the pieces connect
Connect the agent to typed product tools, scoped identity, current state, relevant knowledge, and an approval step for consequential actions.
03 / OPERATING MODEL
How the system behaves
The agent can answer, create, update, or coordinate within defined boundaries. Logs and evaluations make its behaviour reviewable.