LOCAL WORKFLOW EXAMPLE · MOCK TOOLS
Make the legal
workflow boundary explicit.
Explore a local example that places policy and receipt checks around drafting, matter access, reviewed communication, and submission steps.
- 01
Propose a scoped action
Identify the matter, operation, and intended destination.
- 02
Evaluate the boundary
Check policy and receipt conditions for the mock tool.
- 03
Inspect the outcome
Review the recorded decision and whether the mock action ran.
Keep consequential steps reviewable
The example includes court-submission sign-off and reviewed client-communication scenarios. These illustrate where a workflow should stop for a separate decision.
It does not connect to a court, send a client message, or demonstrate a released legal assistant.
Keep matter access explicit
Other scenarios cover matter-scoped document access and discovery-export destinations. The examples help an integrator inspect how request scope reaches a governed mock executor.
They do not establish legal privilege, citation accuracy, conflict screening, or a production document-management integration.
Run the local example
# The governed legal drafting example is not published as a package.
# Request evaluation access at evaluation@acgs.ai.Copy the example or select it manually.
The example uses development trust settings and mock side effects.