“Here is the refund I recommend.”
OutputText
Agent action authorization & accountability
AI agents
can act.
Keep control.
Route sensitive actions through one boundary that applies policy, brokers scoped credentials, meters consumption, and seals a verifiable record.
Authorize before. Bound during. Prove after.
ACTION DOSSIER / 7F-204
ROUTED
REQUESTING AGENT
refund-assistant
07:42:16Z
PROPOSED ACTION
Issue a $240 refund
customer / acme-co · payment / rf_8421
IdentityBOUND
PolicyALLOW
ApprovalRECORDED
BudgetWITHIN LIMIT
AUTHORITY / FEIROS
RECEIPT PENDING
Illustrative action record · shaped by the FeirOS control model
Scroll to trace the governed path
Coverage begins at the routed boundary
01 / The thresholdFrom assistance to authority
THE PRODUCTION MOMENT
The risk changes when software starts acting.
Assistants produce an answer. Operators change a record, issue a payment, call production, or message a customer.
At that threshold, model guardrails are no longer enough. Authority needs a boundary.
“Refund issued. Customer notified.”
OutputConsequence
One decisive question
May this agent take this action now?
System authority
A tool call can write to the systems your business depends on.
Credential exposure
Standing secrets turn one compromised run into a wider blast radius.
Evidence gap
A mutable activity log cannot, by itself, prove who authorized what.
02 / The boundaryOne action · four planes
FEIROS / SYSTEM ARCHITECTURE
One governed path.
Four independent planes.
Each plane has one job and an explicit limit. Together they form the boundary between an agent’s intent and a sensitive system.
ACTION / 7F-204
DECIDING
refund-assistant
refund.create / $240
tenant_eu · acme-co · run_8421
-
01
GOVDERDECIDESPOLICY RESOLVED
-
02
VULTRINOENFORCESAUTHORITY SCOPED
-
03
AVERINPROVESRECEIPT SEALED
-
04
LERIAMETERSUSAGE RECORDED
DECISION
ALLOW / SCOPED
7e91…c204
Resolve policy before execution.
Govder turns organizational policy into the effective configuration for a decision. It answers who may do what, under which conditions.
HOLDS NO CREDENTIALSNEVER ON /EXECUTE
Use authority without exposing the secret.
Vultrino is the default-deny credential proxy on the action path. It injects the credential only after the request clears its enforced boundary.
DEFAULT DENYIN-PATH BOUNDARY
Leave evidence that travels.
Averin seals signed, hash-chained records into a tamper-evident history that can be verified offline—with the trust level declared, not hidden.
OFFLINE VERIFIABLETHREE TRUST LEVELS
Make consumption accountable.
Leria is the durable book of record for usage and budget signals. It stays off the synchronous path, containing spend with an honest bounded-overshoot model.
DURABLE LEDGERBOUNDED, NOT ZERO, OVERSHOOT
03 / The operating ruleBefore · during · after
A COMPLETE ACTION RECORD
Authorize before.
Bound during.
Prove after.
01BEFORE
Ask the whole question.
Bind identity, delegated authority, policy version, approval, context, and budget state to one decision.
02DURING
Narrow the authority.
Broker only the credential and scope the approved action requires. The agent does not need the standing secret.
03AFTER
Carry the proof forward.
Preserve the decision, action, and result in a portable record that does not depend on a mutable dashboard.
04 / Control roomThe human surface
FEIROS / OPERATOR EXPERIENCE
Know what is safe.
See what needs you.
FeirOS turns the four-plane system into six plain controls: agents, permissions, budgets, approvals, stop, and proof.
ILLUSTRATIVE OPERATOR SURFACEALPHA / SAMPLE STATE
2
NOW / NEEDS YOU
Two approvals are waiting.
Everything else is running within its current limits.
Open approvalsControl loopRunning
01 / FLEETOpen fleet
Consumption this period
$1,166of $5,000
Bounded controls · 23% recorded
Governed activity
- Refund approved within scope3 min ago
- Deploy request held for review18 min ago
- Evidence bundle verified42 min ago
PROOF AVAILABLECaptured activity has a verifiable record.Open proof →
05 / How to beginOne protected workflow
LAND SMALL / EXPAND BY EVIDENCE
Start with one sensitive workflow.
Not an enterprise-wide governance program: bring the moment where a named agent is about to receive write access. Make that path governable first.
- 01
Route one action
Put one protected tool or API behind the execution boundary.
- 02
Define authority
Set the identity, action, context, approvals, and budget response.
- 03
Exercise outcomes
Test an allow, a deny, an approval, a stop, and a budget-triggered response.
- 04
Verify the record
Export the sealed evidence and check it independently.
- 05
Expand the boundary
Add the next workflow only after the first path earns trust.
Good first boundaries
- Financial operations
- Customer records
- Infrastructure
- Access changes
- Outbound communication
06 / EvidenceTruth before theatre
ALPHA / BUILT TO BE INSPECTED
A boundary you can point to.
Limits you can name.
Accountability begins with honest coverage. FeirOS governs actions routed through its boundary—never actions it cannot see.
FOUR-PLANE INTEGRATION HARNESSREAL PROCESSES / NO MOCKS
Core paths exercised together.
- 01Core loopREQUEST → RECORD
- 02Budget resetMETER → DECIDE
- 03Kill triadREVOKE → DENY
- 04Promotion gateOBSERVE → ENFORCE
Evidence of integration—not a claim of customer scale or production maturity.
Routed actions only.
Direct or uninstrumented actions remain outside the governed boundary.
Bounded overshoot.
The meter stays off the hot path; soft ceilings contain rather than promise a zero-lag cutoff.
Declared trust.
Evidence is tamper-evident and offline-verifiable at its stated trust level—not magically complete.
BRING ONE WRITE-ENABLED WORKFLOW
Give agents authority.
Keep control.
Put the next sensitive action behind a boundary that can authorize it, contain it, and leave a record.