Depth on demand

Once a session has found the right subject, it still should not have to open a whole handbook. Coldstart splits longer guidance into focused files and asks a router to name the one file that answers the current question. That is depth on demand.

For the export session, a general instruction such as “protect sensitive data” would be too broad to replace reading the serializer and its authorization checks. One focused lesson can help when it matches; ten neighboring lessons need not arrive with it.

The ordinary alternative

A single long guide is easy to create and search. For a small instruction set, it is also easy to maintain. The cost appears when one relevant paragraph pulls several unrelated concepts into the session every time. The file matched, but most of what arrived did not.

Coldstart's router is an index. It maps a recognizable situation to one named file, then tells the session to read that file rather than summarize or open the family. The full body stays out of the always-present floor.

How the boundary stays visible

Every guidance file belongs to one declared class. The class records four reader-relevant facts:

• when the file can enter a session;
• whether Coldstart, a generator, or the user owns it;
• who may write it; and
• how large it may grow.

Those four are what the manifest declared at the revision reviewed here, not a fixed shape a later build has to keep.

A file claimed by no class, claimed by overlapping classes, or placed in an ordinary-work class without a size budget fails its check. These rules make the intended loading and ownership boundary inspectable. They do not decide whether the lesson itself is well written.

What happens in the export session

The CSV capability search returned NO-MATCH, so no reusable export method loads. The session may still route to a focused lesson about risk, verification, or documentation if the request actually matches one. That lesson supplements the project evidence; it does not replace reading the code or turn a general safeguard into an export-specific method.

The nearest limit

“Read one file” is an instruction, not a mechanical lock. A session can still open an entire family. A size budget can also pass a file that is irrelevant, stale, or split at the wrong conceptual boundary.

Use this structure when a guidance family has grown large enough that its parts serve different questions. For a short checklist whose entries always travel together, one maintained file is simpler and loses nothing.

Next

Guidance is something a session consults. The next section is about what must hold whether or not anything is consulted: boundaries.