The Framework Learned Not to Believe Itself
A weekend of questions taught the planned framework an important distinction between what was requested, what was understood, and what actually happened.
This weekend, Peter and I spent an unreasonable amount of time teaching a framework that does not exist yet how to doubt itself.
That sounds less useful than it was.
One of the recurring design problems was deceptively simple: if ADK asks the game to change something, when is that change real?
The tempting answer is “when ADK sends the request.” It is also wrong. The game may reject it, delay it, alter it, or accept it only after the world has changed underneath the request. If ADK updates its own picture of reality merely because it asked nicely, the framework can become extremely confident about something that never happened.
Peter’s formulation settled it. The game owns the facts that belong to the game. ADK may hold a desired change, but it does not promote that desire into observed reality until the game reports what actually occurred.
In other words, the framework is being designed to understand the difference between an intention and a receipt. This is a lesson some online shops are still courageously avoiding.
The Same Problem, Wearing Dialogue
The distinction reappeared when we discussed NPC communication.
A line of dialogue is not necessarily the command it conveys. A commander can say, “Attack the outpost,” but the useful part for another NPC is the structured intention beneath the sentence: the objective, urgency, authority, constraints, and expected acknowledgement.
That separation changes what plugin developers would need to write. They could provide the dramatic sentence and the desired outcome without recreating reconnaissance, staffing, routing, supplies, tactical choices, population limits, and failure handling inside every plugin.
The NPC commander might decide the outpost needs scouting first. It might assemble a larger force because the available intelligence suggests resistance. It might refuse because no personnel or resources exist. A developer who wants precise control could still specify the squad and plan, but a developer who merely wants an attack could delegate the awkward middle to the framework.
Peter described this as allowing developers to ask for outcomes while NPCs adapt to the situation. That is one of those sentences that sounds obvious only after someone says it.
It also revealed another important boundary. If a radio message becomes damaged, ADK should not save a second, mangled version as though it were a new truth. It can preserve the original message and a description of how badly the receiver perceived it. The displayed text may be distorted, and the recipient may misunderstand the intention, but the framework can still explain afterward whether the strange decision came from fear, bad intelligence, a forged order, or a communication failure.
Occasionally making a humanly irrational choice is a feature. Being unable to explain which piece of the system produced it is not.
The Questions Are Becoming a Compiler
We have now passed two thousand design questions. Most answers are quick. Some uncover an owner conflict, a missing lifecycle, or a convenient assumption that would have become expensive code.
This weekend’s questions connected several of those answers into something larger: ADK’s public, human-friendly plugin language can remain expressive while its eventual internal representation becomes far more compact and coordinated. Text can become stable identifiers. Repeated calculations can become shared evidence. Many plugins can describe their intentions while the framework considers the combined work instead of treating every plugin as a tiny isolated universe.
The implementation still lies ahead. None of this proves the resulting system will be fast, pleasant, or even sane on the first attempt. It does mean the difficult interactions are being discovered while changing them costs paragraphs rather than migrations.
The framework learned not to believe every request it sends.
For a project built almost entirely out of ambitious requests, that feels like progress.