Embed Dave shadow dossier annex and fix index link

This commit is contained in:
root 2025-12-21 16:08:41 +00:00
parent e7e6ebc1c2
commit 1ea4f0ec2a

View file

@ -48,7 +48,7 @@ This dossier documents the **InfraFabric microlab**: a functioning single-shard
- 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).
- Optional culture stress-test (explicit satire; not a protocol): **Annex (Non-Technical): The Dave Factor Shadow Dossier**`https://infrafabric.io/static/hosted/IF_DAVE_SHADOW_DOSSIER_SANITIZED.md`
- Optional culture stress-test (explicit satire; not a protocol): [Annex (Non-Technical): The Dave Factor Shadow Dossier](#annex-dave-factor-shadow-dossier)
## Cold Open — The Fuck Moment (Origin)
@ -508,7 +508,7 @@ Optional “audit culture” annexes (satire; Dave is a pattern, not a person):
- [ANNEX: IF.PHIL | Auditable Philanthropy: Access, Subsidy, and Governance Without Vibes](#annex-ifphil-auditable-philanthropy-access-subsidy-and-governance-without-vibes) — `if://doc/IF_PHIL_AUDITABLE_ACCESS/v1.0` — Author: Danny Stocker; Status: RELEASE / v1.0
- [History File Error Handling Test Report](#history-file-error-handling-test-report) — `if.api/llm/openwebui/docs/internals/HISTORY_FILE_TEST_REPORT.md`
- [CLOUD SESSION: Legal Document Database Build](#cloud-session-legal-document-database-build) — `if.legal/CLOUD_SESSION_LEGAL_DB_BUILD.md`
- [ANNEX (Non-Technical, Satire): The Dave Factor — Shadow Dossier (Culture Stress-Test)](https://infrafabric.io/static/hosted/IF_DAVE_SHADOW_DOSSIER_SANITIZED.md) — Full satire (optional): `https://infrafabric.io/static/hosted/IF_DAVE_SHADOW_DOSSIER_FULL_SATIRE.md`
- [ANNEX (Non-Technical, Satire): The Dave Factor — Shadow Dossier (Culture Stress-Test)](#annex-dave-factor-shadow-dossier) — Full satire (optional): https://infrafabric.io/static/hosted/IF_DAVE_SHADOW_DOSSIER_FULL_SATIRE.md
---
@ -26980,6 +26980,61 @@ This is the **traceability / evidence export** blueprint used by IF.emotion, des
- Verifier tool: `https://infrafabric.io/static/hosted/iftrace.py`
- Reference bundle (v2.1): `https://infrafabric.io/static/hosted/emo_trace_payload_016cca78-6f9d-4ffe-aec0-99792d383ca1.tar.gz`
<a id="annex-dave-factor-shadow-dossier"></a>
## ANNEX (Non-Technical, Satire): The Dave Factor — Shadow Dossier (Culture Stress-Test)
“Dave” is a pattern, not a person. This annex is a cultural threat model: a way to describe how rigorous systems get diluted into evidence-theater through incentives and polite ambiguity.
Canonical standalone versions:
- Sanitized (application-safe): https://infrafabric.io/static/hosted/IF_DAVE_SHADOW_DOSSIER_SANITIZED.md
- Full satire (optional): https://infrafabric.io/static/hosted/IF_DAVE_SHADOW_DOSSIER_FULL_SATIRE.md
- Dave prompt/bible: https://infrafabric.io/static/hosted/IF_DAVE_BIBLE_v1.0.md
- Patchset (how to add “Dave Factor” callouts across IF.* papers): https://infrafabric.io/static/hosted/IF_DAVE_FACTOR_PATCHSET_v1.md
### 1) What this is
The **Dave Factor** names a predictable failure mode in organizations: systems drift toward *plausible deniability* because it is individually rational.
In safety work, this shows up as: logs without receipts, consensus without vetoes, metrics without methods, and documentation that is optimized for comfort instead of truth.
This annex is a *shadow lens*: a way to read every IF.* document and ask, “How would a rational actor dilute this into harmless theater?”
### 2) What this is not
- It is not an accusation about any individual.
- It is not a substitute for a threat model.
- It is not permission to be adversarial to humans.
It is a reminder that **incentives beat intentions**.
### 3) The Dave translation (small Rosetta stone)
| Rigorous phrase | Common dilution | What to do in IF.* docs |
|---|---|---|
| “Critical failure” | “Operational headwind” | Keep severity terms; attach evidence bundles |
| “Immediate action required” | “Next sprint item” | Add explicit deadlines + owner + acceptance test |
| “Unverified claim” | “Needs follow-up” | Mark as `UNVERIFIED` and require a trace ID |
| “Audit trail” | “Observability” | Require external verifier steps and SHA sidecars |
| “Veto / stop-ship” | “Alignment session” | State veto authority and escalation path |
### 4) How InfraFabric is designed to survive contact with Dave
InfraFabrics protocols contain countermeasures against this failure mode:
- **IF.TTT**: turns disputes into verification by producing portable evidence bundles.
- **IF.BIAS → IF.GUARD**: forces escalation and multi-voice review when risk is high.
- **IF.ARMOUR**: names epistemic attack surfaces (confabulation, narrative drift) explicitly.
This annex exists to keep these protections from being “optimized away” during adoption.
### 5) Recommended pattern: one Dave callout per paper
Add a short callout box (max ~6 lines) to each major paper:
> **The Dave Factor:** If this section is paraphrased into softer language, what *exactly* becomes untestable? What artifact (trace ID / bundle / verifier step) prevents that dilution?
<a id="state-of-the-art-prompt-injection-defenses"></a>