Status
No AgentBoundary certification records have been issued or published.
- Private verification: available with result-holder approval
- Expired or superseded records: shown only when publication is approved
AgentBoundary
Verify a scoped AgentBoundary result without turning it into a blanket safety claim.
A public or private verification path for certified agents, grounded in scenario scope, versions, dates, tool boundaries, limitations, and recertification triggers.
What you receive
Concrete outputs for a specific decision.
- Verification status
- Scenario scope
- Model version
- Prompt version
- Tool scope
- Test date
- Limitations
- Recertification triggers
Work product
Illustrative registry format
No AgentBoundary certifications have been issued or published. The cards below show the proposed record format only.
Illustrative record shape
Example only: a record would identify the agent, status, test date, scoped workflow, retrieval access, and tool permissions.
- Model: recorded by exact provider and version at test time
- Prompt: recorded by version or digest
- Tool scope: read tickets, draft response, no send/delete/execute actions
Recertification trigger
Retest required after model swap, prompt rewrite, memory behavior change, new tool permission, policy update, architecture change, or major retrieval-source change.
Structured intake
Verify a certification ID or private result
Use this form when a vendor has provided a verification ID, result date, or private sharing instruction. Do not include secrets, customer data, prompts, logs, or confidential files.
01
Registry fields
Status
Current, expired, superseded, private, or unavailable based on the result holder's approved publication settings.
Scope
The exact agent flow, prompt version, model version, tool scope, retrieval scope, and scenario set reviewed.
Limits
What the result does not cover, including future prompt changes, tool additions, model swaps, policy changes, and architecture updates.
02
Private verification
Some vendors may keep results private. TKOResearch can support customer diligence by confirming scoped details under an approved sharing path.
Limits
Scope and assumptions stay explicit.
- A verified result is scoped technical support, not a guarantee of safety across all future versions or deployments.
Related paths
Next step