Governed workflows
Explore source-backed examples and integration references. These are evaluation starting points; customer deployments and business results are not claimed.
At the point of execution
Require a valid decision receipt before an integrated tool call can run.
Beta · release candidateAt the integrated executor, deny or escalate outcomes stop the call. The runtime is not a sandbox for every action an agent could take.
Explore the execution kernelExplore a workflow
Keep the request, its permitted scope, and the review boundary together. Each example has its own operating conditions.
Local workflow example · mock tools
Explore policy and receipt checks around drafting, matter access, reviewed communication, and submission.
The available example uses mock tools, temporary storage, and unsigned development receipts. It does not connect to a court, send a client message, or demonstrate a released legal assistant.
Cloud infrastructure
Check Google Cloud Terraform plan JSON and retain control evidence.
Check a Google Cloud Terraform plan before apply. Your CI pipeline enforces the result.
Healthcare prototype
Inspect model-assisted assessment, healthcare policy rules, and a reviewable decision record.
Prototype evaluation with synthetic examples. This is not a clinically validated decision system, a signed execution gate, or a compliance certification.
Integration references
Inspect which hooks are implemented, which evidence is retained, and which responsibilities stay with the integrating system.
Source middleware
Inspect pre-tool checks, output screening, final-response holds, and optional evidence capture.
Integration reference. The existing evidence-panel HTML uses fixture traces; its replay and export buttons do not call a backend.
Governance evaluation
Evaluate authority and policy, explain the result, and retain evidence for reviewing a governed action.
Engineering self-assessment reference
Review decision and audit fields alongside gaps and operator responsibilities.
A source-authored evidence mapping. It is not a conformity assessment, legal conclusion, certification, or deployment approval.
Credential-governance concept
Explore the intended boundary between a proposed action, a scoped credential decision, and an external service.
Design the controls
Define authority and review before the workflow reaches an external system.
Operating patterns
Choose operating modes and controls appropriate to an agent task.
These patterns help define a workflow. They do not grant permission, authenticate a reviewer, or create an executable decision receipt.
Failure modes
A practical catalogue of agent-workflow risks, warning signs, and integration controls.
Evidence and assurance
Review product claims, security boundaries, and deployment-specific data questions.
Keep the evidence in view
Components have different contracts and levels of maturity. Review the setup, source evidence, and operating conditions for the path you choose.
Review Claims & Evidence