# ShadowRT (Dave Red Team) — what it is, how it works, why it exists

**Audience:** external reviewers + future operators  
**Scope:** black/white description of the ShadowRT dossier app as deployed today  
**Updated:** 2025-12-29  

Naming (avoid drift):
- Public governance brand: **IF.TRACE / T3**
- Internal legacy implementation name: **IF.TTT**
- ShadowRT is the “delivery vehicle” that makes IF.TRACE legible (and shareable) via dossiers.

---

## 1) What ShadowRT is

ShadowRT is the public-facing **Shadow Dossier generator + publisher** for InfraFabric Red Team.

It produces “mirror-first” dossiers from vendor PDFs / standards / policies and publishes a **no-login receipt surface** so a third party can verify:
- which source bytes were used
- which output bytes were published
- that the output has not been silently changed after the fact

---

## 2) Why it exists (the Trojan horse, explicitly)

Most people won’t read a vendor PDF. Some will read a short, sharp dossier.

ShadowRT is intentionally designed as the high-attention wrapper, so the serious thing gets clicked:
- the **trace receipt**
- the **offline verification path**
- the “what this proves / what this does not prove” framing

The dossiers are entertaining. The receipts are the product.

---

## 3) What it publishes (public, no-login)

Each run produces a public handle `shareId`. Everything public keys off that one handle.

Canonical receipt surface:

https://infrafabric.io/static/trace/<shareId>
https://infrafabric.io/static/pack/<shareId>
https://infrafabric.io/static/pack/<shareId>.md
https://infrafabric.io/static/dossier/<shareId>
https://infrafabric.io/static/dossier/<shareId>/download

Source mirrors (when hosted):

https://infrafabric.io/static/source/<sha256>.pdf

Sandbox fallback (if a client blocks `red-team.*` hostnames):

https://infrafabric.io/r/<shareId>

HTML-only sandbox support:
- Every important artifact has an HTML view (same path without `.md`), because some constrained reviewers can fetch HTML but reject “downloadable” assets.

---

## 4) What “verified” means (and what it doesn’t)

ShadowRT inherits the IF.TRACE black/white rule:

**Verified means:**
- `source_sha256` matches the bytes you can download as the source
- `output_sha256` matches the bytes you can download as the published output
- the trace record binds those hashes to a trace id

**Verified does not mean:**
- “the vendor claim is true”
- “the output interpretation is correct”
- “you are compliant”

ShadowRT phrases it as: “the source claims …” unless the claim is independently verifiable.

---

## 5) Process (receipt-first chronology)

1. Capture source bytes (PDF/URL) → compute `source_sha256`
2. Generate dossier output bytes → compute `output_sha256`
3. Create trace record (`trace_id`)
4. Publish the `/static/*/<shareId>` receipt surface
5. (Optional) publish offline triage bundles and a selector index under hosted static
6. Third parties verify by hashing artifacts (and optionally verifying bundles offline)

---

## 6) Quantum-ready receipts (scope)

ShadowRT trace pages may show **QUANTUM READY** when a post-quantum signature receipt exists for the trace record.

This is phrased as “ready” on purpose:
- it means PQ receipts exist today (future-proof audit history)
- it does not claim blanket “quantum-secure everything”

---

## 7) Live examples (no login)

AI Guardrails dossier (example):

https://infrafabric.io/static/trace/6qRgcR01kw_qNo63Dbs_ob9n
https://infrafabric.io/static/pack/6qRgcR01kw_qNo63Dbs_ob9n

IF.TRACE “Skeleton” paper (includes §1.4 receipt-first lifecycle):

https://infrafabric.io/static/trace/C0746UzTDsT-hG4orbKAyA9M
https://infrafabric.io/static/dossier/C0746UzTDsT-hG4orbKAyA9M

External review pack for the IF.TRACE paper (HTML-first):

https://infrafabric.io/static/hosted/review/iftrace-paper-update/2025-12-29/review-pack.html

---

## 8) Known traps (things that keep breaking reviews)

- Link wrapping breaks reviewers: put one URL per line.
- Some LLM sandboxes reject `.tar.gz` (client-side 415) even when browsers/curl succeed: provide HTML fallbacks and let humans download bundles locally.
- Do not share Forgejo UI links for receipts; share `/static/*` aliases only.
- Never claim “compliance”; claim “verifiable receipts that support audits”.

