InfraFabric
Operational control infrastructure for enterprise AI.
Coordinate execution, enforce governance checkpoints, and publish verifiable evidence from one operating surface.
Security, legal, and engineering teams can review the same facts with less reliance on vendor assertions alone.
Integrity evidence confirms artifact lineage and tamper status. It does not certify semantic or legal correctness.
Control-plane atlas
Shipped modules
1
Preview modules
7
Latest module evidence date (build snapshot)
2026-02-21
Control-plane atlas
System relationships and cross-cut security posture.
This view combines declared registry relationships, documented operating folds, receipt lineage, and the cross-cut `if.security` posture that applies across modules.
Substrate-agnostic transport posture
Contracts are defined at the envelope/control level. Runtime can sit on different underlying substrates as long as contract behavior and evidence boundaries remain intact.
Platform-agnostic execution posture
Governance checkpoints, security signals, and receipt lineage are attached to module contracts, not to one model vendor or one cloud control plane.
Claim-safe promotion posture
Module status is promoted by evidence and gate closure, not by UI polish. Preview and roadmap modules stay explicitly labeled until gates are met.
| Type | From | To | Meaning | Source |
|---|---|---|---|---|
| registry parent | if.switchboard | if.api | switchboard is declared as an if.api child module in registry metadata. | if.registry.json |
| documented runtime fold | if.api | if.bus | canonical handoff for typed integration envelopes into the event backbone. | ecosystem addendum + module contracts |
| documented runtime fold | if.bus | if.blackboard | coordination events flow into append-only task/session lineage. | ecosystem addendum |
| documented runtime fold | if.bus | if.context | transported events become policy-scoped context and derivations. | ecosystem addendum |
| documented decision flow | if.blackboard | if.gov | governance decisions consume operational chronology and signal history. | if.security posture + if.gov fold |
| documented decision flow | if.context | if.gov | bounded context artifacts feed triage/council checkpoints. | ecosystem addendum |
| registry parent | if.gov | if.rook | rook is declared as a governed execution module under if.gov. | if.registry.json |
| registry parent | if.content | if.acquire | acquire is a content-suite module with inherited claim boundaries. | if.registry.json |
| receipt lineage | if.switchboard / if.gov / if.context / if.rook | if.trace | declared uses_receipts_from lineage for reviewable integrity anchors. | if.registry.json |
| receipt lineage | if.security / if.security.secrets.detect | if.trace | security posture and detect module both publish integrity-backed artifacts. | if.registry.json |
| cross-cut posture | if.security | all core modules | one shared posture contract for security signals, evidence kinds, and containment mapping. | docs/89-if-security-posture.md |
| security submodule | if.security.secrets.detect | if.bus / if.blackboard / if.gov | detector findings emit security signals, then enter coordination and governance review lanes. | docs/89-if-security-posture.md + if.security pages |
| extended receipt lineage | if.shadowrt / if.story / if.skills / if.knowledge / if.kb / if.research / if.intelligence / if.swarm / if.emotion | if.trace | additional registry modules that declare receipt linkage to the same integrity sink. | if.registry.json |
Module readiness
Current status and evidence links.
A compact decision board for procurement review: owner, readiness, gate-to-green, and primary evidence path.
| Module | Review owner | Readiness | Gate to green | Evidence |
|---|---|---|---|---|
| if.trace public surface | Security + Legal | shipped as-of 2026-02-21 | Keep no-login verification and claim-boundary language on all public receipts. | Open receipt |
| if.api preview surface | Integration Engineering | preview as-of 2026-02-21 | Publish integration inventory with adapter status and committed endpoint tests. | Open contract evidence |
| if.bus internal runtime | Platform Engineering | preview as-of 2026-02-21 | Expose deterministic transport checks with explicit external scope boundaries. | Open transport evidence |
| if.switchboard internal runtime | Platform Engineering | preview as-of 2026-02-21 | Sustain targeted-routing benchmarks and publish reproducible stress-test traces. | Open routing evidence |
| if.blackboard internal runtime | Program Operations | preview as-of 2026-02-21 | Ship immutable signal/task evidence coverage with external verification samples. | Open coordination evidence |
| if.context internal runtime | Applied AI | preview as-of 2026-02-21 | Publish ACL boundary tests and retrieval provenance coverage for promoted surfaces. | Open retrieval evidence |
| if.gov preview surface | Operations + Legal | preview as-of 2026-02-21 | Show enforced stop-conditions and human escalation outcomes in reproducible runs. | Open gate evidence |
| if.rook internal runtime | Runtime Operations | preview as-of 2026-02-21 | Keep role-scoped policy checks, revocation paths, and lane arbitration evidence visible. | Open operator evidence |
Evaluation paths
Three tracks for enterprise review.
Each track has defined artifacts, ownership, and a clear next decision.
Security and risk review
Validate claim boundaries, runtime controls, and incident review posture.
Typical first pass: 1-2 days
Open security evidenceTechnical diligence
Review module readiness, boundaries, and promotion gates before pilot scope.
Typical first pass: 1-2 days
Open readiness boardCommercial planning
Confirm pilot scope, integration assumptions, and escalation ownership.
Typical first pass: 30-60 min
Start pilot briefingControl modules
Clear responsibilities, explicit boundaries.
Each module declares its role, what it proves, and the gate required to move from preview to shipped.
if.trace
shippedOperational role: Public integrity layer for receipts and artifact lineage with no-login verification.
Boundary: Proves byte integrity and custody lineage; does not prove semantic correctness.
Risk reduced: Tamper ambiguity during external review
Gate to green
Keep no-login verification and claim-boundary language on all public receipts.
if.api
previewOperational role: External integration front door with explicit contract boundaries and adapter clarity.
Boundary: Separates demo adapters from committed runtime contracts.
Risk reduced: Unbounded adapter behavior across third-party surfaces
Gate to green
Publish integration inventory with adapter status and committed endpoint tests.
if.bus
previewOperational role: Additive event backbone that normalizes transport without replacing existing substrates.
Boundary: Reference runtime exists; public endpoint guarantees are not implied.
Risk reduced: Schema drift and silent payload breakage
Gate to green
Expose deterministic transport checks with explicit external scope boundaries.
if.switchboard
previewOperational role: SIP-style routing control plane with separate reliability, precision, and fallback controls.
Boundary: Reliability, precision, and fallback are measured as separate controls.
Risk reduced: Misrouted execution under multi-agent noise
Gate to green
Sustain targeted-routing benchmarks and publish reproducible stress-test traces.
if.blackboard
previewOperational role: Append-only coordination ledger preserving tasks, sessions, signals, and decision lineage.
Boundary: Public surfaces are read-only projections of append-only stores.
Risk reduced: Decision drift across parallel operators
Gate to green
Ship immutable signal/task evidence coverage with external verification samples.
if.context
previewOperational role: Deterministic memory pipeline isolated from execution state to reduce drift and spill.
Boundary: Context retrieval is policy-scoped; no blanket semantic guarantees are implied.
Risk reduced: Context leakage and cross-tenant retrieval drift
Gate to green
Publish ACL boundary tests and retrieval provenance coverage for promoted surfaces.
if.gov
previewOperational role: Runtime governance checkpoint that enforces stop-conditions and human escalation paths.
Boundary: Governance artifacts are reviewable; runtime SLA/compliance guarantees are bounded.
Risk reduced: Uncontrolled continuation beyond policy limits
Gate to green
Show enforced stop-conditions and human escalation outcomes in reproducible runs.
if.rook
previewOperational role: Policy-bound operator profile for autonomous execution inside strict role and lane boundaries.
Boundary: Rook is an execution profile, not the orchestration infrastructure itself.
Risk reduced: Runaway autonomy outside approved operating lanes
Gate to green
Keep role-scoped policy checks, revocation paths, and lane arbitration evidence visible.
How the system stays auditable
InfraFabric separates routing, data movement, governance, coordination, and integrity evidence. That separation helps reduce blast radius when one layer fails.
Bounded claims: Every claim maps to an observable artifact.
Promotion criteria: Preview surfaces move to shipped only after stated gate checks.
Review continuity: Post-incident review starts from a shared evidence baseline.
Why review teams keep this in scope
Shared evidence base
Engineering, security, and legal evaluate the same artifact trail.
Clear scope boundaries
Each module states what is in scope and what remains a separate decision.
Reproducible review trail
Post-incident review starts from append-only artifacts, then reconciles with operator timelines.
Governance example
Role-scoped site rewrite under arbitration
Documented run showing lane-based review, contradiction handling, and claim-boundary enforcement.
Illustrative evidence of method, not a universal outcome guarantee.