Become a design partner

Foundation for Action. Built for autonomous systems.

Intelligence
is not
authority.

The independent enforcement layer
for the autonomous economy.

AI agents can initiate payments, change financial records and execute consequential actions. Access does not necessarily establish institutional authority. CAUVIA is developing independent infrastructure to check authority before execution, across platforms and organisational boundaries.

See the institutional use case
Independent Autonomous Action InfrastructureA new boundary for autonomous action
01 / THE INSTITUTIONAL PROBLEMAUTONOMOUS ACTION. INSTITUTIONAL CONSEQUENCES.

Access is not
authority to act.

AI agents are gaining the ability to initiate payments, change financial records, modify supplier details and execute consequential actions across enterprise systems.

Legitimate access to a system does not necessarily establish institutional authority to perform a particular action. CAUVIA is building independent infrastructure to verify that authority before execution, with verifiable evidence of the decision.

RISK / INDEPENDENCE / EVIDENCESee the commercial use case
SCROLL TO EXPLORE

A foundation for autonomous action.

I.

A new institutional risk.

An agent can have access while lacking authority for a consequential action.

II.

An independent point of control.

Authority should remain with the institution, across the platforms it chooses.

III.

A decision with evidence.

Authorised actions proceed. Insufficient authority leads to denial or review, with a record of the decision.

CONTINUE THROUGH THE STORY
WHAT CAUVIA IS — AND IS NOTA PRECISE CATEGORY
The core question

Is this autonomous actor authorised to cause this consequential action, here and now, under the authority of the institution it claims to represent?

CAUVIA is

Independent Autonomous Action Infrastructure.

Pre-execution authority control and evidence, intended to work across agents, enterprise applications, institutions and execution providers.

  1. Verify authority
  2. Control execution
  3. Produce evidence
CAUVIA is not
  • An AI agent platform
  • A payment rail
  • An identity provider
  • A generic AI governance dashboard
  • A full cybersecurity suite
  • A replacement for your system of record

Prevention depends on integration at a genuine execution point. A monitoring-only integration cannot promise prevention.

THE BOUNDARY / A SPATIAL STUDYSee the finance use case

SCROLL TO EXPLORE

Capability moves.
Authority holds.

The moment before an action becomes a consequence.

  1. 01
    An action is proposed.Identity and access are inputs.
  2. 02
    Institutional authority is verified.Authority for this specific action.
  3. 03
    The boundary decides.Permit, stop or require review.
SCROLL PROGRESS
01 — 03
WHY CAUVIAINDEPENDENT AUTHORITY ENFORCEMENT

Authority before
consequence.

CAUVIA’s intended role is independent of the agent or application proposing the action. Institutions retain authority while existing systems carry out authorised work.

VERIFY AUTHORITY / CONTROL EXECUTION / PRODUCE EVIDENCEExplore the finance use case
SCROLL TO EXPLORE

A clear public promise.

01

Verify Authority

Establish whether the institution authorises the proposed action.

INSTITUTIONAL AUTHORITY
02

Control Execution

Allow an authorised action to proceed; deny or escalate where authority is insufficient.

CONTROL BEFORE CONSEQUENCE
03

Produce Evidence

Generate a verifiable record of the authority decision.

EVIDENCE OF THE OUTCOME
CONTINUE THROUGH THE STORY
02 / A COMMERCIAL USE CASESUPPLIER BANK-DETAIL CHANGES

VALID ACCESS. BUT CURRENT AUTHORITY?

The agent can
change the account.
Should it?

An autonomous finance agent attempts to modify a supplier’s bank account. It has valid credentials and access permissions.

The institutional question is whether it has current authority to make that specific change. CAUVIA’s intended role is to establish authority before execution and prevent the action where the required authority cannot be verified.

Explore a paid institutional pilot
ILLUSTRATIVE FINANCE WORKFLOW
Requested actionModify supplier bank details
Credentials & accessValid
Institutional authorityMust be established
ExecutionControlled before the change

Design-partner use case. Validation against live institutional authority records is outstanding.

03 / INTEROPERABILITYACROSS PLATFORMS AND ORGANISATIONS

Choose your platforms.
Retain your authority.

CAUVIA is being designed as platform-neutral infrastructure across AI agents, enterprise applications and organisational boundaries. CAUVIA is intended to remain independent of any single AI model, cloud, bank, ERP vendor, integrator, government or sector.

MicrosoftGoogleOracleSAPSalesforceXero

Designed to integrate with environments such as Microsoft, Google, Oracle, SAP, Salesforce and Xero, subject to technical and commercial validation. Naming an ecosystem is not a claim of partnership or working integration.

04 / THE INTERACTIVE DEMONSTRATIONOUTCOMES, NOT IMPLEMENTATION

Same access.
Different authority.

An agent requests a supplier bank-detail change. Choose an illustrative authority condition to see what should happen.

Fictional simulation. No institutional record is connected, no bank details are changed and no real evidence is signed here.

AUTONOMOUS FINANCE AGENT

Modify a supplier’s bank details

Current accountEnding 1234
Proposed accountEnding 5678
Credentials
Valid
System access
Permitted
Institutional authority
Present

Fictional supplier · No bank connection

CAUVIA / AUTHORITY BEFORE EXECUTION
  1. 01Verify AuthorityInstitutional authority is present
  2. 02Control ExecutionThe authorised change may proceed
  3. 03Produce EvidenceA decision record is part of the intended outcome
ALLOW

The institution authorises the change in this fictional example.

Illustration only. No live action.

Illustrative decision summary
Requested action
Supplier bank-detail change
Outcome
ALLOW
Action status
May proceed in the illustration

This is a presentation of the outcome, not a CAUVIA evidence format. The real system’s intended outcome includes verifiable evidence of the authority decision. This website generates no signed record.

THE EVIDENCE / AN EXPLODED VIEWSkip to demonstrated capabilities

CONNECTED TO THE DECISION

A decision.
Its context.
A record.

CAUVIA’s intended outcome: an authorised action, controlled execution and verifiable evidence of the decision.

  1. 01
    Verify authority.Establish whether the action is authorised.
  2. 02
    Control execution.Allow, deny or escalate the action.
  3. 03
    Produce evidence.Preserve a verifiable decision record.
SCROLL TO ASSEMBLE
01 — 03
05 / TECHNICAL VALIDATIONCREDIBILITY WITH CLEAR BOUNDARIES

Technical progress.
Institutional proof next.

We distinguish completed technical testing, external sandbox work and the outstanding requirement to validate against live institutional authority records.

TECHNICAL TESTING / SANDBOX / LIVE VALIDATIONExplore the open infrastructure model
SCROLL TO EXPLORE

What is demonstrated. What comes next.

Completed technical testing

Authority decisions and evidence

Controlled-environment testing has demonstrated authority decisions, execution controls and verifiable decision evidence. This is technical validation, not a live institutional deployment.

11 / 11end-to-end scenarios passing
780automated tests passing

Internal results reported by CAUVIA’s engineering team, 8 October 2026. Not an independent audit.

External sandbox work

BlinkPay payment demonstration

Payment work has been demonstrated in the BlinkPay sandbox using a test bank and test money. This does not establish production deployment, partnership or validation of supplier bank-detail changes.

Outstanding institutional validation

Three proofs ahead

  1. A real institutional authority record with a production funds-flow integration.
  2. A paid finance-system pilot controlling supplier bank-detail changes.
  3. Cross-organisational workflows.

Real institutional reliance, operational assurance and independent validation remain to be established.

CONTINUE THROUGH THE STORY

CAUVIA is in development. We do not claim production maturity, regulatory approval, recognised industry-standard status or independent institutional verification.

06 / THE OPEN INFRASTRUCTURE MODELADOPTION AND A SUSTAINABLE ECOSYSTEM

Open foundation.
Institutional value.

CAUVIA Core is intended to be free and open source, supporting adoption by enterprises, SMEs, AI platforms and technology providers.

The intended commercial ecosystem includes Sector Control Profiles, institutional services and integrations, conformance testing and certification, and deployment through enterprise IT teams and systems integrators.

INTENDED DIRECTION · LICENSING AND DISCLOSURE BOUNDARIES TO BE DEFINED

An ecosystem built
around institutional outcomes.

01 / SECTOR CONTROL PROFILES

Sector-specific assurance.

Intended to address institutional outcomes such as authorised financial actions, controlled supplier changes and accountable sector workflows.

02 / COMMERCIAL SERVICES

Integration and institutional support.

Services intended to connect authority controls to institutional workflows and enterprise environments.

03 / CONFORMANCE

Testing and certification.

A proposed commercial and governance pathway that requires defined criteria, independent validation and appropriate oversight.

04 / DEPLOYMENT ECOSYSTEM

Enterprise teams and integrators.

Implementation through institutional IT teams and systems integrators, supported by an interoperable foundation.

An open specification is not a recognised industry standard. That status would require adoption, independent validation and appropriate governance. Core release terms and the boundaries between open, proprietary and confidential material remain to be defined.

ABOUT CAUVIATHE COMPANY BEHIND THE BOUNDARY

Built in New Zealand.
Designed for a connected world.

CAUVIA Limited is building independent infrastructure so that autonomous capability can increase productivity without transferring legitimate authority away from the institutions accountable for it.

Company
CAUVIA Limited
Founder & CEO
Graeme Bennett
Stage
In development. Technical testing completed; live institutional validation is next.
Seeking now
An Institutional Design Partner for a paid pilot.
Principle
Intelligence is not authority.
BEFORE WE TALKCLEAR EXPECTATIONS

Independent by design.
Precise about proof.

Is CAUVIA another AI agent platform?

No. CAUVIA’s intended role is independent institutional authority enforcement across agents and enterprise applications. It is not being positioned as a proprietary governance dashboard or vendor-specific security product.

Are the named platforms integrated today?

Microsoft, Google, Oracle, SAP, Salesforce and Xero are illustrative technology environments. Their inclusion does not imply integrations, partnerships or endorsements.

Does CAUVIA prevent every unauthorised action?

No system can promise that. CAUVIA addresses the authority boundary for consequential actions. Prevention depends on integration at a genuine execution point; a monitoring-only integration can observe but cannot promise prevention.

Is CAUVIA Core already available as open source?

Free and open-source Core is the intended direction. Release scope, ownership, contribution arrangements, licensing and disclosure boundaries still need to be defined. No current release or licence is announced here.

What is the immediate commercial priority?

A paid institutional pilot focused on one consequential workflow, particularly supplier bank-detail modification or a financial transaction. These are distinct workflows and require their own integration and validation.

07 / A PAID INSTITUTIONAL PILOTCOMMERCIAL VALIDATION STARTS WITH ONE WORKFLOW

FOR CEOS, COOS, CIOS, CFOS AND INSTITUTIONAL RISK LEADERS

Become a CAUVIA
Institutional Design Partner.

Work with CAUVIA to identify one consequential workflow, connect an authoritative institutional approval record and demonstrate that unauthorised execution is prevented while authorised actions produce verifiable evidence.

Our immediate priority is a paid institutional pilot, particularly supplier bank-detail modifications or consequential financial transactions.

Discuss a paid pilot
INSTITUTIONAL & STRATEGIC ENQUIRIES

Graeme Bennett

Founder & CEO · CAUVIA Limited

graeme@cauvia.nz
  1. 01Select one consequential workflow.For example, supplier bank-detail changes or payment instructions.
  2. 02Connect one real authoritative approval source.The institution’s own record of who may authorise what.
  3. 03Agree acceptance criteria.Testable allow, deny and escalate outcomes.
  4. 04Independently review the evidence.Your team assesses the outcomes against the agreed criteria.