if. if.
Home / if / papers

Regulatory spine (03b)

Rendered from repo-local docs/242-infrafabric-regulatory-spine-addendum-03b-v1.0-2026-02-01T151451Z.md. This page is presentation only; treat the document’s own black/white section as authoritative.

InfraFabric — Regulatory Spine (03b addendum) (v1.0)

Danny Stocker | InfraFabric Research | ds@infrafabric.io | 2026-02-01

Document: 242-infrafabric-regulatory-spine-addendum-03b-v1.0-2026-02-01T151451Z

Generated (UTC): 2026-02-01T15:14:51Z

Purpose: A short, procurement-grade “regulatory spine” that should be read before the historical uncut dossier. It makes the actor model (subjects/operators/payers/frontier labs) explicit so readers don’t accidentally optimize for the wrong stakeholder.

Black/white (required):

  • This document is a lens, not a compliance guarantee.
  • VERIFIED claims are limited to publicly retrievable bytes and deterministic behaviors (see Verify).
  • NORMATIVE claims are architecture/doctrine recommendations, not legal advice.
  • Receipts prove byte integrity only; not correctness, safety, compliance, or intent.

Reading order (Anthropic pack intent): 01 (productization evidence) → 02 (system map) → 03b (this doc) → 03 (uncut dossier, unchanged)

If you read the dossier without the lens, you will treat narrative as evidence and evidence as narrative.

1) The doctrine you need up-front (NORMATIVE)

Regulatory scrutiny is rarely about whether you have a policy PDF. It is about whether:

  • you can reconstruct what happened (audit trails),
  • you can bound what happened (least privilege + failure containment),
  • and you can prove the boundary to an outside reviewer without privileged access.

InfraFabric’s thesis is: the missing primitive is a review surface that survives hostile environments (GET-only, no login, sandboxed LLMs, truncation).

Doctrine source (repo-local, audit-grade):

  • docs/239-regulatory-design-patterns-infrafabric.md

2) Actor model (subjects / operators / payers / frontier labs)

Regulatory frameworks exist because incentives drift.

  • Subject: the human impacted by a decision, inference, or data flow.
  • Operator: the party running the system and controlling access/log retention.
  • Payer: the party paying for outcomes (often pressures for speed and coverage).
  • Frontier lab / upstream vendor: the model/tool supplier (updates change capabilities and risk).

InfraFabric patterns are designed so a system can be audited in a way that is:

  • fair to the subject,
  • enforceable for the operator,
  • honest to the payer,
  • and legible under upstream drift.

If the subject can’t audit the runtime that affects them, the “constitution” is for the architects, not the governed.

3) Patterns (short list)

These are the patterns an auditor actually cares about:

  1. Evidence-first surfaces (/llm): GET-only, text-first, no login.
  2. Byte integrity receipts (if.trace): sha256 (and PQ-ready when present).
  3. Chain of custody envelopes (if.bus): correlation IDs + payload hashes + DLQs.
  4. Adapter boundary (if.api): normalize tool calls and make side effects inspectable.
  5. Context as evidence (if.context): span-addressed provenance (what bytes were read).
  6. Governance packs (if.gov): decisions as auditable units-of-record (not vibes).
  7. Skills as reviewable contracts (if.skills): tool affordances + gating rules as bytes.
  8. Public/private separation (/llm vs /mcp): evidence plane vs tenant/NDA plane.

If you can’t explain your failure modes, you don’t have controls — you have optimism.

4) What to do with the uncut dossier (NORMATIVE)

The historical uncut dossier is included for narrative completeness. Treat it as:

  • motivation,
  • design intent,
  • and “why this exists” context.

Do not treat it as a substitute for verifiable artifacts.

Uncut dossier rule:

  • The uncut dossier bytes must remain unchanged (frozen historical artifact).

This addendum exists to prevent the common procurement failure mode: a long narrative gets mistaken for auditability.

5) Verify (repo-local + public)

Repo-local sanity:

python3 -m json.tool if.registry.json > /dev/null
rg -n \"VERIFIED:|NORMATIVE:|HYPOTHESIS:\" docs/239-regulatory-design-patterns-infrafabric.md | head

Public, no-login verification (GET-only):

curl -fsS https://infrafabric.io/llm/conformance.json.txt | python3 -m json.tool > /dev/null
curl -fsS https://infrafabric.io/llm/if.registry.json.txt | python3 -m json.tool > /dev/null
curl -fsSI https://infrafabric.io/llm/entrypoint.json.txt | head -n 5

6) Files touched / not touched (IF-931)

Files touched:

  • docs/239-regulatory-design-patterns-infrafabric.md
  • docs/240-infrafabric-productization-pack-v9-singlefile-2026-02-01T151451Z.md
  • docs/241-infrafabric-system-explainer-v3-2026-02-01T151451Z.html
  • docs/242-infrafabric-regulatory-spine-addendum-03b-v1.0-2026-02-01T151451Z.md
  • /root/tmp/if-931-openclaw-evidence/** (local evidence capture; public-safe sources + sha256)

Files not touched (explicit):

  • docs/236-infrafabric-productization-pack-v8-singlefile-2026-02-01T125116Z.md (frozen prior version)
  • docs/237-infrafabric-system-explainer-v2-2026-02-01T125116Z.html (frozen prior version)
  • Anthropic uncut dossier bytes (03_DANNY_STOCKER_INFRAFABRIC_DOSSIER_UNCUT_20251223-1925CET.*) (frozen historical artifact)