Example workflow you can build
Find the missing evidence behind a production change.
An agent gathers the records and flags gaps. An authorized admin exports oz0 activity, and a reviewer checks what the evidence supports.
01 The problem
Your system
"Who approved firewall change CHG-1042 before it went live?"
API requeststarts an oz0 job
02 The agent investigates
- Tool rules & approvals
- Model budgets
- Job history
Your task plugin
Runs on your oz0 node
Connector tool · Change system
Querying: CHG-1042 in the change system.
Result: No approval record found in scope.
Tools · Pipeline and oz0 history
Match the change ID and timestamps.
Your systems
- CHG-1042
- Pipeline run
- oz0 history
Result: Deployment recorded; approval unproven.
Agent output · Evidence report
Links the deployment evidence and explains that approval is still unproven.
03 People decide
Your admin · oz0 export
An authorized admin decides what oz0 records may be exported.
04 The outcome
Export permitted
Your reviewer
Verify the signed oz0 bundle; cross-check external records.
Approval gap remains in the report.
Export refused
Restrict the scope or obtain permission.
Keep the request open.
Both possible outcomes are shown. No real actions run.
How these parts fit
- Plugin
- Installable package of agents, tools or instructions.
- Agent
- Uses your model to choose tool calls.
- Connector
- Plugin providing tools for an outside system.
- Tool
- Exposes actions the agent can call.
- API request
- Your app asks oz0 to start work.
Use existing plugins or build these integrations. Plugin docs
A valid signature proves bundle integrity, not that the firewall change was authorized.
What you connect
Provide read access to external records, recorded oz0 activity, export admin access and a trusted verification key.
Build an agentA starting point
Evidence export and offline verification are built in. An agent that gathers external records is a custom workflow.
Docs