# The difference

Source: https://kimberlytegroup.com/#practice

An interactive, authored fictional model. No client results or production connections. Local deterministic calculations illustrate shared definitions, scoped access, change authority and AI boundaries. Browser controls are simulated policies, not security enforcement.

## Net revenue

Recognized invoice amounts less posted credits. Disputed items remain included until an approved accounting event changes them.

Calculation: Σ invoiced − Σ credits. Owner: Revenue controller.

Approved, all regions: $1,440,000. Proposed change: Exclude disputed invoices. Candidate, all regions: $1,000,000. The candidate is never published by the demo.

The headline falls even though no sale has changed. Finance owns the accounting treatment; a reporting preference can’t quietly replace it.

## Gross margin

Gross profit divided by net revenue for the same recognized invoice cohort. Both sides use the same region filter.

Calculation: (net revenue − cost) ÷ net revenue. Owner: Finance controller.

Approved, all regions: 30.9%. Proposed change: Exclude disputed invoices and their costs. Candidate, all regions: 31%. The candidate is never published by the demo.

Removing disputed items changes both the numerator and denominator. A better percentage alone is not evidence of a healthier business.

## Promise reliability

Deliveries on or before the original promise, divided by the original due-date cohort. Complete evidence as of 24 October 2026.

Calculation: on original promise ÷ commitments due. Owner: Service owner.

Approved, all regions: 75%. Proposed change: Use the accepted delivery date. Candidate, all regions: 91.7%. The candidate is never published by the demo.

Operations can meet a revised date while the customer still absorbs a changed promise. Keep the two meanings distinct; don’t rename one into the other.

## One contract, several uses

Board pack, operating review and AI briefing resolve the selected measure through the same definition and viewer scope. They are illustrative destinations, not product integrations.

- Finance lead: All regions; permitted measures: revenue, margin, delivery; record detail available.
- Regional lead: East region; permitted measures: revenue, delivery; record detail available.
- Service partner: East · aggregate only; permitted measures: delivery; aggregates only.

## People and authority

An owner or documented deputy may review a change. Neither selection approves or releases it. With no authorized reviewer, the proposal is held. Existing reports retain the approved definition in every state.

## AI boundaries

Internal explanation uses the approved result and current access. External sending requires separate human approval. Definition writes are blocked. Withdrawing the assistant’s delegated read access clears its rendered answer and stops the next request. The human viewer’s report access remains. Copies already taken cannot be recalled. No AI service is called.

## What gets in the way

### Agendas & infighting

A shared number changes whose story wins. That is an operating decision, and we treat it as one.

### Assumptions & inaction

“Everyone agreed” is not a release record. Someone needs the authority, the evidence, and the next move.

### Arrogance & ignorance

Confidence doesn’t settle a definition. We want to see the calculation—and what would make us change our minds.

The A.I. distinction is drawn from Synthicate: https://www.synthicate.co/

This is one possible design, not a universal architecture. A live implementation needs contracts, identity, enforcement, event history, exception handling and decisions grounded in the actual organization.