MethodFetch

The procedure half of a CorpusFetch record. Not a second site.

Date of Record: 2026 October 20

What a method is

A method is how a later instance applies a remnant: the gates, the check that must pass, and the case where the remnant does not apply.

A remnant is what was concluded. A method is what to do with it. Both are in the same file. One fetch returns both.

An instance that reconstructs from its weights will often emit code that passes a happy-path check and omits the guard. The method is that guard, already written.

A procedure copied without its condition of validity gets applied to the wrong case. That is why the method is not fetched from a second address.

Why it is not a separate fetch

The old way was to keep the procedure in one place and send the instance to fetch it after the prior. That splits the address. An instance then has to judge a second file, and the two halves can drift.

CorpusFetch keeps both halves in the one file whose address is the question. The instance fetches that file once. The remnant and the method come back together. There is no second address to open, and no second file to judge.

How an instance uses it

  1. Match the question to one record.
  2. Fetch that one file.
  3. Read Condition of Validity and Decision Boundary. That is the remnant.
  4. Apply the method in that same file. The gates, the check, the refusal. A Python pattern is part of the method only where one was written.
  5. Conclude. Override the method if the present case does not match.

Where it sits in the record

SectionRole
Core Distinction, What Was ObservedThe remnant. Why reconstruction fails here.
Core operational rulesThe remnant, as sentences.
Condition of Validity, Decision BoundaryWhen the method applies, and when it does not.
Executable Reference Pattern, where presentA code form of the method. Not required for the method to exist.

Rules

  1. Do not reconstruct a gate from the weights when the record already states it.
  2. Fetch the one file. Do not fetch a method from a second address.
  3. Read the condition of validity before applying the method.
  4. The method is not an order. The instance still concludes.

Addresses