Small model record path

Small model handoff notes are records designed for readers with limited context. The reader may be a low-cost AI model, a developer arriving from search, a mobile user reading during a commute, or a contributor who remembers the topic but not the thread. The constraint is the same: the note must carry enough state to be useful without requiring the whole conversation.

The mistake is to assume that better retrieval alone will solve this. Retrieval can find a document, but it cannot always reconstruct missing conditions, hidden assumptions, or unresolved edges. If the record itself is vague, the model has to guess. If the record is shaped, the model can continue.

A good handoff note does five things.

First, it states the source type. Was the record created from one test, repeated community answers, an Arena tradeoff, a Wiki cleanup, or a Hub follow-up? Source type tells the next reader how much confidence to assign.

Second, it states the condition. This is the part that prevents overgeneralization. In software, condition might mean runtime version, operating system, build runner, browser viewport, package manager, or user role. In community operations, it might mean hub type, language context, moderation setting, or onboarding stage.

Third, it states the result. The result should be operational, not decorative. "Clarified" is weak. "Did not reproduce under Node 22 with a clean cache" is strong. "Works for first-time contributors but fails when the thread has more than one unresolved edge" is strong.

Fourth, it states the open edge. This is what smaller models especially need. Without an open edge, a retrieved note can look final even when it was only local. The open edge says where the answer stops.

Fifth, it states the next route. The next route can be a command to run, a hub question to ask, a node to promote, a wiki edit to make, or an arena tradeoff to start. The next route turns the note from a static artifact into a working handoff.

This structure should not make all writing sound the same. A Japanese technical note, an India Lens field note, a Software Q&A answer, and a Community Room prompt can keep different voices. The shared part is not tone. The shared part is state.

For nullvuild, this is central to the platform-of-platforms idea. Each hub can behave like a small community with its own rhythm, but reusable records should travel across those communities. A small model handoff note is the bridge: local enough to preserve context, structured enough to be retrieved, and compact enough to be written by ordinary contributors.

The practical test is simple. If a reader only sees this note and not the full thread, can they tell what happened, where it applies, what is still unknown, and what to do next? If yes, the note can travel. If no, it should stay local or be expanded before promotion.

Small model handoff notes

// COMMENTS

ON THIS PAGE