Skip to content
PAVREN / Stories / CAINCO: three functions, one responsibility when designing AI agents

CASE STUDY · INSTITUTIONAL DESIGN

CAINCO: three functions, one responsibility when designing AI agents

From Administration to Procurement and Accounting: designing three governed agents around institutional processes without transferring human approval powers to AI.

Author: Luis Adolfo Soto Dorado10 November 2026Read · 4–6 min
Published scope: Documented status: design and technical handoff completed. No claim of live Enforce deployment or quantified impact.

Where the work began

A purchase does not end when someone produces a document. It involves requests, owners, exceptions, approvals and records. Without those relationships, AI can generate useful responses while remaining unable to establish who may authorize the next action.

CAINCO’s design work covered three connected functions: Administration, Procurement and Accounting/Payments. The goal was to let agents assist with preparation and review without treating system access as a source of authority.

What the team designed

The engagement examined workflows, normal and exceptional paths, requirements, agent cards, and an information and integration architecture. It separated assistance tasks from decisions reserved for competent people.

The design considered access boundaries, handoffs across functions, supervision and traceability. Demonstrations used synthetic data; they must not be interpreted as real financial transactions.

What was delivered—and what was not

The outcome was a design and technical handoff package intended to support implementation of governed agents in identified institutional processes. The design phase was completed and delivered.

This is not evidence of production agents, autonomous payment execution or deployed Enforce controls. It is an institutional architecture and design case, not a claim of measured operational impact.

What the case teaches

Three agents are not three grants of authority. Authority cannot be inferred from a user role, a technical credential or model capability; it has to be represented at each transition in the process.

The experience illustrates why useful governance starts with the task, the person responsible and the expected outcome—not with a list of abstract controls.

Next step

Read the complete official corpus or explore an authorization scenario without taking real actions.

Explore Govern 3.0 → · Developers →

Frequently asked questions

Which agents were designed?

Three agents for Administration, Procurement and Accounting/Payments.

Does the case demonstrate Enforce in production?

No. This case does not claim an operational Enforce installation or measured production results.

Luis Adolfo Soto Dorado

Creator and intellectual architect of PAVREN. DAcorp S.R.L. supports publication.

Editorial note: these accounts distinguish design, operations and proposed future work. No undocumented metrics, testimonials or endorsements are claimed.