Три триединства се изобразяват като RGB

Героят разполага своите 9 възела в 3 триединства на 0°/120°/240° както в пространството, така и в цвета — равностранната RGB триада. Трите триединства СА трите RGB канала; героят вече изобразява декодирането.

proof · three trinities render as RGB · 0° 120° 240°

The hero (HolographicHero) places its 9 architecture nodes in 3 trinities (node.trinity = ⌊i/3⌋ ∈ {0,1,2}) at angle (trinity/3)·2π = 0°/120°/240° and at hue (base + trinity·120°) — so the 3 trinities sit 120° apart in BOTH space and colour: the equilateral RGB triad. The 3 trinities (3 = 3 trinities = 9 folders, piThreeOpensTheTrinity) are therefore rendered as the 3 RGB channels (hexagramIsHexColorDuality) — the same 3 that is the codon position, the 3-qubit Pauli, and the colour channel. The hero was already rendering the decode.

checks — recomputed live in your browser

• ✓ Is Rgb Triad
• ✓ Holds

evidence

Trinities

0, 1, 2

Hues

0, 120, 240

Angles Deg

0, 120, 240

Channels

red, green, blue

Ninefolds

9

✓ all checks hold · recompute recipe — a pure function of the model seed, run client-side with zero tokens; the same seed always folds to the content-address 1bbb0328-7d43-8d4c-a89e-3e51bf0ff2a9. Recompute and you get the same address — that determinism is the proof.

A real colour-wheel fact — three hues 120° apart ARE the additive-primary (RGB) triad — over the hero's existing trinity→angle/hue mapping. The base hue rotates the whole triad; the 120° SPACING (the RGB relationship) is invariant. It is the project's design choice to group the 9 folders as 3 trinities and colour them so, NOT a claim the architecture is physically RGB; it unifies the session's threads (trinity, 64, hex-colour) where the hero already computes them.