Ten named pathogens. Four antibody gates. Four hygiene rules. The operating contract that prevents the same fuckup from firing silently again.
Doctrine for Dr. DNicole Fields, Ed.D. | Integral Exploration Development Group, LLC
Each disease has a name, a symptom, a root cause, an evidence trail from this session, and the antibody that catches it. We name them so they cannot fire silently. We log them so we can grep them. We carry them in every pre-flight. The original 7 (D1 through D7) plus the 3 newer pathogens (R-014, R-015, R-016) surfaced on May 28 to 29.
Which gate catches which disease. A lit cell means the gate, by design, blocks the disease before it ships. A dark cell means the gate is not the primary catch for that pathogen, and the hygiene layer carries it instead.
| Disease | G1Pre-flight Audit | G2Triad Verifier | G3Regression Scan | G4Topic-Native Check |
|---|---|---|---|---|
| D1Inherited-Default Blindness | ||||
| D2Doc / Email / Code Drift | ||||
| D3Pattern-Not-Instance Failure | ||||
| D4Corpus Sampling Bias | ||||
| D5Nexus-Transplant Reflex | ||||
| D6Silent-Regression Ride | ||||
| D7Stochastic-Gate-As-Truth | ||||
| D8Generator-Embedded Metadata at Rest | ||||
| D9Structural Paraphrase on Mirror | ||||
| D10Ledger Deploy Drift (local vs live) | ||||
| D11Static Verification Misses Live Contract | ||||
| D12Schedule-Date Default Drift |
Newer pathogens (R-014 through R-018)
Surfaced May 28 to 29 from the Notion calendar audit, the CD mirror confession, and the 27-day ledger deploy gap. D8 and D10 are caught by G2 Triad Verifier (extended with the persistence canary and md5 local-vs-live diff). D8 also auto-elevates via G3 because the same R-011 pre-send strip pattern fires the at-rest leak. D9 is caught by G1 pre-flight Q6 (state K of N for the corpus you mirrored) and by G2 because the source-to-mirror diff is a structural triad: source structure must equal rendered structure must equal downstream-consumer structure.
Each gate is a hard checkpoint. It runs automatically where possible, and is invoked explicitly by the operator where not. A gate that does not block is not a gate. A gate that fires after the email goes out is not an immune response.
The moment-by-moment kill chain of the trust incident plus the two follow-on incidents (calendar source pollution on May 28 and the local-vs-live HTML deploy gap caught May 29). Each event names the pathogen that caused it and the gate that would have caught it. The bottom of the chain is the recovery: where the doctrine was authored, the antibodies issued, and the newer R-014, R-015, R-016 pathogens appended.
The gates catch named pathogens. The hygiene rules raise the baseline so new pathogens have a harder time finding a foothold. Hygiene is universal: it applies to every task, every client, every artifact.
Never speak about a corpus you have not fully read. If you sampled, state the sample size and the population size in the same breath. The reader gets to weight the claim accordingly.
if read < total: prefix report with "viewed N of M"Every centerpiece in a non-source doc must be designed for the topic. The Nexus Proposal's Flywheel, ELCC orbital, and Pipeline ribbon are source-native to the Proposal, not to anything else.
grep doc for transplant signatures; BLOCK on matchAny Claude or LLM gate that decides PASS or BLOCK is run twice, scores averaged, decision taken on the average. If the two scores differ by more than 4 points, the gate is flagged and escalates to a human.
score = avg(call_a, call_b); if |delta| > 4: escalateThe three layers are bound to a single source of truth. Drift between any two of them is a deploy block, not a follow-up task. The triad verifier runs daily, on commit, and on pre-ship.
deploy_ok = (doc == email == code); else BLOCKA request enters the system. It traverses four immune checkpoints in order. Any checkpoint may block. Only a clean traversal earns GREENLIGHT.
Same setup. Same architecture claim. Same time-of-day. On the left, the disease ships and Dr. DNicole gets a watermarked-image email at 06:55. On the right, the Triad Verifier catches the drift, the request is blocked, the fix is applied, no client harm.
openai_generate().triad_status cron. Code does not match. Status flips to drift.shutterstock_first(). Triad reconciles to agree.This document is not a postmortem. It is a contract. From this point forward, every other IEXDG doc links here. Every pre-flight is mandatory. The regression registry is read before any touch. The triad runs nightly.