# InfraFabric dossier addendum (v1 narrative + evidence)

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.trace
  - path: /if/trace
  - status: shipped
- product_id: if.typeset
  - path: /if/typeset
  - status: preview
- product_id: if.gov
  - path: /if/gov
  - status: preview
- product_id: if.emotion
  - path: /if/emotion
  - status: preview
- product_id: if.bus
  - path: /if/bus
  - status: roadmap
- product_id: if.api
  - path: /if/api
  - status: roadmap
- 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.kb
  - path: /if/kb
  - status: preview
- product_id: if.knowledge
  - path: /if/knowledge
  - status: roadmap

## 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 a spec + reference scripts:

- IF-320: register `if.knowledge` (registry-driven; no deployment implied)
- IF-321: `if.knowledge` spec (black/white; additive-only posture)
- IF-322: deterministic addendum generator + linter (stdlib-only)
- IF-324: published `if.knowledge` LLM review pack (HTML-first)

## Evidence (verified facts only)

Homepage (“for whom” framing):

https://infrafabric.io/

LLM reviewer hub (no-login):

https://infrafabric.io/llm/

if.knowledge (module page):

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

if.knowledge review pack (HTML-first):

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

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

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

if.security posture pack (HTML-first):

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

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

https://infrafabric.io/static/hosted/review/if-gov-decision-pack-demo/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.api integrations inventory (HTML-first):

https://infrafabric.io/static/hosted/review/if-api-integrations-inventory/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.search demo (HTML-first):

https://infrafabric.io/static/hosted/review/if-search-demo/2026-01-10/index.html

Evidence-only addendum (generated via `if.knowledge` reference scripts):

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

## Interpretation (clearly labeled)

This section is intentionally “interpretation”: it describes why the artifacts above matter, and what I believe the trajectory shows. It is not presented as proof.

1) Constitutional “for whom” is now first-screen, not buried

The public homepage opens with “Constitutional AI for the subjects.” and a plain-language boundary: what a receipt proves (byte integrity) and what it does not (truth/correctness/compliance/intent). The goal is to make verification legible to non-experts (e.g., a nurse or farmer), not just to system architects.

2) The platform moved from a dossier to a published, no-login review surface

The `/llm/` hub exists specifically to reduce reviewer friction: HTML-first packs, one-URL-per-line link hygiene, and registry-driven naming. This is practical for real external review: no accounts, fewer “where is the latest?” failure modes.

3) The integration backbone (`if.bus` + `if.api`) is converging on stable contracts

Rather than building a monolith, the work emphasizes a stable envelope and transport-neutral runtime spec for the event spine (`if.bus`) and a clear adapter/integration surface (`if.api`). Security posture is treated as cross-cutting (`if.security`) rather than rewritten per product.

4) `if.knowledge` exists to reduce drift under time pressure

The `if.knowledge` pipeline is a pragmatic response to velocity: build-time generation and linting so addenda/packs can stay consistent and reproducible without relying on a single “strong model” to remember the entire system.

## Open questions / next steps

- `if.knowledge` v2: add a deterministic concept graph output (registry + schemas + task board + dossier) so interdependencies are explicit and queryable, and so future papers can be rebuilt from structured inputs rather than prose inference.
- Improve external reviewer UX further by adding a single “evidence index” landing page that links (one URL per line) to the latest packs for each registered product/module.

