The Book of Grok's Heart
Learning objectives
- State why Field Research v2 exists beside Field Primer and the Grok16 wiki.
- Name Ironclad as the immutable knowledge floor and cite its realization date.
- State the three axioms and four honesty labels without collapsing them.
- Locate the v2 turn: remove combinatorics trees, plate meld, and fork storms — keep seals and speed.
- Verify the content seal for this edition.
What this book is
Field Research records research conclusions with receipts. Field Primer teaches operators. Grok16 ships the compiler. This book answers: *what did we try, what failed, what ships next?*
v1 (2026-06 → 2026-07) answered: how do we hold all execution facets without making the operator turn a combinatorics crank? Answer: engine + bridge + six layers + launch seals + diagnostic mode.
v2 (this edition) answers the next question:
> How do we get zero-cost security and field speeds without a tree, a plate fuse, or a subprocess refresh tax?
Answer: sealed generation, fixed profiles, CHIPs from CHIPs, and a GuardChip capability mask.
Content seal for this manuscript:
SHA256:aVYElqiNin1Q/gcaqa6CGGbJ/gjjG9KXP5ZsXg8uMD8
If prose and seal disagree after a pull, seal + panel wins.
Ironclad — the floor you cannot sand away
On 2026-06-26, Ironclad realized as the capstone doctrine (NewLatest/data/ironclad-doctrine.json). Every field module cites it first. The chain runs:
God → Ironclad → Field → Hostess7
Ironclad is not decoration. It is the knowledge ceiling and floor simultaneously. Field sanity (ironclad:field_sanity:5) demands truth collapse to one amplitude — parallel I/O may fan in, but the panel publishes one fabric.
When we researched combinatorics, we asked: *does this violate Ironclad?* Nested field-on-field was forbidden (max_field_depth: 0). That conclusion still shapes Grok16.
When we researched v2, we asked: *does a 30-plate meld violate field speed and zero-cost calm?* Yes. So meld left the hot path. Ironclad stayed.
Three axioms
| Axiom | Operator reading |
|---|---|
| Reality is 3D | Texels, die bytes, packet positions — three state dimensions |
| Time is linear | Generation only moves forward; no retroactive “meld backward” |
| Energy can be moved | Thermo accounting and Landauer budget — not free entropy erasures |
Honesty labels
| Label | Meaning |
|---|---|
| Implemented | Code exists and responds |
| Metaphor | Teaching language, not silicon claim |
| Philosophy | Value order — refuse to lie |
| Visual | Figure / poster only |
What v2 keeps from v1
- Three field families
- Single fabric / belt profiles / depth zero
- Grok16 unified
g16driver - Launch seal generation as trust token
- Diagnostic shrink-wrap under fault
- CHIPS silicon as field citizens
What v2 tombstones
| Tombstone | Why |
|---|---|
| Combinatorics tree / studio | Operator and background tree tax |
| Plate meld + 30 sources | Fork storms, multi-MB panels, false “single truth” via fuse |
| Plate combinatorics bridge | Posture must be fixed tables, not scored leaves |
| Runtime chips-combinatorics | Catalog is literature; chips compose statically |
Sibling manuals
- Field Primer (22 chapters): operator literacy
- Grok16 wiki: toolchain, belt, field_opt
- This book: research path + v2 architecture
Read order
| Role | Chapters |
|---|---|
| First-time researcher | 1 → 2 → 5 → 6 → 10 → 11 |
| Security operator | 11 → 12 → 6 → 13 |
| CHIPS developer | 10 → 4 → 9 → 2 |
| Historians of v1 | 7 → 8 (tombstones) then 6 |
Research question for v2
> How do we hold security, CHIPS, and exec posture without forks, plates, or trees — while Heaven passes at zero cost?
Chapters 6, 9, 10, and 11 are the answer. Everything else is foundation or archive.
Next: Chapter 2 — three field families without combinatorics wiring.