What is the model actually doing?
Start with tokens, context, and the limits of evidence.
OPTIVERSE SYSTEMS JOURNAL
A field guide for people who want to understand, build, and run AI systems. Follow the evidence, experiment with the diagrams, and learn where systems succeed—or fail.
Start with tokens, context, and the limits of evidence.
Connect evidence, validation, permissions, and recovery.
Explore scheduling, KV memory, and GPU placement.
Ordered by prerequisites. Routes share some foundation guides.
THE LIBRARY
Explanations, interactive diagrams, and exercises in every guide. Explore a topic or follow the reading route.
25 guides
Suggested order within each topicUnderstand what models predict, what context can hold, and where evidence and permissions matter.
Follow a prompt from tokens to predictions, and learn what a fluent answer can—and cannot—establish.
Build a clear request, budget its context, and handle missing information before asking for an answer.
Separate missing evidence, stale knowledge, retrieval errors, and unsupported claims so you can choose the right control.
Turn a proposed tool call into a bounded operation with explicit permissions, approval, and recovery.
Give each component a clear responsibility. Validate outputs, manage state, and recover safely.
Map the responsibilities of models, tools, data, and application code before connecting them into a system.
Design stage contracts that catch malformed data, unsupported interpretations, and broken business rules.
Give conversation context, task state, evidence, and durable records clear owners and lifetimes.
Choose where a model may decide, which tools it may use, and which actions still require human review.
Build a versioned evaluation set and a regression gate that can reveal where a system starts to fail.
Keep delegated authority and approval outside model-generated text, and test the boundary with adversarial inputs.
Bound a tool loop, distinguish failure from uncertainty, and recover without duplicating external effects.
Find relevant sources, reconstruct documents, and connect each answer to evidence you can inspect.
Retrieve permitted evidence, preserve its sources, and evaluate retrieval separately from the final answer.
Combine lexical and dense rankings, then assemble a bounded evidence packet with explicit freshness rules.
Reconstruct reading order, tables, and source relationships so a document becomes traceable evidence.
Connect visual claims to source pages and regions, and recognize what an image cannot establish.
Bring the parts together in support and travel workflows with explicit boundaries and failure cases.
Resolve a support case with evidence, account permissions, clear escalation, and verified outcomes.
Bring evidence, state, approvals, and recovery together in an inspectable travel-planning system.
Follow a request through scheduling, memory, and GPU placement. Measure capacity under real constraints.
Trace a request through prefill, decode, caching, and streaming—and reconcile its timing and memory costs.
Explore token-budget scheduling, chunked prefill, preemption, and backpressure in a small runnable simulation.
Calculate memory per token, allocate complete blocks, and distinguish snapshot capacity from room to finish.
Compare data, tensor, pipeline, and context parallelism using memory, communication, and failure boundaries.
Balance prefix reuse against queue load, compatibility, and tenant isolation when routing inference requests.
Decide when phase separation is worth the cost of KV transfer, extra coordination, and a more complex deployment.
Separate model routing from expert placement, and calculate the memory and communication each layout needs.
Measure useful capacity with a frozen workload, per-class latency goals, queue evidence, and failure tests.
No guides match. Try another keyword, or clear your filters to start again.
THE BIGGER PICTURE
Each concept links to the knowledge it builds on. For a step-by-step sequence, use the complete reading route.
You can start here.
Read this guide ↗