Proof ledger

Know what is proven before you choose the next step.

TechnoMinds keeps implementation, synthetic sandbox evidence, recovery evidence, authoritative production outcomes, and external prerequisites visibly separate. These counters are never added together.

Check Wave 25 readiness Review trust center Open Fatoorah API

Separate by evidence

Five ledgers. One honest boundary.

A sandbox success can help you evaluate the workflow. It cannot become a production number by being placed next to one.

SOURCE_PROVEN

Source proven

Separate counter

Capabilities represented in the current product and code authorities.

Public tools

Bounded, browser-first acquisition tools

Primary wedge

Fatoorah

Hosted and API journeys are the acquisition focus

Hosted Fatoorah and Fatoorah API entry points
Invoice lifecycle, error guidance, mapping and sandbox authorities
Public trust, security and availability surfaces

Boundary: Implementation evidence is not a production acceptance claim.

SANDBOX_PROVEN

Sandbox proven

Separate counter

Synthetic, test-only workflows that a visitor can inspect without external provider access.

Environment

Synthetic

TechnoMinds-operated test behavior

Card required

Evaluation can start without a payment card

Wave/readiness planning tool
Hosted invoice and Fatoorah API sandbox paths
Request logs, usage, keys, webhooks and evidence surfaces

Boundary: Sandbox results are local TechnoMinds behavior, not ZATCA/FATOORA acceptance.

RESTORE_TESTED

Restore tested

Separate counter

Recovery evidence is shown only when the relevant restore scope has been exercised.

Public production restore claims

No unsupported claim is published

Evidence mode

Scoped

Request the appropriate evidence pack for procurement

Archive and evidence model is part of the canonical platform
Restore and retention scope is kept distinct from sandbox counters
Procurement evidence can be reviewed without exposing secrets

Boundary: Production object-storage, KMS and off-host restore ownership remain separate operational evidence.

PRODUCTION_PROVEN

Production proven

Separate counter

Authoritative external outcomes are counted only after a verified taxpayer and provider path exists.

Authoritative documents

No public production outcome is claimed yet

Production access

Gated

Eligibility and external evidence are separate from signup

Production milestones are fail-closed in the analytics authority
First authoritative document is distinct from synthetic first value
Production onboarding, canary and support paths are prepared for verified customers

Boundary: The public counter remains zero until the first authoritative document is actually accepted.

EXTERNAL_EVIDENCE_REQUIRED

External evidence required

Separate counter

A small number of external actions still determine whether a live outcome can be claimed.

Primary gate

Authorized FATOORA/ZATCA taxpayer and entitlement path

Claim status

Open

Verify the provider outcome before publishing production proof

Taxpayer entitlement and EGS/credential evidence
Authoritative standard and simplified invoice outcomes
Provider read-back, reconciliation and retained evidence

Boundary: TechnoMinds does not infer approval, certification, authority or acceptance from local tests.

For a notified business

Start with the question you actually have.

Check the notification, see the next preparation steps, and move into a no-card sandbox. If your business needs a live outcome, the production path stays explicit and supervised.

Open Wave 25 readiness →

Current production boundary

No authoritative production number yet.

The production counter stays at zero until an eligible taxpayer, EGS, external credential, authoritative result, reconciliation and evidence archive have all been verified.

Review the supervised pilot →