TRINITY GRAPH
Product Specification · v0.1 · Compiled March 2026
Executive Summary: The Trinity Graph is a personal world model — a force-directed knowledge graph where every node is something real: a person, an event, a constraint, an idea, or a hypothesis. It maps the topology of your reality and makes that topology queryable and visually alive.
1. Product Definition
1.1 What it is
- A live biological map of who, what, and what-if in your world
- A signal-extraction tool: turns messy field notes into structured graph data
- A decay system: relationships visually fade if not tended
- A hypothesis engine: collisions between nodes generate WHAT IF cards
1.2 The Biological Metaphor
Networks are not like biology — they are biology. (Oliver Luckett, The Social Organism)
- Cell = Node (WHO / WHAT / WHAT IF)
- Synapse / membrane = Edge with label, strength, ATP state
- Decay / apoptosis = Tie strength fades to dotted line at 90 days
- Horizontal gene transfer = WHAT IF generated by WHO x WHAT collision
2. Data Model
2.1 The Trinity Ontology
WHO (Actors): Entities with agency. Fields: vector, superpower, keys, is_bridge_node.WHAT (Ground Truth): Physical/structural reality. Fields: verification_status, date_discovered.WHAT IF (Hypotheses): Output of collisions. Fields: origin_edge, the_test, kill_criteria.
2.2 Boundary Rules
- Rule of Time: start + end timestamp = Situation. Persistent reality = Constraint.
- Rule of Communities: outside trying to get in = WHO. Inside sharing resources = WHAT.
- Rule of Emotional Weight: Lives on the EDGE, not the node.
- Rule of Self: Adele is always the central SELF node. ATP state only applies to SELF edges.
3. Interface & UX
3.1 Zero-Friction Capture (Quick Log)
Trigger: click any edge or WHO node. UI: single large text area — no date pickers, no dropdowns. Four emoji buttons for ATP (Energizing, Draining, Conflicted, Neutral). Appends Atomic Interaction Object.
3.2 Context Drawer
Slides in from the right when an edge is clicked. Keeps the main graph clean. Shows timeline of atomic log_notes[]. Never loads full chat logs.
4. Design Principles
- Blood inside the bones: The graph is the skeleton. Conversation logs are the bloodstream.
- You are the membrane: Only you know if an interaction generated a WHAT IF.
- Zero-friction or death: If logging takes more than 5 seconds the biological graph dies.
- Apoptosis is healthy: Dormant edges are not failures — they are data.