NEWSROOM

AI systems are beginning to act: approving transactions, adjusting limits, initiating payments, executing trades, negotiating with other systems on behalf of people and companies. When an AI system acts, its output is no longer information. It is an event in the world, with financial, legal and reputational consequences.

A blockchain can prove that a transaction happened and that it was signed by a valid key. It can't prove that the transaction should have happened. That is a decision, and decisions need their own infrastructure.

For most institutions, that proposal is wrong, and not only because migration is expensive and risky. It is wrong because it misidentifies the problem. In most institutions, the main obstacle to better decisions is not the quality of their models. It is the absence of infrastructure between those models and the decisions they inform.

Agents are starting to act. They pay suppliers, schedule transfers, move balances between accounts, initiate payments through Pix and Open Finance...

When a company fails, the warning signs usually look obvious in hindsight. Margins narrowed. Working capital tightened. Payments to suppliers slowed. Debt grew faster than revenue. Looking back, the path to distress is clear.

Zayon announced today that STEPA (Structural Trajectory Embedding Predictive Architecture), a research line developed by the company, has been selected among the 100 National Innovation Cases 2026 at the MIT-ANPEI Summit, out of 439 submissions.

It happens quietly, every day, in financial institutions. A field arrives empty and the system fills it with a default. A bureau query times out and the pipeline proceeds without it. A financial statement is two years old, but nothing checks its date. The model receives something that looks like a complete input, produces a confident score, and a decision is made.

A new architecture for AI decision systems makes decisions explainable, traceable, reviewable and certifiable, with trust built in at the level of each decision.

Deborah Nogueira, Founder and CEO of Zayon, has published a new paper on SSRN: From Model Governance to Decision Governance: A Behavior-Centered Architecture for AI-Assisted Decisions in Regulated Financial Services. The paper starts from a question that is becoming increasingly pressing for financial institutions using AI: in regulated environments, is governing the model enough to govern the decision?

The first wave of thinking about AI agents assumed a simple structure: a human delegates a task to an agent, and the agent acts. One principal, one agent, one line of authority.

Ask a financial institution how its credit model performs and you will get a precise answer: an AUC, a Gini coefficient, a calibration curve. Ask what that model has contributed to the institution's results and the answer becomes vague.

That gap is the reason so many institutions struggle to explain, audit and measure their AI decisions. The fix is conceptually simple and architecturally demanding: every consequential decision needs a single record, under a single identifier, that connects everything the decision depended on and everything that followed from it. We call it the decision record.

Every AI system produces logs. Almost none produces proof.

Every AI decision system in a financial institution has a human-in-the-loop somewhere. An analyst reviews borderline credit requests. An account manager decides whether to follow a recommendation. A credit committee approves exceptions. A supervisor reverses a decision after a complaint.

Yet in many institutions, that policy doesn't fully belong to them. Part of it is configured inside a vendor's system by the vendor's consultants. Part is hard-coded in software no one in the credit team can read. Part lives in spreadsheets and documents that don't match what the system actually does.

For financial institutions using AI in credit, this right raises a practical question that goes beyond compliance checklists: when a customer asks why, what exactly does the institution need to be able to explain?

The usual approach to explainable AI in financial services follows a predictable sequence. A model is built for performance. It is deployed. Then, when compliance, customers or regulators ask how it works, an explainability tool is attached to it: feature importances, SHAP values, counterfactual examples.

Every financial institution that automates decisions represents them in its own way. One stores a credit decision as a row in a database. Another as a JSON document in a proprietary format. A third as a combination of log entries across four systems. Policies are written in documents, rules engines, spreadsheets and code. Evidence is referenced by internal identifiers that mean nothing outside the institution.

A cooperative system doesn't need to choose between central control and local autonomy. It needs to make the boundary between them explicit.

In most credit operations, the central object is a number. A score of 0.73. A probability of default of 2.4%. A risk rating of B+. Systems compute it, dashboards display it, analysts discuss it. But a number is not a decision. At some point, someone or something has to turn it into an action: approve or not, how much, under what terms, now or later. In most institutions, that translation is the least structured part of the process. It lives in cutoffs, informal ranges and an