Fear 1
It emails a client something wrong.
The included assistant returns a review packet and has no client-dispatch connector. Its approval endpoint records a user action; that endpoint does not send the packet.
For law firms
Use AI in your practice without losing control of it.
The included assistant prepares review packets for intake, document summaries, billing, and other cataloged outcomes. It has no client, calendar, or trust-ledger dispatch connector.
A guarded run records routing, policy, cap, and pending-review metadata. A separate approval action records an authenticated user hash and approval status. Signatures reveal later changes to those fields; they do not prove that professional duties were met.
What the included path does and does not do.
The supplied assistant path prepares review material and signed metadata. External business-system connectors require separate integration and enforcement.
Fear 2
It misses a deadline.
Deadline extraction is a cataloged outcome template, not an automatic document-ingestion service. You must connect the source and model provider, review the output, and implement any calendar-write gate.
Fear 3
Client confidences leak.
AgentGuard functions receive metadata only. When you select document text for a model call, the browser sends that content directly to your chosen provider under that provider's terms.
Signed metadata, bounded claim
The receipt records the process you configured.
The run receipt records a user hash, model route, cap, capability, and pending-review status. The separate approval receipt records an authenticated account's approval assertion. Anyone with the public key can check whether those signed fields changed. The records do not establish the reviewer's real-world identity, the adequacy of review, or legal compliance.
These fields may help your own counsel evaluate the process against applicable duties:
Model routeWhich configured model and policy metadata was signed.
Content boundaryAgentGuard receives metadata; the chosen provider may receive content.
Approval assertionUser hash, source receipt, status, and signed time.
Dispatch boundaryNo client-send connector is included in this path.
Cost metadataConfigured maximum and projected cost values.
What the supplied template configures.
The operating pack describes capability levels. They become enforcement only where your integration calls the guard before an external action.
| Capability | What it allows | What it cannot do |
|---|---|---|
| READ_ONLY | Intended for classification, summaries, extraction, reconciliation, and packet preparation. | No client-send, calendar-write, or trust-ledger connector is included. |
| TRANSACT | The template describes dispatch-ready drafts that still require approval. | It does not itself dispatch, move funds, or change policy. |
| ADMIN | Named in the operating-pack configuration for retention and capability administration. | No trust-account administration integration ships in the supplied tree. |
The firm remains responsible for the workflow. AgentGuard signs configured metadata and can enforce a policy where it is integrated. A signature proves integrity of the signed fields, not who performed an action, legal supervision, compliance, or an outcome. Review the operating pack and every production connector with your own counsel.
Let your firm automate the work it has been afraid to.
Pick law to load an example team and run the metadata-only signed demo. Production data sources, action connectors, and legal review remain your responsibility.