An agent should be more than an anonymous tool call. Connect its identity to the team responsible for it and the work it is here to do.
AGENT IDENTITYRegistered
Custom-built agent
Release coordinator
Responsible team
Product engineering
Purpose
Prepare release summaries
Identity
release-coordinator
Distinct actorConnected to its work
One identity. A continuous thread of context.
Illustrative example
Bring the way you build
Identity belongs to the agent. It doesn’t have to belong to a framework.
Connect through supported integrations and configured Fabriq paths.
First-class actors
Manage the agent, not just its credentials.
Give every registered agent a place in your inventory. Keep its purpose, responsible team, and access in context as its role changes.
01
AGENT RECORDRegistered
Release coordinator
OwnerProduct engineering
Identityrelease-coordinator
01 / A distinct actor in your inventory
Register the actor.
Make the agent recognizable before you connect its work.
02
RECORDED ACTIVITYActive
Release coordinator
github.repo.readAllowed
slack.message.sendAllowed
02 / Tool calls linked to this identity
Follow its work.
Use the agent identity to connect configured access and recorded activity.
03
ACCESS STATUSDisabled
Release coordinator
New calls through FabriqBlocked
Agent statusInactive
03 / Stop access when the work ends
Retire its access.
Disable an agent when its assignment ends or its access needs review.
ACTIVITY REVIEWIllustrative example
AGENT IDENTITY
Release coordinator
Product engineering
Release summaryRead release notes
Release summaryPost team update
Unfamiliar activityReview this agent’s latest call
Review
One signal. The context to investigate.
Who
Release coordinator
Owner
Product engineering
Next step
Inspect the tool-call record
Put a name to the signal
When activity stands out, know where to look.
Bring suspicious activity back to a known actor. Review the available records alongside the agent’s identity and ownership, then decide whether its access should change.