IF.bus whitepaper (public-safe extract, v2.0.0)
Audience: external reviewers + operators
Reality gate: docs/22-ifttt-handover-and-roadmap.md (single-host; do not imply shipped infra)
Naming (enforced): see AGENTS.md + if.registry.json
This is a public-safe extract of the IF.bus whitepaper v2.0.0. It removes internal paths, if:// URIs, and unverifiable claims while preserving the conceptual architecture.
0) What this is (and is not)
This document is:
- A conceptual architecture summary for
if.busand its relationship toif.api. - A black/white statement of what is verified vs what is unverified in this workspace.
This document is not:
- A claim that
if.busis deployed or production-ready on the current single-host system. - A substitute for a receipt-backed demo or published trace bundle.
1) Verified vs unverified (black/white)
Verified in this workspace:
- A v2.0.0 IF.bus whitepaper exists in internal archives.
if.busandif.apiare registered product IDs with canonical path shapes inif.registry.json.
Not verified in this workspace:
- Any shipped
if.busimplementation on the current host. - Any runnable demo or receipt-backed
if.busbundle. - The paper's detailed claims about adapters, production-ready code volume, or multi-country fintech coverage.
2) Conceptual overview (architecture summary)
IF.bus is described as a central message backbone that:
- Connects core subsystems (onboard components) and external integrations (expansion slots).
- Defines standard message lanes and protocols for inter-component communication.
- Provides traceability hooks so each message can be bound to an IF.TRACE/T3 receipt when implemented.
if.api is described as the expansion-slot interface for external integrations.
This is a conceptual model; it is not evidence of deployed infrastructure.
3) Expansion slots and if.api
The paper describes multiple expansion slots for external integrations under if.api, including a "fintech expansion" slot. In this workspace, these remain conceptual unless a demo is published with receipts.
Black/white reminder:
- Slot taxonomy in the paper is a design, not a deployment.
- Any future demos must be bound to IF.TRACE/T3 receipts to be reviewable without internal access.
4) Message protocol (high-level only)
The paper frames IF.bus messaging around:
- Standardized event envelopes.
- Auditability via hashes and signatures.
- Trace emission when a receipt surface is available.
No message schemas are published here. Any future schemas should be documented with a public-safe contract and receipt-backed demos.
5) Receipt and verification plan (not yet published)
When a public demo is available, receipts should live on the canonical no-login IF.TRACE/T3 share surface:
https://infrafabric.io/static/trace/<shareId> https://infrafabric.io/static/pack/<shareId> https://infrafabric.io/static/pack/<shareId>.md
If a post-quantum signature receipt exists for a trace, it should be labeled QUANTUM READY (never "quantum-secure").
6) Next steps (to make this reviewable)
- Publish a minimal
if.busdemo with a runnable adapter or message exchange. - Bind the demo outputs to IF.TRACE/T3 receipts (HTML-first links).
- Add a public, black/white integration inventory under
if.api(status per integration).
7) Source lineage (for operators)
Source paper version: IF.bus whitepaper v2.0.0 (internal archives). This public-safe extract is intentionally conservative and strips internal-only references.