# InfraFabric dossier addendum (v4 narrative + evidence + diagrams)

Generated (UTC): 2026-01-11

Status: ADDENDUM (evidence links + clearly-labeled interpretation)

Black/white boundary: published receipts (when present) can prove the bytes you downloaded match a public hash. They do not prove factual correctness, safety, compliance, or intent.

## Source dossier

- filename: `DANNY_STOCKER_INFRAFABRIC_DOSSIER_20251223-1925CET.md`
- submitted_utc: 2025-12-23
- local_sha256: d7832c254ae95da2ec1e2026a3bff8748596b3cc3983673fd027f6e437b13f46

## Registry excerpt

Source of truth (public mirror):

https://infrafabric.io/llm/if.registry.json

Selected entries (current status is registry-driven; this addendum does not invent statuses):

- product_id: if.gov
  - path: /if/gov
  - status: preview
- product_id: if.trace
  - path: /if/trace
  - status: shipped
- product_id: if.security
  - path: /if/security
  - status: roadmap
- product_id: if.security.secrets.detect
  - path: /if/security/secrets/detect
  - status: preview
- product_id: if.bus
  - path: /if/bus
  - status: roadmap
- product_id: if.api
  - path: /if/api
  - status: roadmap
- product_id: if.knowledge
  - path: /if/knowledge
  - status: roadmap
- product_id: if.kb
  - path: /if/kb
  - status: preview

## Task board excerpt (if.knowledge chain)

Public task board snapshot:

https://infrafabric.io/llm/task-board.html

This addendum is supported by a build-time pipeline module (`if.knowledge`) with reference scripts and published review packs:

- IF-322: deterministic addendum generator + linter (stdlib-only)
- IF-330: gov-first one-page system map (reviewer navigation)
- IF-331: `if.gov` portfolio-based council structure (design target)
- IF-333: Anthropic addendum v2 (adds `if.gov` development + cost posture)
- IF-334: Anthropic addendum v3 (adds deeper “why security” + “why bus safe path” explanation)

## Evidence (verified facts only)

Homepage (“for whom” framing):

https://infrafabric.io/

LLM reviewer hub (no-login):

https://infrafabric.io/llm/

Gov-first system map (HTML-first):

https://infrafabric.io/static/hosted/review/infrafabric-system-map/2026-01-11/index.html

if.gov product page:

https://infrafabric.io/if/gov/

if.gov review pack:

https://infrafabric.io/llm/products/if-gov/

if.gov decision pack demo (HTML-first):

https://infrafabric.io/static/hosted/review/if-gov-decision-pack-demo/2026-01-05/index.html

if.gov council seats pack (HTML-first):

https://infrafabric.io/llm/products/if-gov/council-seats/2026-01-08/index.html

if.gov triage/council/extended spec (HTML-first):

https://infrafabric.io/llm/products/if-gov/triage-council-extended-spec/2026-01-10/index.html

if.gov portfolio-based council structure (HTML-first):

https://infrafabric.io/llm/products/if-gov/council-portfolios/2026-01-11/index.html

if.trace product page:

https://infrafabric.io/if/trace/

if.trace review pack:

https://infrafabric.io/llm/products/if-trace/

if.security posture (HTML-first):

https://infrafabric.io/llm/products/if-security/security-posture/2026-01-11/index.html

if.security.secrets.detect (preview page):

https://infrafabric.io/if/security/secrets/detect/

if.bus runtime spec pack (HTML-first):

https://infrafabric.io/llm/products/if-bus/bus-runtime-spec/2026-01-11/index.html

if.bus runtime sandbox (HTML-first):

https://infrafabric.io/llm/products/if-bus/runtime-sandbox/2026-01-10/index.html

if.api integrations inventory (HTML-first):

https://infrafabric.io/static/hosted/review/if-api-integrations-inventory/2026-01-05/index.html

if.api GitHub webhook demo (HTML-first):

https://infrafabric.io/static/hosted/review/if-api-github-webhook-demo/2026-01-05/index.html

if.kb bus/api developer KB snapshot (HTML-first):

https://infrafabric.io/static/hosted/review/if-bus-api-kb/2026-01-07/index.html

if.knowledge module page:

https://infrafabric.io/if/knowledge/

if.knowledge review pack (HTML-first):

https://infrafabric.io/llm/products/if-knowledge/

Evidence-only addendum (generated via `if.knowledge` scripts, HTML-first):

https://infrafabric.io/static/hosted/review/infrafabric-anthropic-addendum/2026-01-11/index.html

Anthropic addendum v1 (human narrative, HTML-first):

https://infrafabric.io/static/hosted/review/infrafabric-anthropic-addendum/2026-01-11/v1/index.html

Anthropic addendum v2 (HTML-first):

https://infrafabric.io/static/hosted/review/infrafabric-anthropic-addendum/2026-01-11/v2/index.html

Anthropic addendum v3 (HTML-first):

https://infrafabric.io/static/hosted/review/infrafabric-anthropic-addendum/2026-01-11/v3/index.html

## Interpretation (clearly labeled)

This section is intentionally “interpretation”: it explains the design logic and how the pieces fit together. It is not presented as proof.

### 0) The sentence I want the reader to carry

InfraFabric is an attempt to turn raw research on “Constitutional AI for the subjects” into a set of composable products where:
- governance is reproducible without a black-box model,
- infrastructure choice is a detail (platform-agnostic),
- and the long-run operating cost trends toward deterministic, low-token, auditable workflows.

### 1) Gov-first, for-subjects: how the parts fit together (diagram)

```mermaid
node{init: {'theme': 'base'}}%%
flowchart TB
  GOV["if.gov<br/>decision packs<br/>(preview)"]
  TRACE["if.trace<br/>no-login integrity receipts<br/>(shipped)"]
  SEC["if.security<br/>evidence posture + containment<br/>(roadmap)"]
  BUS["if.bus<br/>event spine + control plane<br/>(roadmap)"]
  API["if.api<br/>adapters + inventories/demos<br/>(roadmap)"]
  API --> BUS
  BUS --> GOV
  GOV --> TRACE
  SEC --> GOV
  SEC --> BUS
  BUS --> TRACE

```

Interpretation:
- `if.gov` is the “decision contract” layer: it defines how decisions are recorded so they can be replayed later.
- `if.trace` is the public verification layer: it can prove byte integrity without logins.
- `if.security` is the shared posture layer: it defines evidence posture and containment (design target), so modules don’t drift into incompatible definitions of “safe to act”.
- `if.bus` is the event spine: it is meant to carry real-world inputs through the contract ecosystem without forcing infrastructure lock-in.
- `if.api` is the integration surface: it normalizes external systems into the bus contract.

### 2) Why “all the security” exists (and why it’s a subjects-first requirement)

Security isn’t a tax; it’s a seatbelt—insurance against silent failure that reduces likelihood and blast radius, making incidents auditable.

In a “for-subjects” posture, security is not mainly about preventing every bad thing. It is about making sure the system cannot quietly:
- act on ambiguous evidence,
- hide failure modes behind proprietary model behavior,
- or degrade into “trust me” operations when incentives push toward speed.

That’s why InfraFabric emphasizes cross-cutting primitives like:
- evidence posture (observed vs derived vs hypothesized),
- actuation gates (hypothesis must not trigger automation),
- and containment (hold/quarantine/review as first-class outcomes).

### 3) Decision packs: reproducible governance without the same black box (diagram)

```mermaid
node{init: {'theme': 'base'}}%%
flowchart LR
  SCEN["scenario.json<br/>structured inputs"]
  EVID["evidence items<br/>explicit links + posture"]
  CHECK["deterministic checks<br/>(where possible)"]
  SYN["LLM summary (optional)<br/>untrusted narrative"]
  DEC["decision pack<br/>vote + dissent + stop conditions"]
  REC["if.trace receipt<br/>byte integrity"]
  SCEN --> EVID --> CHECK --> DEC --> REC
  CHECK -. "optional" .-> SYN -.-> DEC

```

Interpretation:
- the pack is the unit of record (not the model output),
- deterministic checks are the goal for actuation,
- and LLM text is allowed only as an optional narrative helper (not the sole basis for automation).

### 4) Platform-agnostic event spine: why `if.bus` can absorb infrastructure and APIs

The intent of `if.bus` is “transport-neutral contracts”: one stable envelope, plus a minimal transport interface, so application code does not have to change when infrastructure changes.

That matters because infrastructure inevitably changes over a 5-year horizon (vendors, regions, compliance, cost, incident response).

The design posture is “inside-out” (assume compromise) so the runtime includes first-class mechanisms for:
- containment (pause/quarantine),
- replay (audited, bounded),
- budgets and backpressure (detect runaway behavior),
- and structured DLQ events (fail loud, not silently).

### 5) “The safe path is the easy path” for agents and operators (diagram)

```mermaid
node{init: {'theme': 'base'}}%%
flowchart TB
  IN["adapter ingress"]
  VAL["schema + size checks"]
  ROUTE["route to topic"]
  OK["consumer success<br/>ack"]
  BAD["invalid / policy fail<br/>DLQ event"]
  CTRL["control plane<br/>pause / quarantine / replay"]
  IN --> VAL --> ROUTE --> OK
  VAL --> BAD
  ROUTE --> BAD
  CTRL -.-> ROUTE

```

Interpretation:
- compliance becomes “desirable” when the constraints are explicit and the failure modes are deterministic.
- agents (and humans) can only adapt quickly when the system tells them, precisely, why they failed and what the safe path is.

### 6) Cost posture: progressive determinism (tokens trend downward)

The cost posture is a progressive engineering path:
- bootstrap with simulated seats (expensive),
- formalize seats into charters and output schemas,
- move actuation to deterministic checkers (cheap),
- and keep LLMs (if any) as optional narratives.

The key claim is directionality: long-run governance should become reproducible and low-token by default.

## Open questions / next steps

- Add a publishable “actuation gate” demo pack for `if.gov`: show that HYPOTHESIS-only evidence cannot trigger automation (design target from `if.security` posture).
- For `if.bus`: publish a minimal “adapter safe path checklist” (schema + idempotency + budgets + DLQ posture) so adoption becomes measurable (not vibes).
- For diagrams: decide whether to keep Mermaid-only (renderer in wrappers) or add a build-time SVG renderer (D2/Graphviz) for higher aesthetic control (would require adding tooling).
