Canonical: https://ai-nterprise.com/framework/
Language: en
Content status: published

Framework · The public foundation

# A claim becomes *a consequence.*

Follow one claim through four decisions, three control planes and three continuing loops.

On this page

[The moment of consequence](https://ai-nterprise.com/framework/#foundation) [Four decisions](https://ai-nterprise.com/framework/#four-decisions) [Three planes](https://ai-nterprise.com/framework/#three-planes) [Three loops](https://ai-nterprise.com/framework/#three-loops) [One case](https://ai-nterprise.com/framework/#one-case) [Ten principles](https://ai-nterprise.com/framework/#ten-principles) [Use and attribution](https://ai-nterprise.com/framework/#attribution)

00 / The moment of consequence

## Between an answer and an action.

**Diagram transcript:** The moment of consequence · A specific claim version reaches a gate. Knowledge and Authority converge on the same gate. One conditional route leads to an effect; another holds the proposed use for review. Assurance probes Knowledge, Authority and the gate and sends findings to the correction owner. No assurance connection enters the action route. · What is claimed · What is decided · What happens · v3 · Claim · a specific version · Four independent decisions: standing, persistence, visibility, action enablement · Gate · If enabled for this use · C2 · Effect within scope · Knowledge · Evidence · standing · Authority · Mandate · limits · Use held · Proposal for review · Assurance · independent checks · Owner · correction

**The moment of consequence.** Knowledge and authority meet at use time. A held use leaves the stored claim version intact. Four independent decisions: standing · persistence · visibility · action enablement.

### AI-nterprise: Governing What the Organization Knows

White paper · Version 1.0 · 3 September 2026

[White paper · v1.0 ↗](https://doi.org/10.5281/zenodo.22282125) [Read the manifesto](https://ai-nterprise.com/articles/manifesto/)

01 / Four dimensions

## One claim, four decisions.

Standing, retention, access and action each require their own decision.

v3

One claim version
**Four separate decisions**

01 / Standing

### Warranted for this use?

Purpose and consequence determine the required support.

02 / Persistence

### Kept ≠ eligible

Illustrative snapshot · one defined use

| Version | Kept | Eligible |
| --- | --- | --- |
| v1 | Retained | No |
| v2 | Retained | No |
| v3 | Retained | Yes* |

*Within its current scope and validity. History has its own retention rule.

03 / Visibility

### Who may retrieve which form?

Access includes the representation and its supporting context.

04 / Action enablement

### Who may act, within which boundary?

A valid mandate and current conditions govern the effect.

Seeing is not believing. Remembering is not accepting. Accepting is not authorizing action.

[Use the Four Questions worksheet](https://ai-nterprise.com/tools/#four-questions)

02 / Three control planes

## Three planes. One moment of use.

**Diagram transcript:** Three planes, one moment · Knowledge and Authority retain separate write authority and meet at use time. Crossed arrows forbid evidence from writing authority and a grant from manufacturing standing. Independent Assurance checks both planes and the gate, routing findings to the correction owner, never to the action path. · Knowledge · Claims · evidence · versions · standing · correction · Authority · Mandates · budgets · permissions · revocation · Four independent decisions: standing, persistence, visibility, action enablement · Gate · Use time · Action · Separate write authority · Neither rewrites the other · Assurance · tests both planes and the gate · Owner · correction

No single platform needs to own all three planes.

Evidence may not write authority.

A grant may not manufacture standing.

Policy may make action conditional on the claim’s current standing. Each plane retains its own write authority.

### A failed condition and a revoked mandate

A failed condition requires a fresh evaluation. A revoked grant requires a new act by the authority entitled to issue it.

03 / Three coupled loops

## Work. Challenge. Learn.

**Diagram transcript:** Three loops, coupled · A production loop creates work and decisions. An assurance loop challenges and tests the claim and gate. A verified correction passes through explicit authorized promotion before learning changes the next relevant case. Loops are coupled processes, distinct from the control planes. · Production · Work · recommendations · decisions · revisions · v3 · Four independent decisions: standing, persistence, visibility, action enablement · Gate · C2 · Next · case · Assurance · Challenge · evaluate · detect · Verified correction · Authorized owner · promotes the change · Learning · Changed retrieval · evaluation · policy · memory · action

Loops describe continuing processes. Planes describe control responsibilities; there is no one-to-one mapping.

If a verified correction does not alter the next relevant case, the enterprise observed an error but did not learn.

04 / An illustrative case · Chapter 9

## Kept in history. Held from a new use.

New customer accounts require review of an earlier liquidity assessment. Its earlier version remains available to explain the past decision.

![The earlier version v3 is retained in a history tray, while draft v4 awaits review.](https://ai-nterprise.com/assets/case-motion-final-desktop.webp)

**v3: kept, not eligible for the affected new use.** Draft v4 requires review. No action executed.

[Inspect the four moments](https://ai-nterprise.com/#case-study)

05 / The ten principles

## The principles behind the model.

- Draft by default

- Make promotion explicit

- Let evidence travel

- Treat provenance as necessary but insufficient

- Keep the four dimensions separate

- Scale scrutiny with consequence and persistence

- Preserve independent judgment when warranted

- Make challenge and removal first-class

- Require assurance to change the system

- Own the institutional learning loop

Ottaviano De Cicco · AI-nterprise: Governing What the Organization Knows · v1.0 · 3 September 2026.

## Use and attribution

The articles interpret the framework; they do not claim that the complete architecture has been validated in enterprise field operation. Platform work is not evidence of improved outcomes.

White paper: [CC BY 4.0 ↗](https://creativecommons.org/licenses/by/4.0/). The worksheet has its own CC BY-SA 4.0 licence.

[Explore the vocabulary](https://ai-nterprise.com/glossary/)
