Govern
How to Add Governance to Custom AI Agents
Built your own agent framework? Cordum governs it. CAP v2 gives any agent policy checks, approvals, and audit trails.
The problem with ungoverned Custom Agents agents
- Custom agents mean custom governance or none at all.
- Policy rules in if-statements. Updates need deploy cycles.
- Audit trails are afterthoughts.
- Governance divergence grows with the fleet.
How Cordum governs Custom Agents
1
Integrate via CAP v2
SDKs in Go, Python, Node.js, C++. Standard wire format for jobs, results, approvals.
// Go SDK
job := cap.JobRequest{
Type: "custom.agent.task",
Payload: taskPayload,
Metadata: map[string]string{"user": userId},
}
result, err := cordumClient.Submit(ctx, job)2
Define policies
Generic engine matches any job type and metadata.
rules:
- name: web-scrape-constraints
match:
capabilities_contains: web-scrape
action: ALLOW_WITH_CONSTRAINTS
constraints:
domains: ["*.gov", "*.edu"]
- name: deploy-approval
match:
agent: deploy-agent
action: REQUIRE_APPROVAL3
Handle approvals
CAP SDK helpers for wait, timeout, denial.
4
Automatic audit
Every job gets a run timeline. No custom logging.
Custom Agents native vs Cordum governance
| Area | Custom Agents Native | With Cordum |
|---|---|---|
| Policy | If-statements | Declarative, hot-reloaded |
| Approvals | Custom per agent | Standard with routing |
| Audit | Custom logging | Automatic timeline |
| Consistency | Self-governed | One policy bundle |
| SDKs | N/A | Go, Python, Node, C++ |
FAQ
No framework at all?
Primary use case. CAP v2 has no framework dependency.
Migrate from homegrown?
Start with high-risk agents. Parallel run during migration.
Which SDK?
Match your language. Go is most mature.
Related guides
Ready to govern your Custom Agents agents?
Start with the open-source Cordum platform. Add policies, approvals, and audit trails in minutes.