Evidence ceiling E3Proof boundary

External Activation

From discovery to independent proof without founder orchestration.

Implement, evaluate, buy, operate or distribute Finality through explicit self-service paths. Seller readiness never promotes an external fact.

Activation state

Seller-controlled friction is closed. External facts remain external.

External Activation v1 evaluates the current evidence state with empty external inputs and therefore remains at A1. Its implementation package is Finality Global Outcome-Assurance v0.11.0; those are separate version domains.

External Activation
A1_SELF_SERVICE_READY
External evidence score
0/8
E4 institution-controlled
NOT PERFORMED
E5 independent
NOT PERFORMED
Paid external adoption
0
Production deployments
0
Independent implementations
0
Distribution
D0_NO_EXTERNAL_DISTRIBUTION
Neutral governance
NOT ESTABLISHED

Five paths

A stranger should know exactly what to do next.

Each path has a public starting point and an explicit evidence boundary.

Institution flow

SCOPE → Formal SCOPE → protected evaluation → external proof → production.

The buyer controls the workflow and authoritative ending. Protected access is a separate authorization step; E4/E5/E6 appear only after outside parties perform the work.

01Discover / SCOPE

Pick one consequential workflow and test whether execution acknowledgement can diverge from authoritative reality.

Open SCOPE →
02Formal SCOPE

Freeze the required authoritative ending, contradiction rules, STOP conditions and hidden-case custody.

Open Formal SCOPE →
03Protected evaluation

Continue only after identity and Finality authorization are provisioned. Signed-out access remains fail-closed.

Review access requirements →
04E4 / E5

Institution-controlled validation and independent reproduction create evidence Finality cannot self-award.

Open external proof gate →
05E6 / production

Target-system production evidence may establish customer-live only after the existing activation truth gate passes.

Production readiness →

Distribution

Packages are prepared. External distribution is still zero.

Six seller-controlled channel packages reduce listing friction, but no marketplace listing, install or transaction is counted until externally evidenced.

01

AWS MARKETPLACE

PACKAGE READY · not externally listed

02

MICROSOFT MARKETPLACE

PACKAGE READY · not externally listed

03

GOOGLE CLOUD MARKETPLACE

PACKAGE READY · not externally listed

04

GITHUB MARKETPLACE

PACKAGE READY · not externally listed

05

SERVICENOW STORE

PACKAGE READY · not externally listed

06

SALESFORCE APPEXCHANGE

PACKAGE READY · not externally listed

Procurement

A repeatable package without a fabricated sale.

Architecture, security, SBOM, privacy, support, release identity and purchase-route artifacts can be bound into a procurement offer. Legal entity, tax, payment route and customer acceptance remain independently verified gates.

01

Seller package

PREPARED

02

Ready to transact

NOT ASSERTED

03

Customer acceptance

0

04

Paid evaluation

0

05

Production adoption

0

06

Renewal / expansion

0

Machine-readable

Integrate the activation boundary, not a marketing claim.

The public APIs expose External Activation v1 state and v0.11 package schemas for intake, distribution evidence and procurement offers.

Public knowledge index

Search Finality Group

Protected, owner-only and legacy content is excluded.