Fair Questions, Answered on the Landing Page
A new FAQ section answers the questions people actually ask about context-v: token cost, drift, regenerable code, and agents drowning in context.
- Path
- changelog/2026-10-07_01.md
- Authors
- Michael Staton
- Augmented with
- Claude Code on Claude Opus 5.5
- Tags
- Context-Vigilance · Splash · FAQ
Why Care?
People who look at context-v closely tend to ask the same sharp questions. The answers lived in conversations; now they're on the landing page , in our own words, including where we're unsure.
What's New?
A "Fair questions" section sits between The Patterns and The Invitation, as collapsible items:
-
Doesn't all that context overload the context window? Not for us: nothing is autoloaded. Context reaches the agent by being pointed at (a handoff or specific docs), found by its own scans, mapped by Graphify output in our more complex repos, or queried from the Chroma-backed corpus over MCP.
-
Without hard checks, how do the docs stay true? They drift a little, and that's fine. Date fields keep stale docs out of the way, Reflect brings the docs a cycle used back in line, and we're trying a
mirrors/folder for the current state of the code. -
Have you actually regenerated something real? Sort of: stack upgrades, language migrations, and a monolith split into a federated architecture, each in two or three passes of "Please rebuild this."
-
Don't agents get worse with more context? Mostly it isn't read. When a long session truly fills the window, we write a handoff, close the session, and start fresh.