Coldstart has not been released. The behavior on this page runs in the development build; there is no release you can install today.
A reusable method is useful only when the session can find it without pretending the library covers more than it does. Coldstart calls a method selected from its declared catalogue a routed capability. The result can be a matching entry or an explicit miss.
For the order app, the honest result is the important one: the request to extend a CSV export
without exposing a field returns NO-MATCH.
The ordinary alternative
Without routing, you can search a notes folder, ask the model to choose, or keep a short list of favorite procedures. That is enough when the collection is small and familiar. As it grows, the same broad words can describe several methods, and a plausible result can be mistaken for a real fit.
Coldstart makes each reusable method declare how it can be found, what it is for, what it is not for, and whether it is usable in the current environment. A request uses one route at a time:
- an exact declared phrase;
- declared category values; or
- free text ranked against the catalogue.
The query reads generated search and return views. If those views are missing, unreadable, or disagree, the query refuses instead of quietly searching a partial catalogue. Eligible results may be removed for the current environment; that filter does not promote a weaker result.
The CSV receipt
The observed request was: extend an existing CSV export without accidentally exposing a new field. It returned:
| Receipt field | Result |
|---|---|
| Request | The CSV-export question as asked |
| Near miss | none |
| Outcome | NO-MATCH |
| Next action | Say no declared method covers it; continue on general skill |
That receipt is one query run against the development build at the revision reviewed here. A later library could answer the same question differently.
The coding session can still inspect the serializer, apply the already recorded field decision, and write checks for authorization and escaping. What it must not do is invent a library entry or claim that an unrelated method was selected.
Why a miss can still be wrong
NO-MATCH reports what this search found. It does not prove that no useful method exists. A relevant
entry could be described poorly, score below the threshold, or be filtered out in this environment.
Likewise, a match proves reachability, not quality or correctness.
The product's bounded routing evaluation does not show superiority over a simple word-matching baseline. Use the result as a catalogue receipt, not evidence that routing improves the work. If a small manual index is easier to inspect and maintain, it remains the better tool.
Next
Cards are one shape of guidance. The other is much smaller and much more numerous: depth on demand.