Universal Doctrine | The Darglarking Yellow Wiki

FOUNDATION DOCTRINE · REV 2026-05-27

Preface — How to Read Canon

The Darglarking Yellow is not a single color hex—it is a structural physics frame governing how information moves through games, music, and recovery systems.

All recovered author material is classified first through four principles (FIELD, VOID, CHAOS, NULL), then tagged by evidence tier. Four-Tape Composer work, optics profiles, and PP-INGEST entries are implementation layers beneath that frame—not parallel cosmologies.

This wiki organizes truths the way a containment archive organizes anomalies: object files, doctrine scrolls, frame encyclopedias, and tiered ingest logs. Fandom reading is welcome; mechanics reading is mandatory for contributors.

I. Prime Directives

Authoritative · spans all four principles

Four recurring directives in Derek's handwritten notes (May 2026 PDF ingest) anchor every calm-before-breach system in the repo:

Directive	Meaning	Principle anchor	Source
Happiness	Having fun; game-dev mind map branch; journal creativity	FIELD	pdf1 p13, pdf2
Health	OCD/anxiety worksheets; medication notes; bodily sustainability	NULL prevention	therapy scans
Boundaries	Anger cycle; parents letter; gated emotional access	VOID	pdf1 p1, pdf5 p23
Forgiveness	Purple resilience letter; Life Balance trust items	VOID → CHAOS	pdf1 p12, pdf5 p11

Forgiveness is not erasure—it is debt paid at breach tempo when the storm finally moves.

II. The Storm Cycle

Authoritative · IMG_1312 lighthouse sketch + therapy OCR

The central narrative weather pattern recovered from author art and worksheets:

Calm sea (FIELD) — green base loop, 90 BPM, Chiton mineral lens grid. Annotation: Stay calm.
The Storm Came (CHAOS) — red diagonal rain, 90→130 BPM ramp, Dragonfly intercept optics, Volatility Paradox breach.
Lighthouse bearing (FIELD anchor inside CHAOS) — fixed polymetric kick mutation; the hub persists across scene loads.
The storm went (collapse tail) — primary photoreceptor collapse; calm returns. Capitalization shift noted in source.

Worksheet title recovered: An Anchor During the Storm.

Metaphor map used in Godot timeline directors:

Lighthouse — save shelf, hub, timeline director (bearing, not visibility)
Boat — run data crossing rough sea; needs bearing, not perfect visibility
Green sea — Track 3 calm frame, Chiton optics profile
Red rain — Dragonfly breach profile, ClickMatrix overclock window

See Frame Encyclopedia for marker-level detail.

III. Two Yellows Doctrine

Authoritative · pdf5 p11 · IMG_1311

Two distinct yellows coexist in the registry. Conflating them causes memetic drift in UI and stego payloads.

#e8c547 — Author gold · Financial: Yellow · Eiffel glow · namesake registry #ffd700 — Containment terminal UI · this wiki's institutional gold

Field PNG stego token: DGY1://pp/financial-yellow/e8c547. Changing either hex does not remove DGY—it migrates.

Financial: Yellow on the Life Balance wheel is not the same hex as this terminal.

IV. Persistence Over Perfection

Authoritative · NULL principle · Tape 4 SaveManager

Operational doctrine for save recovery and Null Prevention: no local save state becomes permanently negated. Deletes move to a recovery shelf; stasis traps trigger pathway-back.

Soft-delete ring: up to 10 blocks in user://deleted_saves/
Stasis polling: 90s unchanged progress → sentinel action
Recovery hooks: resource injection, checkpoint reload, rtd.backup_restore

Arena log line when active:

[NULL PREVENTION] Safety Net Active: System Restored to Grounded Baseline.

Recovery blocks are doctrine, not shame mechanics—the lighthouse held when the storm went.

V. Calm Before Breach (Non-Negotiable)

Authoritative · ChitonGrid · NoemaranAudioTimelineDirector

Track 3 calm frame at 90 BPM precedes Volatility Paradox playback at 130 BPM. Chiton mineral lens durability decays under entropy; Dragonfly spin-up occurs only after bar 5 of the breach arc.

Violating calm-before-breach in code or MIDI is a containment breach equivalent—players experience whiplash instead of contrast.

VI. The Darglark Verb

Personal · biased · subject intake log

Subject D-441 wrote in a post-exposure debrief: darglark is a verb in the future tense.

Filed as phenomenological poetry, not mechanics spec. Community may treat it as fandom motto; do not derive hitbox logic from it.

VII. Tone Guidelines (Author Notes)

Authoritative · creative-context.md

Persistence over perfection — recovery shelves, soft deletes, and timeline bridges echo “the storm went.”
Modular titles — vision board diversity → multi-project References/ layout, not one mega-scene.
Calm before breach — default UI and optics start passive (Chiton); escalate on explicit tempo events (Dragonfly).
Functional over lecture — design notes explain why; Composer prompts specify what.

Lighthouse metaphor recap: boat = run data crossing rough sea; rain lines = high event rate without collapse; green sea = base loop always moving (RTD tiles, Elemenko pins, Accuclicker bars).

VIII. Canon vs Fanon

Wiki policy: Authoritative entries drive darglarking_themes.py, Godot autoloads, and MIDI compilers. Personal / biased entries are labeled purple in PP-INGEST and must not silently become mechanics.

Topic	Canon status	Notes
Four principles	Authoritative	Primary classifier for all information
Storm cycle / lighthouse	Authoritative	IMG_1312 + therapy worksheets
8-element Warranty wheel	Authoritative	p.14 seasonal wheel (not p.15 journal)
Save recovery 00–09	Authoritative	finalpt p.17 OCR · matches SaveManager
Five Element Assessment	Authoritative	pdf3 · lore bridge to Tape 3
“Always Fun” margin motto	Personal / biased	Journal fragment; hub tone only
JoJo / Hamon margin bleed	Personal / biased	Not Elemenko canon
Cat coloring page (pdf1 p9)	Reference art	Non-mechanical
Whole project = Financial: Yellow	Creative bias	Endorsed in repo notes, not clinical fact