šŸ•øļø Architecture

Graph Architecture

The propose-verify-select cycle forms a reasoning graph — a structured record of how Turbo thinks, proves, and decides.

Propose → Verify → Select as a Graph

Every Turbo query creates a directed acyclic graph (DAG) of reasoning. The prompt node fans out to candidate nodes, each connected to a verification node, which feeds into a scoring node. The best-scored candidate is selected as the final answer.

šŸ’¬ Prompt
🧠 Cand. A
t=0.3
🧠 Cand. B
t=0.6
🧠 Cand. C
t=0.9
šŸ”¬ Verify A
āœ… pass
šŸ”¬ Verify B
āœ… pass
šŸ”¬ Verify C
āŒ fail
šŸ“Š 0.96
šŸ“Š 0.87
šŸ“Š 0.38
āœ… Selected
Answer

Graph Node Types

The reasoning graph consists of five types of nodes, each representing a distinct phase of the Turbo pipeline:

// Graph node types const NodeTypes = { PROMPT: 'prompt', // User's question — root node CANDIDATE: 'candidate', // Generated answer at temperature T VERIFICATION: 'verification', // Test code + execution result SCORE: 'score', // Fuzzy predicate scores SELECTED: 'selected', // Final chosen answer — leaf node }; // Edge types const EdgeTypes = { GENERATES: 'generates', // Prompt → Candidate VERIFIES: 'verifies', // Candidate → Verification SCORES: 'scores', // Verification → Score SELECTS: 'selects', // Score → Selected CONTEXT: 'context', // Previous Selected → New Prompt };

The Graph Grows Over Time

Each query adds a new sub-graph to the overall reasoning graph. The selected answer from one query becomes context for the next, creating a knowledge chain:

// Multi-query graph growth Query 1: "What is 47 Ɨ 83?" └─ Candidates → Verify → Score → Selected: 3901 Query 2: "Now divide that by 7" ←── context: 3901 └─ Candidates → Verify → Score → Selected: 557.28... Query 3: "Round to nearest integer" ←── context: 557.28 └─ Candidates → Verify → Score → Selected: 557 // The graph now has 3 linked sub-graphs // Total nodes: 3 prompts + 9 candidates + 9 verifications // + 9 scores + 3 selected = 33 nodes

This graph structure provides a complete audit trail of every decision. You can trace back through the graph to see exactly why any answer was selected, what alternatives were considered, and what verification evidence exists.

Graphs vs Linear Chains

āŒ Linear Chain (Standard AI)
Prompt → Answer → Prompt → Answer

Single path. No alternatives explored. No verification. Error in one step propagates to all subsequent steps. No way to backtrack or audit.

āœ… Reasoning Graph (Turbo)
P ⟶ C₁ Cā‚‚ Cā‚ƒ ⟶ V₁ Vā‚‚ Vā‚ƒ ⟶ āœ…

Multiple paths explored simultaneously. Each verified independently. Errors caught and filtered. Full audit trail. Knowledge compounds across queries.

Relation to Knowledge Graphs

Turbo's reasoning graph shares principles with knowledge graphs used in modern AI systems:

šŸ”® Future Direction

The Mikoshi team is researching cross-session graph persistence — where verified knowledge from previous sessions can be reused without re-verification. Imagine: ask a question once, prove the answer, and never need to re-derive it. This is the foundation for truly cumulative AI intelligence.

See the reasoning graph in action

⚔ Try Turbo in Synapse