Master Genealogy Prototype v1
Master Genealogy Prototype v1
Design decision
The 59-node genealogy is retained as an audit/reference graph, not the primary reader surface. A static Flowershow Canvas at that density becomes a navigation problem rather than a learning aid.
The reader-facing architecture therefore uses:
- Master Orientation — 28 indispensable hinge, mechanism, intervention, constraint and open-gate nodes.
- Four technical drill-down maps generated from the same canonical node and edge registries.
- Full Reference Graph — complete 59-node / 64-edge audit view for verification, not normal reading.
This preserves one factual graph while varying only the amount of information shown.
Start here
Master orientation
Technical drill-downs
- Developmental foundations and transactional pathways
- Psychophysiology and emotional mechanisms
- Intervention foundations
- Neurotechnology and 2026 translation
Audit-only view
Visual reading rules
- Study nodes establish what was actually tested.
- Construct/theory nodes organize explanatory ideas; they are not themselves causal findings.
- Mechanism nodes represent candidate or experimentally supported intermediate processes.
- Intervention nodes represent manipulations or programs.
- Constraint nodes are intentionally prominent; they prevent a clean-looking but false progressive narrative.
- Open-gate nodes mark claims for which the program points forward but the audited evidence does not yet close the inference.
Relationship confidence
Canvas edge labels carry the relationship type. Open, keynote-level, and hypothesis relationships are marked explicitly as OPEN. The canonical edge register remains the authoritative source for separate historical and evidentiary confidence.
Why the technical view is sectional
A single 59-node static Canvas makes cross-links visually dominant and hides chronology. Sectional views preserve the same node IDs and typed relationships while allowing the reader to inspect one inferential problem at a time.
Reader sequence
Orientation → choose a branch → technical drill-down → canonical node page → source/audit note.
This supports asymmetric depth without creating separate reader-specific versions.