P1 / POWERS
Bounded powers
Finite, enumerated capabilities. A newly exposed tool gains no power to act merely by becoming reachable.
The Financial Harness.
Authority before action.
The Harness is the control architecture beneath the Agentic Finance Department. It binds agent identity to enterprise mandate, evaluates policy and delegated authority, routes exceptions to the right human, and preserves the evidence behind every consequential transition.
THE CONTROL PATH
Authority is not a prompt.
An intelligent system may form intent. That does not make the intent authorised. The Harness separates reasoning from enterprise authority and makes the transition between them explicit.
Financial Harness / governed transition
INTENTAgent proposes consequential work.
GARD IDIdentity + mandate resolved.
POLICYRules + authority evaluated.
GARD BOARDVerdict / exception / receipt.
GARD RAILOnly cleared work routes onward.
PRINCIPLES
Six things the Harness has to make true.
P2 / IDENTITY
Verified identity
The environment knows who is acting. Invalid identity, endpoint or scope fails closed.
P3 / TRANSITIONS
Gated transitions
Intent cannot become consequential action without a policy decision and, where required, human sign-off.
P4 / INSPECTION
Inspectable decisions
Actor, mandate, policy result and decision trace stay correlated.
P5 / LEARNING
Supervised change
Outcomes may inform proposals. Feedback does not silently rewrite enterprise policy.
★ / EVIDENCE
Proven, not asserted
Controls should be testable and consequential decisions reconstructable.
GARD ID
Identity carries authority context.
Every GARD that enters finance needs a verifiable identity and an explicit mandate: what it is, where it runs, what job it holds, what it may do and who owns that delegation.
ID.1 / REGISTRY
Know Your Agent
Agent, runtime, role and decision history.
ID.2 / MANDATE
Delegation encoded
Corporate delegation expressed as machine-enforceable scope.
ID.3 / LIFECYCLE
Narrow. Revoke. Cascade.
Limits can be changed without relying on a prompt to remember the change.
GARD BOARD
The place where mandates, exceptions and evidence meet.
Routine work inside mandate can continue. Work outside delegation routes to the named human with provenance and context. The verdict becomes part of the decision record as it happens.
BD.1
Exception queue
Named approver, reason, provenance and changed context — not a raw alert.
BD.2
Decision trail
Which GARD. Which mandate. Which policy. Which human. Which outcome.
BD.3
Department control
Mandate hierarchy and intercept visibility across the agentic department.
GARD RAIL
Route only what has cleared governance.
GARD Rail is the post-verdict boundary. It does not need to become the bank, ERP or payment provider. It keeps governance structurally distinct from execution.
ERP / AGENTInstruction formed
HARNESSGovernance verdict
CLEARAuthority receipt bound
RAILAuthorised route
EVIDENCEOutcome correlated
AUTHORITY STACK
The hard backend is a chain of authority, not a chain of prompts.
Each layer answers a different question. Consequential action is released only when the chain resolves.
GARD FINANCIAL HARNESS / CONTROL PATHGOVERNED PATH
Intelligence can be probabilistic. Financial authority cannot.
HARNESS PRINCIPLE — EVERY AGENT. EVERY MANDATE. GOVERNED BEFORE CONSEQUENCE.
WHAT STAYS PRIVATE
Show the control. Protect the implementation.
The public architecture explains the control model. Detailed policy-engine implementation, rule schemas, orchestration, attestation internals, conformance harnesses and proprietary decision logic belong in qualified architecture reviews and NDA material.
INTELLIGENCE INTERPRETS. THE HARNESS ENFORCES. · ★GARD is governing intelligence. The Harness is enforceable governance.