Adoption Rail
Capability → Doorway → Product → Identity → Protocol → Platform Role → FOI Role → Proof → Expansion
Each element should have a short definition.
Capability
The continuity logic already exists before platform adoption.
Includes, where applicable:
SIF → identity → nomenclature → sampling pathway → custody → laboratory path → settlement → trend → corrective action → verification → preserved record
Doorway
The host platform provides access into FOI.
Platform Asset / Workflow → FOI Entry Point → FOI Operating Rail
Initial adoption does not require a deep API.
Product
A customer-facing product or service may initiate the event, but the product is an execution mechanism inside the continuity model.
The product does not define the underlying continuity requirement.
Identity
FOI adopts the existing customer/platform asset identity whenever available.
Protocol
The governing rail remains unchanged.
Platform Role
The platform may provide access, context, asset identity and adoption support.
The platform is not required to operate FOI Continuity.
FOI Role
FOI operates the continuity utility and preserves the accountable fuel-continuity record.
Proof
Adoption is established through actual continuity activity.
Platform Access → User Entry → Completed Event → Preserved Record → Repeat
Expansion
Fuel leads.
Mission-critical fluids may later adopt the same continuity architecture after fuel proves the rail.
Platform Qualification Protocol
1. Fit
Does the platform already manage relevant assets, PM, compliance, reliability, life-safety or operational records?
2. Gap
Is cradle-to-grave fuel-quality continuity absent or incomplete?
3. Light Doorway
Can initial access occur without rebuilding either system?
4. Clean Identity
Can the existing asset identity remain intact while FOI operates the continuity event?
5. Protocol Intact
Can FOI preserve the governing rail unchanged?