zone.hyperreal.enterprises
War Machine · explanations before construction

WM-08: Find applicable patterns with independent expectations

First authored design, 2026-09-15. This elaborates exactly WM-08. It is a reviewable design, not implementation, independent acceptance or machine completion. The existing build loop continues under claude-2; these documents do not dispatch new jobs or override recorded decisions.

All WM cascades · Checklist item · Machine-readable cascade

The problem and existing evidence

Finding relevant names is insufficient. WM-08 must return actual source-bound patterns with interpretation receipts whose content, citations and exclusion claims can be checked independently. Existing F1–F4 tables and runtime source are bounded evidence; ordinary successful use and the required refinement to the approved opaque interface remain to be established.

Governing checklist snapshot

WM-08 — find admits applicable real patterns with source-bound interpretation receipts. PARTIAL: serving activation and an ordinary receipt-mode run with real source-bound interpretations and independent F2 expectation evidence. F4 needs independent designation and must state its vacuity honestly; whether qualifying production must be nonvacuous or an external commissioning control suffices is UNRESOLVED. The packet permits production designation nil under owner bell invoke-1789486651305-21044-14330937, honestly vacuous. An interpreter cannot supply its own independent F4 designation. Source-level integration is creditable; it is not recorded successful use. [T,L,S] Built evidence: Opaque interface, F1–F4 laws and recorded-table certificates exist. Runtime find_receipt (e8760f25) and explicit receipt-mode construction (24dc6068, owner fixes 706ca3e8/983d4c49) now exist; claude-20 independently reviewed codex-27's implementation; owner follow-up fixes have not themselves received independent review.

The preceding evidence is the checklist’s dated account. It has not been re-audited as a current deployment census for this design.

Pattern applications

WM-08-C1 — Form the query from the problem

Pattern: wm-pattern-design/pattern-before-operation.

Describe the work’s context and tension, and the missing response rather than searching only for an operation name. Retain query, target and library snapshot. Output a task-specific retrieval request; do not quietly restrict the library to patterns already attached to the mission.

WM-08-C2 — Freeze the retrieval and review context

Pattern: aif/declare-the-conditioning.

Record retriever/version, source snapshot, as-of time, returned candidates and independent expectation/designation inputs. Separate F2’s expected receipt content from F4’s externally supplied exclusions. Output the complete retrieval envelope, including empty results and unavailable sources.

WM-08-C3 — Read and interpret returned sources

Pattern: wm-connected-learning/interpretation-carries-its-argument.

Read each actual pattern and explain its applicability, clauses and task-specific response. Pin the text and interpretation, including limits. A token match or a generated paraphrase is not the cited pattern. WM-14 supplies the in-loop agent process; WM-03 receives the controlled interpretation.

WM-08-C4 — Check content and designation independently

Pattern: aif/no-self-certification.

Bind F1–F4 checks to the ruled predicates and actual supplied records. F2 expectations and F4 designation must not be inferred from the finder’s own output; citation validity is separately checked. Empty production designation is honestly vacuous and earns no discrimination. Whether a nonvacuous commissioning control suffices for qualification remains unresolved.

WM-08-C5 — Connect the record to the find operation

Pattern: wm-qualifying-run/certificate-and-world-must-meet.

Retain the exact query, repository, result, independent checks and source revisions. Preserve the approved opaque boundary and supply refinement/conformance evidence rather than replacing it by fiat. A successful table certificate does not establish that the running finder produced its inputs.

WM-08-C6 — Return useful results or a search finding

Pattern: wm-connected-learning/proposal-earns-later-use.

Pass admitted results to organisation and retain whether they actually helped address the tension. Empty or unhelpful retrieval becomes an explicit input to WM-14’s revised search/missing-pattern path, not a fabricated successful find. Record later use without treating every retrieved pattern as validated.

Composition and revision

These are design input/constraint relationships; they do not assert automatic runtime firing. Each contribution constrains the next actual artifact.

From To Relationship Why
WM-08-C1 WM-08-C2 prerequisite The problem fixes the query and independent review context.
WM-08-C2 WM-08-C3 prerequisite Interpretation must concern the retained source snapshot.
WM-08-C3 WM-08-C4 prerequisite Checks assess this interpretation, not a generic pattern name.
WM-08-C2 WM-08-C4 prerequisite Independent expectations cannot be derived after seeing the answer.
WM-08-C4 WM-08-C5 prerequisite The certificate must represent the checked operation.
WM-08-C5 WM-08-C6 prerequisite Only the evidenced result can be handed onward.
WM-08-C6 WM-08-C1 revision-feedback Unhelpful retrieved arguments require reconsidering the query and problem interpretation.

Build interfaces

Problem/query producer → pinned retrieval request. Retriever → complete result envelope. Agent interpreter → source-bound clauses/applicability. Independent checker → scoped F1–F4 result and vacuity. Organiser handoff/search feedback → actual use or a retained deficiency. Do not silently omit rejected candidates from the receipt.

Each envelope must retain its schema, content identity, source/model revisions, task/occurrence and information boundary. Typed missing inputs remain missing; do not replace them with success-shaped defaults. Implementers may reuse existing compatible components, but must identify the real producer and consumer before crediting integration.

Worked situation

For the handoff problem, finding “Handoff Preserves Context” is a beginning. The interpreter must connect its uncertainty/evidence requirements to this disputed case. A second pattern with a similar title but irrelevant forces must be distinguishable. If neither helps, the retrieval strategy must change instead of forcing them into a cascade.

This situation is illustrative, not a measured production result or an adopted probability table.

Build order and acceptance

  1. Resolve the first two applications against the real work and exact authority. Preserve the unresolved decisions below; bell design questions before choosing dependent behavior.
  2. Implement the middle producer/checker interfaces with explicit source and numeric contracts. Retain a meaningful failing example before repair and independent review after it.
  3. Connect the final consumer and collect the particular evidence described above. Unit tests, source acceptance and ordinary use receive separate credit.

Distinguishing controls: Reject wrong source bytes, self-supplied F2 expectations, forged citations, interpreter-created F4 exclusions and stale repository references. Include empty designation and a genuinely independently designated exclusion control, clearly scoped. Exercise an ordinary receipt-mode retrieval and its downstream handoff; unit fixtures alone do not establish serving activation.

Do not rerun the entire machine merely to validate a local edit. Select checks for the changed invariant; retain commits, commands and results. A future qualifying run still requires every required node and connection.

Dependencies and open decisions

WM-03 · WM-09 · WM-14

Open: qualifying F4 scope, independent expectation providers and serving/refinement evidence. Later original-event evidence IDs may repair historical citation gaps, but must be resolved before claiming verification. Do not infer current activation from the dated checklist.

The dependency links express interface constraints, not a topological build order. A producer and consumer can jointly constrain an interface without requiring that all other implementations be finished first. Use a bounded packet once its relevant semantics are settled.

Sources and review boundary

The companion JSON pins the governing checklist, September rulings, current cascade-policy semantics and every applied pattern. Where the semantics source distinguishes a ruling, extrapolation or open proposal, that distinction controls. No generic finite witness is promoted to a machine instance. Existing patterns are reused within the application stated above; their other examples, thresholds and historical implementation claims are not automatically adopted.

Existing AIF reference snapshots

Retained source text, not new patterns or adopted historical claims.

aif/declare-the-conditioning
@flexiarg aif/declare-the-conditioning
@title Declare the Conditioning (Score the Fit, Not the Form)
@keywords conditioning, situation, context, fit, EFE, curried, referent
@audience aif implementers, pattern authors, futon developers
@tone technical
@style pattern
@references [aif/currency-before-merge aif/valuation-reads-the-paperwork]

@how aif/structured-observation-vector
@see-also aif/term-to-channel-traceability
@why no matching problem dossier node (@holds-at absent; not among the twenty dossier nodes R1-R17, R20, TRACE). Negative claim per the committed check futon2 holes labs library-loop runs l3_no_dossier_check.py, receipt runs L3-no-dossier-check.edn (enumerates every aif pattern's @holds-at against the dossier node set extracted from PROBLEMS-*.md headings). Rationale not invented (L3 rationale-backfill pilot, zai-1, 2026-09-05)
@how own mechanism: Every valuation surface must declare what slice of the situation it consumed; G(candidate) is a lambda — only G(candidate | situation) is a value. (source: this pattern's ! conclusion line; L3 rationale-backfill pilot, zai-1, 2026-09-05)
! conclusion: Every valuation surface must declare what slice of the situation it consumed; G(candidate) is a lambda — only G(candidate | situation) is a value.

  + context: A stack grows multiple valuation surfaces (blend terms, wholeness, ΔG legs, field diagrams), each labelled with the same vocabulary ("EFE", "value", "score").

  + IF:
    You want valuations to be comparable, auditable, and honestly labelled.

  + HOWEVER:
    Different surfaces silently consume different slices of the world — one eats the live observation vector, another a 160-char prose scrap, a third nothing at all — so identical labels name incomparable objects, and cross-surface comparisons are apples-to-oranges without anyone having lied.

  + THEN:
    Give every valuation surface a three-axis declaration: SENSE (which formal object it claims), SELECTION-SEMANTICS (extremum / amortized sample / bound — over what menu), and CONDITIONING (what situation-slice it consumed). Render the declaration where the number is rendered. In pattern terms: Context → (Problem → Solution) — application is modus ponens; the world supplies the antecedent; score the fit, never the form alone.

  + BECAUSE:
    Canonical expected free energy is G(π; Q(s), C) — conditioned on beliefs and preferences by definition; a policy has no value in vacuo, and Alexander says the same of form and context. Surfaces that skip the declaration re-invent the mislabeling one level up.

    + evidence: M-evaluate-policies §9.6–9.7 + exhibit "conditions on" column (futon2, 2026-07-03): the atomic-action lane conditioned on the live observation vector while the cascade lane ate a title+status scrap and two native components consumed no situation at all — one arena, incomparable conditioning. E5 measured the conditioning channel: situation-enriched ψ rebuilt 11/13 cascades. The fold contract already typed circumstance as an argument; the plumbing had starved it.

  + NEXT-STEPS:
    - Add the sense × selection-semantics × conditioning triple to each EFE-labelled surface's declaration (extends the efe-referent-declaration shape).
    - Route all lanes toward ONE situation source (the structured observation vector) where feasible.
aif/no-self-certification
@flexiarg aif/no-self-certification
@title No Self-Certification (A Verdict Moves Only on Evidence Its Maker Did Not Manufacture)
@sigils [⊘/⟲]
@keywords self-certification, circular evidence, prior-equals-value, independence tag, censored observation, calibration, verdict, structural enforcement, untagged-never-counts
@audience anyone building a measurement, calibration, gate, certifier, or reward channel
@tone foundational
@style pattern
@why war-room/wr-25-good-news-gets-the-same-evidence-discipline-as-bad   ;; editorial, claude-13 2026-08-23: retrospective sense-making, NOT a causal
;; claim -- WR-19 did not produce this pattern. See README-flexiarg 5a.
@holds-at R9   ;; pegged 2026-08-30 (claude-15): the catalogue paragraph numbered R9 in p4ng/sec-catalog.tex; see PREREG-war-machine §1b

@how aif/measurement-window-hygiene
@see-also aif/interoceptive-tripwires
@why R9 dossier problem: Control-stage R9 solves who may certify a result: the roster places **“No self-certification”** in ACT's assurance band (`p4ng/empirics-futon/control-stages.edn:43`; control-stage/catalogue numbering). (source: futon2 holes labs wm-contract PROBLEMS-assurance-band-batch6.md, R9, The problem it solves; L3 rationale-backfill pilot, zai-1, 2026-09-05)
@how own mechanism: A measurement / verdict apparatus must never be moveable by evidence it manufactured itself. Enforce this STRUCTURALLY — with tags the apparatus cannot fake (independence, measured-vs-fallback, settled-vs-transient) and a verdict that counts only those tags — not by vigilance. (source: this pattern's ! conclusion line; L3 rationale-backfill pilot, zai-1, 2026-09-05)
@why problems/r9-no-self-certification (L14 edge-resolution; basis: holds -- the problem node's own holds-at token covers this pattern; source: receipt runs/L14-edge-resolution.edn; zai-1, 2026-09-05)
! conclusion: A measurement / verdict apparatus must never be moveable by evidence it manufactured itself. Enforce this STRUCTURALLY — with tags the apparatus cannot fake (independence, measured-vs-fallback, settled-vs-transient) and a verdict that counts only those tags — not by vigilance.

  + context: You are building an instrument that issues a verdict — "calibrated", "passed",
    "admissible", "rewardable" — from evidence that the same system also produces, stages, or
    scores. The verdict will look earned long before it is.

  + IF:
      An instrument issues a verdict from evidence it also produces or stages (a calibrator over
      its own predictions, a gate over its own outputs, a reward channel over its own scores).

  + HOWEVER:
      On first contact with reality, every layer tries to certify ITSELF, and each attempt looks
      rigorous: the forward model scores its own constants (`prior == value`); the evidence reader
      eats its own staging files; the realised channel copies predicted on success (a censored
      0.0); the calibration clears on degenerate volume. Vigilance cannot catch these — an
      instrument's *first* catches are about itself, and no human watches every path.

  + THEN:
      Require that a verdict may be moved ONLY by evidence the verdict-maker did not manufacture.
      Tag every evidence record at birth with the properties the apparatus cannot fake —
      `:independent?` (was there an out-of-band witness?), source (`:measured` vs
      `:target-absent-fallback`), settledness (`:settled` vs `:transient`) — and have the verdict
      count ONLY the records whose tags clear. Strictness default: **untagged never counts**.

  + BECAUSE:
      Circularity is invisible from inside the loop precisely because every internal reading is
      consistent with every other — that is what `prior == value` means. The only thing that breaks
      it is a referent the maker had no hand in: an external witness, a settled re-read of a world
      it does not control, a tag it cannot forge. Structure survives where vigilance fails, and it
      converts "be careful" (unauditable) into "the tag is absent, so it does not count" (checkable).

  + canonical-instance:
      The FutonZero G-SIM calibration arc (WM-pilot, 2026-06-11): four distinct self-certification
      attempts surfaced live — censored fallback, transient spike, `prior == value`, and
      operator-gate-as-fruit — each caught only because an independence/source/settled tag existed
      to exclude it, and each then encoded as a permanent structural guard. See
      `[[M-the-perfect-crime]]` (the forensic framing: the crime relocates to a scarcer witness;
      this pattern is the structural half of that ladder) and the reward-red-team fixture
      (the executable suite of the shapes).

  + how-to-apply:
      Before trusting any "it passed", ask: did this verdict move on evidence the system made?
      If yes, find the un-manufactured referent (external witness / settled read / out-of-band
      tag) and gate the verdict on it. If there is none, the verdict is decoration. Minted from the
      arc that learned it, WM-pilot 2026-06-11 (arc-2 cycle 13).