RunOnProofDocs
Evidence firstScoped decisions
RunOnProof documentation

Catalog

The RunOnProof catalog separates technical products from business solutions. A technical product answers one narrow question. A solution combines several products, a policy, and an action into a business workflow.

This distinction matters. A company-status check can contribute to supplier approval, but it is not supplier approval by itself. An invoice match can contribute to payment authorization, but it does not prove that the payee owns the destination account.

Seven founding technical products

Technical product Question it answers What it does not claim
Resolve Legal Entity Which registered company does the input refer to? That the company is safe or approved
Verify Company Legal Status What supported legal-status facts are current? Solvency, reputation, or absence of all risk
Match Invoice to Company Does invoice identity align with the resolved company? That the invoice is genuine, unique, or payable
Match Business Payee Is the proposed payee sufficiently linked under available evidence? Universal bank-account ownership
Approve Supplier Does the supplier satisfy the named onboarding policy? Permanent approval for every purpose
Authorize Vendor Payment-Detail Change Can this change proceed under the change-control policy? That any later payment is automatically authorized
Authorize Business Payment Does this payment satisfy the named policy and current evidence? A standing mandate for future payments

Each product is deliberately small. The output should identify the legal entity, claim, jurisdiction, evidence, observation time, policy when applicable, decision, conditions, and limitations.

Six business-facing offers

Company Check

Resolves the legal entity and returns supported company facts. It is the simplest entry point and the foundation for deeper workflows.

Supplier Approval

Combines identity, legal status, available restriction evidence, customer rules, and any required supporting checks to decide whether a supplier may be onboarded.

Invoice & Payee Verification

Tests whether the invoice points to the expected company and whether the proposed recipient is supported by available binding evidence. A limitation in either part remains visible.

Payment Authorization

Applies a named policy to the company, invoice, payee, amount, evidence, and approval conditions for one payment action.

Vendor Change & Continuous Authorization

Controls sensitive changes and re-evaluates whether an existing supplier remains authorized when evidence, policy, time, or risk signals change.

Company Capability Passport

Reuses still-valid, scoped capabilities derived from committed decisions. It is a transversal layer, not a universal badge.

How to read availability

State Meaning Safe behavior
Active Published for the declared scope with required gates satisfied Use within scope after checking health
Active — limited Usable, but geography, source, claim, volume, or freshness is constrained Show the limitation and block unsupported expansion
Conditioned Requires a source, configuration, approval, access path, or economic gate Do not present as immediately executable
Inactive Implemented or documented but not enabled for production use Test only where explicitly allowed
Roadmap Planned; not a current product promise Do not integrate as available
Blocked A known dependency prevents safe delivery Return REVIEW or STOP according to the contract

Catalog truth versus route presence

A route can exist for testing, compatibility, or future activation. OpenAPI can describe a contract before production is sellable. Neither proves that the product is active, purchasable, or backed by healthy sources. The machine-readable production catalog and coverage information are authoritative.

One action, one decision, one charge

A commercial execution must preserve a clear unit: one intended action, one committed decision, and at most one corresponding charge. Internal evidence reads do not become separate surprise purchases. Safe replay of the same committed action must not create a second economic event.

Choosing the right entry point

Use Company Check when you only need identity and scoped status. Use Supplier Approval when the business question is onboarding. Use Invoice & Payee Verification when the risk is document-to-company and recipient alignment. Use Payment Authorization only when the full payment policy and approvals are ready. Use the Passport to avoid repeating valid work, never to skip evidence that has expired or changed.

RunOnProof public documentationExplicit coverage · scoped claims · evidence first