Pick one consequential workflow and test whether execution acknowledgement can diverge from authoritative reality.
Open SCOPE →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.
Build a compatible implementation against the Minimal Assurance Profile, run conformance, attack it, and publish an attributable result.
→EVALUATOREvaluate independentlyRun institution-controlled E4 or independent E5 with hidden cases and externally controlled signing/trust roots.
→BUYEREvaluate as an institutionChoose one consequential workflow in SCOPE, freeze authoritative state in Formal SCOPE, then continue to protected evaluation when authorized.
→OPERATOROperate a WitnessRun the independent Witness/verifier path with isolated custody and no requirement for Finality credentials.
→DISTRIBUTION_PARTNERDistribute FinalityReview channel packages for cloud marketplaces, enterprise stores, reseller or direct distribution without implying a live listing.
→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.
Freeze the required authoritative ending, contradiction rules, STOP conditions and hidden-case custody.
Open Formal SCOPE →Continue only after identity and Finality authorization are provisioned. Signed-out access remains fail-closed.
Review access requirements →Institution-controlled validation and independent reproduction create evidence Finality cannot self-award.
Open external proof gate →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.
AWS MARKETPLACE
PACKAGE READY · not externally listed
MICROSOFT MARKETPLACE
PACKAGE READY · not externally listed
GOOGLE CLOUD MARKETPLACE
PACKAGE READY · not externally listed
GITHUB MARKETPLACE
PACKAGE READY · not externally listed
SERVICENOW STORE
PACKAGE READY · not externally listed
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.
Seller package
PREPARED
Ready to transact
NOT ASSERTED
Customer acceptance
0
Paid evaluation
0
Production adoption
0
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.