index.md

HTML wrapper for HTML-only fetchers; content is shown verbatim.

Raw file

Links (extracted)

Clickable list for reviewers; avoids copy/paste line-wrap issues.
# InfraFabric dossier addendum (v2 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.gov
  - path: /if/gov
  - 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.typeset
  - path: /if/typeset
  - status: preview
- product_id: if.emotion
  - path: /if/emotion
  - 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 reference scripts and published review packs:

- IF-322: deterministic addendum generator + linter (stdlib-only)
- IF-327: Anthropic addendum v1 (human narrative; black/white)
- IF-328: deterministic concept graph v2 (registry + schemas + task board + dossier mentions-only)
- IF-330: gov-first one-page system map (reviewer navigation)
- IF-331: `if.gov` portfolio-based council structure (design target)

## 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/

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

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

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

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

if.knowledge graph v2 (HTML-first):

https://infrafabric.io/llm/products/if-knowledge/knowledge-graph/2026-01-11/index.html

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.security posture (HTML-first):

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

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

## 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) Reduce “sprawl perception” with a deliberate reading order

InfraFabric has many modules because it is designed as a contract ecosystem, not a monolith. This can read as sprawl unless the introduction is deliberate.

The gov-first one-page system map is meant to fix this by giving reviewers a stable ordering:
`if.gov` → `if.trace` → `if.security` → `if.bus`/`if.api` → supporting modules.

### 2) `if.gov` as decision-contract infrastructure (not “LLM council theater”)

The credible claim is not “a council of models decides”.

The credible claim is:
- the **decision pack** is the unit of record
- evidence links are explicit
- dissent is preserved
- deterministic checks are used where possible
- LLM text (if used at all) is **optional and untrusted**
- integrity is bound via `if.trace` receipts (byte integrity, not truth)

Evidence typing (OBSERVED / DERIVED / HYPOTHESIS) is treated as a cross-cutting posture defined in `if.security`. It is a design target for actuation gates; it should not be described as “fully enforced” unless an end-to-end runtime demonstrator exists.

### 3) `if.gov` development + cost posture (token budgets + progressive determinism)

The portfolio-based council structure is not proposed as “20 LLM roleplayers forever”.

It is proposed as a **progressive engineering path** that makes governance legible to non-experts while driving toward model-agnostic determinism:

1) **Phase 1 (bootstrap; expensive)** — simulate seats (LLM optional), but force schema-constrained outputs, explicit evidence links, and dissent capture.
2) **Phase 2 (structured; cheaper)** — convert seats into explicit charters (must-evaluate questions + output schema).
3) **Phase 3 (hybrid; cheaper)** — deterministic checkers enforce actuation gates and constraints; LLMs (if used) draft summaries only.
4) **Phase 4 (deterministic; near-zero tokens)** — stdlib checkers decide; LLMs become optional narrative helpers.

Token costs are therefore not “a permanent burn”; they are a temporary research instrument to learn what needs to be made deterministic.

Practical guardrails (design target):
- start with a minimal council (e.g., 5 seats) and expand only if/when it produces measurable value
- set a per-decision token budget cap and treat it as a first-class constraint in the decision pack
- prioritize building deterministic checkers for the seats that most often block/approve decisions (finance, risk, legal, safety, technical)

Black/white boundary: any numeric cost model must be treated as a local measurement or an illustrative placeholder unless backed by a published measurement artifact.

### 4) Why this is aligned with the fellowship theme

This posture is aimed at “Constitutional AI for the subjects” in a strict sense:
- reduce reliance on black boxes
- make decisions replayable
- keep proofs legible without privileged access

## Open questions / next steps

- Define a minimal `if.gov` “actuation gate” checker: enforce that HYPOTHESIS cannot trigger automation (design target from `if.security` posture).
- Add token-budget reporting to decision packs (design target): record “budget spent” vs “budget allowed” and what drove it (seat count, context size, research requests).
- Publish standalone public demo packs for `if.gov.triage`, `if.gov.council`, and `if.gov.council.extended` so SKU-level behavior is reviewable end-to-end (not just spec-level).
- For the portfolio-based council: agree the first 5 seats to formalize into deterministic checkers, and define the evidence required to promote each seat from “simulated” → “implemented”.