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.
Live module operating map
Shipped modules
1
Preview modules
7
Latest module evidence date (build snapshot)
2026-02-21
System map
One visual, one real execution story.
This diagram represents the actual control-plane path used in reviews: execution flow, governance gate checks, coordination memory, and evidence lineage.
Execution path
Primary flow runs from ingress through `if.api`, `if.switchboard`, `if.bus`, and `if.rook`.
Governance and memory
`if.gov` gates high-impact transitions; `if.blackboard` and `if.context` preserve continuity and scoped recall.
Evidence lineage
Dashed paths indicate receipt lineage to `if.trace`, where integrity can be externally verified.
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
shippedPublic integrity layer for receipts and artifact lineage with no-login verification.
Risk reduced: Tamper ambiguity during external review
Boundary: Proves byte integrity and custody lineage; does not prove semantic correctness.
Gate to green
Keep no-login verification and claim-boundary language on all public receipts.
if.api
previewExternal integration front door with explicit contract boundaries and adapter clarity.
Risk reduced: Unbounded adapter behavior across third-party surfaces
Boundary: Separates demo adapters from committed runtime contracts.
Gate to green
Publish integration inventory with adapter status and committed endpoint tests.
if.bus
previewAdditive event backbone that normalizes transport without replacing existing substrates.
Risk reduced: Schema drift and silent payload breakage
Boundary: Reference runtime exists; public endpoint guarantees are not implied.
Gate to green
Expose deterministic transport checks with explicit external scope boundaries.
if.switchboard
previewSIP-style routing control plane with separate reliability, precision, and fallback controls.
Risk reduced: Misrouted execution under multi-agent noise
Boundary: Reliability, precision, and fallback are measured as separate controls.
Gate to green
Sustain targeted-routing benchmarks and publish reproducible stress-test traces.
if.blackboard
previewAppend-only coordination ledger preserving tasks, sessions, signals, and decision lineage.
Risk reduced: Decision drift across parallel operators
Boundary: Public surfaces are read-only projections of append-only stores.
Gate to green
Ship immutable signal/task evidence coverage with external verification samples.
if.context
previewDeterministic memory pipeline isolated from execution state to reduce drift and spill.
Risk reduced: Context leakage and cross-tenant retrieval drift
Boundary: Context retrieval is policy-scoped; no blanket semantic guarantees are implied.
Gate to green
Publish ACL boundary tests and retrieval provenance coverage for promoted surfaces.
if.gov
previewRuntime governance checkpoint that enforces stop-conditions and human escalation paths.
Risk reduced: Uncontrolled continuation beyond policy limits
Boundary: Governance artifacts are reviewable; runtime SLA/compliance guarantees are bounded.
Gate to green
Show enforced stop-conditions and human escalation outcomes in reproducible runs.
if.rook
previewPolicy-bound operator profile for autonomous execution inside strict role and lane boundaries.
Risk reduced: Runaway autonomy outside approved operating lanes
Boundary: Rook is an execution profile, not the orchestration infrastructure itself.
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.