Add submission pack bridge section

DANNY_STOCKER_INFRAFABRIC_DOSSIER.md

@@ -13,6 +13,42 @@ This project investigates the Operator-as-Architect paradigm. I do not write man
 
 ---
 
+<a id="bridge-submission-pack"></a>
+
+## 00. The Bridge: Submission Pack (Reviewer Orientation)
+
+This section exists to reduce reviewer bandwidth cost. It states exactly what is claimed, how it can be independently verified, and where the boundary is.
+
+### Executive Summary (Why)
+
+InfraFabric is a security-first agent runtime built to solve a practical problem: **autonomous systems create disputes**. “What did it do?” is a forensics question. “Why did it do it?” is a chain‑of‑custody question.
+
+Most LLM “safety” work focuses on probabilistic guardrails (block bad outputs). InfraFabric adds a deterministic layer: **verifiable provenance** (traceability, signed artifacts, and replayable evidence bundles) so that high‑stakes actions and claims can be audited without trusting the operator.
+
+This dossier documents the **InfraFabric microlab**: a functioning single-shard proof‑of‑concept (≈3 months) that implements these primitives and ships real audit artifacts.
+
+### The Reviewer Map (Claims → Proofs → Limitations)
+
+| Core claim | Proof (artifacts) | Limitation (scope / boundary) |
+|---|---|---|
+| **A) Traceability is safety.** High‑stakes agents cannot be trusted without a verifiable history of what happened (request → retrieval → decision → output). | **IF.TTT + evidence bundles**: the IF.emotion trace protocol ships a portable tarball + manifest + verifier steps that a third party can run. Start here: `https://infrafabric.io/static/hosted/IF_EMOTION_DEBUGGING_TRACE_WHITEPAPER_v3.3_STYLED.md` (includes end‑to‑end verification appendix). | **Microlab / single shard.** Proven in a single-host environment. Completeness is bounded by explicit witness boundaries; PQ is anchored at registry time (not necessarily on every hot-path artifact). No public append‑only transparency log yet. |
+| **B) Governance requires plurality.** A single model acting as “the judge” is brittle; adversarial viewpoints and escalation are required. | **IF.BIAS → IF.GUARD**: risk preflight sizes councils and escalates; councils preserve dissent and veto paths; decisions are traced. Pointers: IF.BIAS, IF.GUARD, IF.5W sections. | **Cost / latency tradeoffs.** Multi-seat governance is reserved for higher-stakes decisions; low-stakes paths use smaller councils or fast-track gates. |
+| **C) Context is the best firewall.** Static filters fail; security must distinguish “reference” vs “leak” and “discussion” vs “exfiltration”. | **IF.ARMOUR + IF.YOLOGUARD**: epistemic/anomaly detection primitives and secret/relationship screening patterns (architecture + docs). | **Domain specificity.** Calibrated for concrete security surfaces (secrets/PII/prompt injection); generalizing to broader “harmful intent” is an open research vector. |
+
+### Rosetta Stone (Closest Analog, not “equals”)
+
+| InfraFabric term | Closest industry analog | Boundary (where it differs) |
+|---|---|---|
+| **IF.TTT** (Traceable/Transparent/Trustworthy) | Supply-chain integrity patterns (SLSA/SBOM + CT-like audit thinking) | IF.TTT applies the discipline to **semantic decisions and retrieval lineage**, not just binaries. It produces portable evidence bundles + verifier steps for third-party audit. |
+| **IF.GUARD** (Council governance) | Human-in-the-loop oversight / review boards | IF.GUARD is an *algorithmic* oversight layer with explicit escalation and traceability; humans can be added, but the default artifact is machine-verifiable provenance. |
+| **IF.ARMOUR** (Assurance) | Epistemic security / anomaly detection | Armour is framed as coherence/consistency defenses (detective layer), not regex-only filtering; it does not claim to “solve truth”. |
+| **IF.swarm.s2 / IF.PACKET / IF.BUS** (Transport) | Event-driven architecture / message bus + schema enforcement | The transport layer is where contracts live: schema compliance, trace IDs, signatures, and privilege boundaries are enforced as protocol rules. |
+
+### Navigation Guide (Clean vs Origin context)
+
+- If you want the rigorous spec spine first: start at **“INFRAFABRIC: The Master White Paper”** and then the IF.TTT / IF.BIAS / IF.GUARD sections.
+- If you want the origin context (microlab lab notes / narrative artifacts): start at the **Cold Open** and IF.STORY sections (they explain why the architecture exists).
+
 ## Cold Open — The Fuck Moment (Origin)
 
 > "That's actually fascinating — and a little eerie. You may have stumbled into a moment where the mask slipped."
@@ -401,6 +437,8 @@ InfraFabric is the operating system that turns AI from a chatbot into a reliable
 
 ## Index
 
+- [00. The Bridge: Submission Pack (Reviewer Orientation)](#bridge-submission-pack)
+
 ### External audit artifacts (public, reviewer-friendly)
 
 These artifacts are published in a dedicated repo and mirrored to a static directory for reliable downloads (avoids intermittent Forgejo “raw” quirks).