01WORK
Attach the supporting documents.
Add a source in Grounding Studio, such as an SOP or operating policy, and attach it to the work system or to a particular task.
Back to homeGive the work
Give the work
a source of truth.
Declare which documents support the work, which sources each agent receives, and which source governs a fact.
Attach the right context to the right scope. Keep work-system documents, individual agent sources and the fact order distinct as the design moves into realization.
Support for the decisionDeclared sources
01
Work-system documentsProposal procedure · operating policy
02
Each agent’s sourcesEvidence agent → account record
Writing agent → approved content
03
Fact orderWhich source governs each fact?
Declared support → agent brief → realization
DesignSimulateRealize
The question that matters
When sources disagree, which one governs the decision?
More context does not settle that question. Grounding makes the intended support explicit: what applies to the work, what applies to each agent, and the order of truth for a fact.
From intent to implementation
02AGENT
Give each agent its own sources.
Set the source list for the agent staffed on a task. Two agents on the same task can hold different lists.
03TRUTH
Declare the fact order.
In Realization readiness, say which source is authoritative for which fact, including how to handle stale or contradictory information.
Relevant context. Explicit authority.
A recommendation’s precedent, a work system’s SOP and an agent’s source list have different jobs.
Domain grounding
Use platform and tenant material for domain-specific precedent. Different recommendation models consume different sources.
Work-system grounding
Attach SOPs, policies and specifications to the work or a task so the analysis rests on declared evidence.
Agent grounding
Prepare the sources that belong in each agent’s brief and permission scope. Realization carries source references with the package.
Before you get started.
Does every agent receive every attached document?
No. Work-system attachments, per-agent source lists and the fact order are distinct. Each agent’s list should reflect its part of the work.
Are source documents copied into the package?
Realization names sources and carries the relevant references. It does not copy the source content into the generated package.
Is an attached policy automatically enforced?
No. Declaring a source or writing an instruction does not itself enforce behavior. Destination permissions and actual control mechanisms determine what is blocked.
Design · Simulate · Realize
Ground the design. Prepare the agents to use it.
Bring the work, its sources and its authority together in realization.