The Proof Model

Definition

The Proof Model is the evidence discipline of the Zero Gravity Framework. It is how the practice distinguishes activity from movement, and delivery from value.

Why proof matters

Delivery is not proof. Activity is not proof. A decision is not proof. Movement requires evidence.

Technology output, adoption counts, model deployments and signed-off decisions are all easy to accumulate. None of them, on their own, demonstrate that the business moved. The Proof Model exists so that the honest question — did any of this move the business? — has an honest answer.

Not every form of value can be reduced to a single financial metric. The Proof Model records movement in whatever unit is genuine for the decision domain in question.

Baseline

Before any intervention, the current state is recorded:

• the current condition of the decision domain;
• the existing friction and where it appears;
• the measures already in use;
• the ownership of information, decision and action;
• the assumptions being made about how value is produced;
• the movement that is expected if the intervention succeeds.

Without a baseline, there is nothing to demonstrate against.

Measures

The Proof Model draws its measures from the Framework rather than inventing new ones per engagement:

• Return on Data (ROD) — the business movement produced by data, analytics and AI investment.
• Decision-to-Action Latency (DAL) — the elapsed time and friction between a meaningful decision and the observable action or outcome that follows.
• Automation Readiness Level (ARL) — the degree to which a decision or action flow can be safely and effectively automated.
• Information Performance — whether information can perform its intended role at the point of decision.
• Decision Value — the value created by improving a specific decision or decision flow.

Additional context-specific measures may be added where a domain requires them. No universal formula is imposed.

Intervention

The Proof Model records what actually changed. An intervention may act on:

• information;
• process;
• decision design;
• ownership and decision rights;
• governance;
• architecture;
• capability;
• automation;
• coordination between teams.

The intervention is described in terms specific enough that a successor could reconstruct what was done and why.

Movement

Movement is what became observably different after the intervention. It is measured against the baseline and expressed in the units chosen upfront.

Movement is not activity. Reports produced, meetings held and dashboards launched are not movement. Movement is a change an outside observer could see and attribute to the intervention.

Evidence Pack

<a id="evidence-pack" aria-hidden="true"></a>

The Evidence Pack is the structured record that connects the original situation, chosen measures, intervention, observed movement and supporting evidence. It is the artefact that survives handovers, audits, successor teams and time.

It typically contains:

• the decision domain in scope and the target measures;
• the baseline, with method and date;
• the intervention itself — what changed in information, process, ownership or automation;
• the ARL assessed for the domain, where relevant;
• the observed movement, measured against the baseline with the same method;
• the residual friction and the next intended move;
• named ownership for future review.

Its purpose is traceability, handover, auditability, institutional memory and learning. It replaces persuasion with record.

The Evidence Pack is a component of the Proof Model — not a separate Framework concept.

For the concise canonical definition, see the Evidence Pack Dictionary entry.

Learning

Findings from the Proof Model influence:

• the next decision;
• the next baseline;
• programme prioritisation;
• Automation Readiness in the affected domains;
• broader organisational capability.

Proof is not a report at the end of an engagement. It is a loop that keeps closing.

The proof loop

Baseline → Hypothesis → Intervention → Decision → Action → Movement → Evidence → Learning → Next baseline.

The loop is iterative, not a waterfall. Learning shapes the next baseline; the next baseline shapes the next intervention.

Application

The Proof Model runs through every programme. Discover Gravity sets the baseline. Reduce Gravity intervenes and records movement. Build Momentum makes the loop self-sustaining inside the organisation. It supports the practice; it is not a separate service.

What the Proof Model is not

• A reporting dashboard.
• A universal ROI formula.
• A sales-attribution mechanism.
• A guarantee that every intervention will produce movement — some produce learning instead, and both belong in the record.