index.md
HTML wrapper for HTML-only fetchers; content is shown verbatim.
Raw file
Links (extracted)
Clickable list for reviewers; avoids copy/paste line-wrap issues.
# 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.bus` and its relationship to `if.api`.
- A black/white statement of what is verified vs what is unverified in this workspace.
This document is not:
- A claim that `if.bus` is 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.bus` and `if.api` are registered product IDs with canonical path shapes in `if.registry.json`.
- A receipt-backed public share exists for this extract (see “Receipt-backed publication” below).
Not verified in this workspace:
- Any shipped `if.bus` implementation on the current host.
- Any runnable demo or receipt-backed `if.bus` bundle.
- 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-backed publication (HTML-first)
Public doc (hosted-static; HTML-first):
https://infrafabric.io/static/hosted/review/if-bus-whitepaper/2026-01-05/index.html
Raw Markdown (optional):
https://infrafabric.io/static/hosted/review/if-bus-whitepaper/2026-01-05/index.md
IF.TRACE/T3 receipt (this publication):
https://infrafabric.io/static/trace/ia6GfbdBzr-yfpkYBSiK-IE2
Pack (HTML view; sandbox-friendly):
https://infrafabric.io/static/pack/ia6GfbdBzr-yfpkYBSiK-IE2
Pack (raw Markdown):
https://infrafabric.io/static/pack/ia6GfbdBzr-yfpkYBSiK-IE2.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)
1) Publish a minimal `if.bus` demo with a runnable adapter or message exchange.
2) Bind the demo outputs to IF.TRACE/T3 receipts (HTML-first links).
3) 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.