How the entire class connects into a collective intelligence network — and what serendipity looks like when it works.
The Trinity Graph is not a tool. It is a biological operating system layered over the entire cohort. Think of every student as a node. Every conversation, every project, every connection is an edge. The graph is the living map of the class's collective intelligence — and the serendipity engine is the algorithm that traverses it to surface connections nobody would have found on their own.
There are three layers. They are not separate products. They are the same system at three different levels of abstraction.
Every domain, skill, market, dataset, and insight each student carries. Triples: Entity → Relationship → Entity. Nashville R1 → requires → 5ft setback. Healthcare → regulated by → FDA.
The layer that traverses both graphs to produce something new. A feasibility score. A warm intro path. A market hypothesis. The output no individual could have generated alone.
The emergent layer. When the algorithm finds a connection between two nodes that nobody programmed, nobody anticipated, and nobody would have found through normal networking. This is the prize.
Every student's individual knowledge graph feeds into the collective. Here are the node types that exist across the cohort map.
Name, background, archetype (Connector, Builder, etc.), Kirk Step, spirit animal. The base identity node.
First-degree connections each student contributes. GC uncle, title insurance contact, city planner friend. These are the edges that bridge structural holes.
What each student actually knows. Supply chain, regulatory compliance, data science, sales. Weighted by depth (novice → expert).
The domains each venture operates in. PropTech, Healthcare, FinTech, Art. Connects ventures to relevant student expertise automatically.
Each pod's startup. BackyardOne, Artiquity, Enginuity, Aura Health, Ubiquity. The unit that the whole graph is trying to serve.
A customer discovery finding, a validated hypothesis, a market signal. These are the artifacts that emerge from pod interviews and feed back into the graph.
A detected gap between two clusters. The system flags these automatically. "BackyardOne needs regulatory expertise. MBA-3 has it but is on the Artiquity pod."
A surfaced connection that was unexpected. A cross-pod insight. A warm intro nobody knew existed. The graph's highest-value output.
Serendipity in a recommender system means surfacing connections that are unexpected but relevant — not random noise, not obvious matches. The serendipity engine is what separates the Trinity Graph from a CRM or a LinkedIn graph.
Not just stated preferences. The system infers latent interests from project choices, collaboration patterns, and conversation data. A student who says "fintech" but keeps asking questions about regulatory arbitrage has a latent interest in policy.
The algorithm scans for gaps between venture clusters. BackyardOne needs healthcare-adjacent regulatory experience? The graph checks every student across all pods, not just the BackyardOne team.
Each potential connection gets a score: how unexpected is it (novelty) × how relevant is it (utility). Score too low = boring and obvious. Score too high = random noise. The sweet spot is high novelty + high relevance.
The engine doesn't email you a list. It surfaces the connection at the right moment — during a relevant conversation, before a session where cross-pod collaboration would be valuable, or when a venture hits a specific kind of wall.
If the connection was acted on — a collaboration happened, a warm intro was made — the graph records the edge with weight. Over time, this teaches the serendipity engine which patterns generate real value vs. false positives.
Artiquity needs blockchain provenance expertise. The graph detects that a BackyardOne MBA has prior experience with property title chains on distributed ledgers. VanderBot surfaces the connection before Demo Day. Neither pod knew this existed.
BackyardOne needs access to Nashville zoning officials. The graph finds that an Ubiquity pod member's family member works in Metro Planning. Three degrees of separation → one warm intro. CAC = $0.
Three different pods, doing customer discovery in completely different markets, all independently hear the same friction point: "the permit process is broken." The graph aggregates these signals and flags it as a cross-market structural hole worth investigating.
Enginuity's pod is all Builders. They are technically excellent but stuck on go-to-market. The graph detects that Adele (The Connector) has solved a structurally similar GTM problem. VanderBot suggests a 20-minute cross-pod session.
Your pod is a micro-instance of the Trinity Graph. Adele is the Brain (topology). The 4 MBAs are the Membrane (sensory organ). The graph is the infrastructure that makes their outbound energy compound rather than evaporate.
Systems Architect
Customer Discovery
Network Seeding
Market Validation
Network Seeding
Each MBA is a node contributing their warm network edges to the graph. When they feed contacts back to Adele, those nodes get wired in. The graph grows. The serendipity engine has more to work with. The pod's collective reach expands exponentially.
The Trinity Graph is designed to get more powerful as more nodes and edges enter the system. Here is the scaling arc across the course:
Each student enters the graph as a node. Basic attributes: archetype, background, Kirk Step. VanderBot begins learning each student's individual knowledge graph through conversation.
Each pod builds their 100-triple Knowledge Graph. These triples get ingested into the collective system. Now the graph knows not just WHO each student is but WHAT they know.
The serendipity engine begins running cross-graph traversal. The system starts detecting structural holes across pods. VanderBot surfaces the first unexpected cross-pod connections. The graph starts generating value it was not explicitly programmed to generate.
The Laptop Drop is the first moment the entire class can see the collective graph. All five Inkwell ventures mapped. All warm networks visible. All structural holes identified. The serendipity engine goes live across the full cohort.
By Demo Day, the graph has ingested weeks of customer discovery, cross-pod collaboration, and real market signals. Each venture's pitch is no longer just a slide deck — it is a node in a living network that can demonstrate compounding value in real time.
When the Trinity Graph is fully operational across the cohort, this is what becomes possible:
Every customer discovery interview, every investor conversation, every advisor relationship starts with a warm intro traced through the cohort's collective warm network graph. Zero cold outreach for any pod.
Every customer interview, market signal, and validated hypothesis gets written back into the graph as a node. Nothing lives in a Google Doc or a forgotten Slack thread. The cohort's collective intelligence is permanently accessible and queryable.
The cross-graph traversal surfaces a market opportunity that nobody was explicitly looking for — a structural hole visible only when two pods' customer discovery data is analyzed together. A new venture is born from the graph's output, not from a founder's isolated idea.
Metcalfe's Law: network value = N². Each new node (student, contact, insight) added to the graph increases the total value for every other node. By Demo Day, the graph is worth more than the sum of its parts. That is the organism.