Download Markdown · Download source · if.trace receipt · Review pack (HTML) · Review pack (MD) · Single-file pack (HTML) · Single-file pack (MD) · Marketing excerpt (HTML) · Marketing excerpt (MD)

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:

This document is not:


1) Verified vs unverified (black/white)

Verified in this workspace:

Not verified in this workspace:


2) Conceptual overview (architecture summary)

IF.bus is described as a central message backbone that:

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:


4) Message protocol (high-level only)

The paper frames IF.bus messaging around:

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)

  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.