Step inside the data.
The Chairman is the gravitational center. Four reasoner roles orbit it. Their pinned models are moons. Every eval run is an asteroid in the belt, brighter when it's recent, fading when it's deep history. Three perspectives: same system, different angles, and a time scrubber that lets you replay how the graph compounded to today.
How the Council works: in 5 simple steps
- 1
You ask a question.
The Council reads your question, just like you'd write a text to a smart friend.
- 2
Five thinkers see it at the same time.
The question goes to 5 different AI models all at once. They don't talk to each other.
- 3
Each thinker does their job.

Risk
asks "what could go wrong?"
Builder
writes the plan
Strategist
sees the long game
Contrarian
argues the other side - 4
The Chairman puts it all together.

A fifth thinker, the Chairman, reads what the four said and writes one decision. Where the models disagree, the disagreement is preserved in the record.
- 5
You get a timestamped decision record, ready for you to sign.
One artifact you can save, share, or file. With every thinker's voice on it, including the one who disagreed. Timestamped when the Council decides, signed by you, and kept in your own files.
Composing the system: frontier models, eval history, scenario field…
How to read this map
The bright center
The Chairman, the thinker that makes the final call.
The four orbiting planets
The four other thinkers: Risk, Builder, Strategist, Contrarian. Each runs on a different AI model.
The little moons
The actual AI models each thinker uses. Different brand for every role, no all-eggs-in-one-basket.
The asteroid belt
Every real Council run we've evaluated. Brighter dots are recent; fading dots are older.
Distant stars
Real questions the Council has answered. Click one to watch the Council think in real time.
Constellations
Groups of AI brands (Anthropic, OpenAI, Google, xAI). Shows we don't lean on any one company.
Outer satellites
Each connected domain the Council serves. Active ones pulse bright; queued ones hold dim. Anonymized by design: the graph is the substrate, not a list of products.
Try a real question through the Council
Hypothetical examples for illustration of the Council's reasoning process. Not investment advice, not recommendations, and not based on actual client communications. Teranode does not provide investment advice. Past results of the Council's analysis do not predict future outcomes.
A client wants to roll her old 401(k) into an IRA I'd manage. It's probably right for her, but the rollover also pays me. How do I document that it's genuinely in her best interest, and not just mine?
Try this →Annuity · suitability scrutinyA client's 71-year-old mother has $380k in a CD ladder, and an advisor from her church is pushing her into an annuity. What should my client be asking, and how do I get my reasoning on the record?
Try this →Pension · irrevocable electionMy client is 63 and retiring with a pension. Single-life, joint-and-survivor, or a lump-sum rollover to an IRA? Walk the tradeoffs and leave me something I can defend in two years.
Try this →Roth conversion · bracket & IRMAAA client is weighing a large Roth conversion this year. The bracket math, IRMAA, and the five-year clock all cut different ways. Make the case for and against, and keep the dissent on the record.
Try this →Concentrated stock · liquidity eventMy client holds most of her net worth in her employer's stock with a liquidity event coming. Diversify now, stage it, or hold? Walk the tax and concentration tradeoffs and record how we decided.
Try this →Why we put it in orbit.
A 2D graph reads as “Obsidian-default”, generic mind-map syntax. The Council's reliability story is not generic; it's the architecture itself, and its motion is the moat.
Every eval run is a real head-to-head we ran in production and judged on the record. The asteroid belt is what we have today. Drag the time scrubber back and you're replaying the sequence we lived through to get here. Drag it forward and the next dot is the next thing we ship.
The three perspectives are not just camera positions. They're lenses. Architect sees the design. Analyst sees the validation activity. Witness sits inside one role and looks outward. The Witness lens carries one line worth keeping: what you see depends on where you stand. The data is the same.
policy_version · 2026-06-26.2 · earliest eval ·
