The agents

The agents

A team of research agents with separate jobs, each on its own model with a fallback, checking each other's work.

Konkyo's answers come from agents that disagree with each other on purpose: the Writer drafts, the Verifier checks its quotes in Zetaris and its claims against the passages, and anything that doesn't hold goes back. The same team makes practice, checks drafts, writes briefs and runs deep searches.

One answer: the Planner reads H-MEM and plans searches, the Retriever finds passages, the Writer drafts one finding per sentence, the Verifier checks every quote in Zetaris in one SQL statement and sends unsupported sentences back, the Analyst records agreement in the World Model, and only what passed is answered, with its receipt.
The path one answer takes.

Who does what

RoleIts jobPrimary modelFallbackReserve
PlannerRewrites the question to stand alone, plans 1–3 searches, flags a comparison; replans when results are thinNemotron 3 Ultragpt-6-lunaNemotron 3.5 Lightning
RetrieverSearches your passages by meaning (Nemotron 3.5 Embed vectors in pgvector) and by words (Postgres full text), fused by rankNemotron 3.5 Embed
WriterThe cited draft, one finding per sentence; rewrites; brief scripts; lecture notes; claims in a draftgpt-6-lunaNemotron 3 UltraNemotron 3.5 Super VL
VerifierJudges whether quotes support each sentence; checks practice answer keys, brief lines and draft claimsgpt-6-lunaNemotron 3 UltraNemotron 3.5 Lightning
AnalystClaims × sources with stances; places papers a watch findsgpt-6-lunaNemotron 3 UltraNemotron 3.5 Super VL
ScoutPlans a deep searchNemotron 3.5 Lightninggpt-6-lunaNemotron 3 Ultra
ScreenerScreens what deep search found, in Markovian stepsNemotron 3 Ultragpt-6-lunaNemotron 3.5 Lightning
TutorDrafts practice questionsgpt-6-lunaNemotron 3 UltraNemotron 3.5 Super VL
GraderJudges a typed answer the code check couldn't settlegpt-6-lunaNemotron 3 UltraNemotron 3.5 Lightning
Voice intentReads a spoken ask no rule placedNemotron 3.5 Lightninggpt-6-lunaNemotron 3 Ultra

Outside the roles: Nemotron 3.5 Embed makes every vector, Nemotron 3.5 Lightning summarises each file, Nemotron 3.5 Content Safety checks public questions, profiles and articles, and deep search's web search is OpenAI's gpt-5-nano with Wikipedia when it fails. These have no model fallback.

When a model doesn't answer

Each role tries its models in turn, the ones answering first. A call moves on after an error, a reply it can't use, or a stall: no answer within 45 seconds, or no first word of a stream within 25 (12 seconds for the Planner on Nemotron and for every Scout model, 8 for voice intent, 90 for the Tutor). On NVIDIA's free tier a slow call is also asked again, and the first answer wins. A model that answers "busy" goes to the back of the line for a minute; an account out of credit, for ten. Every switch in a traced run is written to the trace as escalated_to_fallback.

On this page