Skip to content
Governance / Claims & ProofGovernance

Earn every consequential statement.

Can we substantiate and publish it?

First classify the exact statement. Then attach evidence, scope, permission, ownership, and a review date. Voice fit never substitutes for publication authority.

01 / The decision

No evidence by association.

Only the current Proof Ledger determines publication permission—not a deck, screenshot, website, invoice, customer conversation, or this guideline.

Proof Ledger publication boundary

Public methodology only. No live record, evidence, approval, or permission data is included here.

Canonical
Publication boundaryAuthenticated source required

These guidelines cannot approve a customer, metric, SLA, price, legal statement, or commercial claim.

Exact evidence, scope, permissions, ownership, approval, and expiry remain in the authenticated system of record. Appearance in a specimen never grants permission.

Public source
Methodology only
Live records
Not included
Publication decision
Authenticated gate

02 / See the gate

Move from draft to an explicit release decision.

The gate is intentionally short. Prohibited language stops at classification. Other consequential statements continue only when their exact evidence and permissions are complete.

The human publication flow

The shortest path from draft language to an explicit release decision.

Canonical
  1. 01

    Draft

    Write the exact statement and intended channel. A draft has no permission.

  2. 02

    Classify

    Choose voice-safe, scope-dependent, proof-gated, or do not use.

  3. 03

    Evidence + permissions

    Attach the reproducible source, scope, rights, owner, approval, and renewal.

  4. 04

    Approved or blocked

    Publish only exact approved use; otherwise revise, hold, or retire.

03 / How it works

Three statements take three different paths.

The textual class and outcome remain visible at every step. Green, amber, and red reinforce the decision; color never carries it alone.

Voice-safe pattern

Illustrative classification path

Illustrative
“Run commerce and operations on one connected foundation.”
May proceed to scope check
  1. 01Fits the Ordering.co voice
  2. 02Confirm applicable product capabilities
  3. 03Use only in the confirmed scope

Eligible for scoped use; not evidence by itself.

Scope-dependent

Illustrative classification path

Illustrative
“Keep control of your brand, data, and customer relationships.”
Scope check required
  1. 01Fits the narrative
  2. 02Confirm plan, rights, and responsibilities
  3. 03Do not imply platform or source-code ownership

Blocked until exact scope and qualification are attached.

Requires proof or permission

Illustrative classification path

Illustrative
“Processed 2.4M orders in July.”
Evidence gate required
  1. 01Define the exact metric and period
  2. 02Attach the approved source and applicable product scope
  3. 03Confirm owner, permissions, expiry, and publication channel

Blocked until the exact evidence record is approved for public use.

Do not use

Illustrative classification path

Illustrative
“Unlimited enterprise scale.”
Blocked at classification
  1. 01Contains an absolute promise
  2. 02No evidence can make “unlimited” precise
  3. 03Replace with a measured, scoped statement or omit

Blocked. Do not send to evidence review.

04 / Use and avoid

Gate the exact statement, not the general idea.

Use

Attach the exact wording to its record.

Keep definition, period, source, product, geography, permissions, owner, and expiry with the statement through final production.

Avoid

Do not inherit proof from proximity.

A known customer, a private invoice, a historical metric, or an approved visual layout does not authorize a public claim.

05 / Evidence module

Design the context, not only the result.

The module comes before the field reference so teams can see the complete object first. The specimen is deliberately non-publishable and labels every missing value.

Complete evidence module anatomy

A finished layout with deliberately empty evidence values. It is not a customer result or publishable proof.

Illustrative
Illustrative anatomy · no result supplied

EXACT CLAIM

[Measured outcome]

[The exact, approved statement would appear here.]

Incomplete · not publishable
Definition
[What is measured + exclusions]
Period
[Start date → end date]
Source
[Reproducible system + owner]
Scope
[Product · geography · cohort]
Relationship
[Current or historical]
Permissions
[Name · metric · channel · territory]
Owner + approval
[Accountable owner · approver]
Renewal
[Review or expiry date]
Do not publish: placeholders are visible and no approved-public record is attached.

06 / Technical reference

Open the record when preparing release.

Fields, consequential-claim examples, and the final publication check remain secondary to the human flow above.
Proof record fieldsThe ten fields required before a consequential statement can be publishable.
  1. 01

    Exact claim

    The wording that will appear in the approved channel.

  2. 02

    Definition

    What the statement measures or means, including exclusions.

  3. 03

    Period

    The measurement window or date of record.

  4. 04

    Source

    A reproducible system or primary record and its owner.

  5. 05

    Scope

    Product, cohort, segment, geography, and relationship.

  6. 06

    Relationship

    Whether the customer or operational relationship is current or historical.

  7. 07

    Permissions

    Name, logo, metric, quote, channel, and territory rights.

  8. 08

    Owner

    The person accountable for renewal, correction, and retirement.

  9. 09

    Approval

    The recorded approver and exact approved use.

  10. 10

    Renewal or expiry

    When the evidence must be checked again or removed.

Publication checklistRun this check against the final asset, not only the source copy.
  • The wording matches the approved exact claim.
  • Definition, period, and source remain attached where needed.
  • Product, segment, geography, and relationship scope are unchanged.
  • Name, logo, metric, and quote permissions cover this channel and territory.
  • Qualifications and disclosures remain inseparable from the statement.
  • The evidence has an accountable owner and has not expired.
  • The source can reproduce the result.
  • The published asset links internally to its Proof Ledger record.
Classification referenceExamples of consequential statements by gate.

Requires proof or permission

Enterprise and longevity
Enterprise-proven, operating history, founding dates, or category leadership.
Scale and performance
Orders, locations, capacity, latency, availability, uptime, or time-to-value.
Customers
Names, logos, quotes, cases, rankings, and relationship language.
Comparisons
#1, best, faster, lower cost, or customer outcomes.

Do not use

Unlimited
Support, updates, stores, APIs, capacity, or scale.
Absolute ownership
100% ownership when platform or source-code rights are excluded.
Zero fees
Do not use where platform, usage, add-on, tax, or third-party charges can apply.
Guarantees
Launch, approval, revenue, security, or performance outcomes outside Ordering.co’s control.

The public page defines the record shape. It does not expose or replace the authenticated source of truth.

Expression

Voice

Evaluate whether language sounds like Ordering.co before applying this separate publication gate.

Governance

Governance overview

See the owners, source hierarchy, and review practices that keep decisions trustworthy.