C.23:4.2 - Rule schema (normative)

For each MethodFamily f, author an executable rule set:

LOG.Deduce_f(TaskSignature S2) → {Admit | Degrade(mode) | Abstain}

with the following branch obligations:

R0 — CG-Spec gate (precondition). For the exact G.5 registry row and MethodFamily, verify the cited CG-Spec.MinimalEvidence and EvidenceProfile for every CHR characteristic used by the family’s acceptance clauses and flows, under the declared claim scope and selected slices, qualification window, and intended selector use. Failure ⇒ Abstain with reasons. Publish the consulted CG-Spec, EvidenceProfile, registry, and policy editions. Rationale: selector legality requires the CG‑Spec gate to be explicit, not implicit in prose. Publish associated ReferencePlane notes alongside the consulted ids.

R0.QD — QD/OEE pre‑gates (if applicable). If S2 declares CharacteristicSpaceRef/ArchiveConfig/EmitterPolicyRef or PortfolioMode=Archive, verify: (i) CharacteristicSpaceRef characteristics are CHR‑typed, d≥2, ReferencePlane per characteristic declared; (ii) ArchiveConfig is lawful (topology, resolution, K>0, InsertionPolicyRef, DistanceDef with edition id and declared metric/pseudometric status); (iii) EmitterPolicyRef present (with edition id); (iv) resolve DominanceRegime; if absent, use default= ParetoOnly. Failure of any ⇒ Abstain with reasons.

R1 — Admit. Admit IFF (a) S2 satisfies Eligibility predicates of f (tri‑state aware), (b) the exact EvidenceProfile minima referenced by Acceptance/Flows for f are met for the declared claim scope and selected slices, qualification window, and intended selector use (post R0), (c) all relevant CAL.AcceptanceClauses (G.4) evaluate to true under lawful CHR comparisons, (d) any maturity gating (e.g., a floor on Maturity rungs) is expressed as an AcceptanceClause and referenced here by id (no acceptance thresholds inside LOG). LOG never sets acceptance thresholds; its rules use and cite Acceptance verdicts.

R2 — Degrade. Apply R0 and, when applicable, R0.QD before any degrade branch, including U2, U3, and R7. Failure returns Abstain for the attempted use. After those gates pass, return Degrade(mode) only through a declared family branch when an admitted unknown or an unmet acceptance condition permits a narrower scope or execution mode under the applicable CAL failure behavior; mode ∈ {scope-narrow | sandbox | probe-only}. An eligibility violation still requires R3 abstention. Record the exact S2 unknowns or unmet conditions, narrowed claim scope or execution mode, qualification window, governing policy edition, and result. If the branch changes the intended use, re-evaluate R0 and eligibility for that bounded use before relying on it. LOG-Degrade never changes CHR scales or planes or turns a failed CAL verdict into a pass. Note (CAL vs LOG). CAL‑level degrade.order (fall‑back to order‑only comparisons) is governed by G.4/CG‑Spec and is not a LOG mode. SoS‑LOG never overrides CAL outcomes; a LOG branch only narrows Scope(G) or execution mode (e.g., sandbox, probe‑only), it does not alter CHR scales or admissible orders. probe‑only MUST cite an E/E‑LOG policy id (exploration budget) and Acceptance‑bound guards.

R3 — Abstain. If S2 violates Eligibility or R0 fails, return Abstain with the failed rule, policy edition, evidence profile, claim scope, qualification window, and reasons. Abstain is mandatory for illegal CHR operations and when a conclusion depends on an F.9 Bridge, kind relation, or plane relation that has not been established.

R4 — Relation and loss routing. Cite an F.9 Bridge, kind relation, or plane relation only when the admission decision actually relies on that obtaining relation. Record its participants, direction, what meaning is preserved and what is lost, receiving use, and applicable policy edition. When the admission use makes a separate named assurance claim, identify its exact target claim and receiving use under B.3. Apply a supported loss penalty only under that assurance policy’s declared rule; route it to R_eff only, leaving F and G unchanged. A changed registry row, evidence profile, claim scope, qualification window, or intended use is not by itself a crossing.

R5 — Proof hooks. Every branch MUST cite Evidence Graph Ref (A.10), the lane tags (TA/VA/LA) and freshness windows required by its cited CG-Spec.MinimalEvidence and EvidenceProfile, and Bridge ids + loss notes when the branch relies on a Bridge; the decision is SCR‑visible. When G.6 EvidenceGraph is present, also publish EvidenceGraph path id(s) for the branch (admit/degrade/abstain). A branch verdict is not its own evidence basis.

R6 — QD archive / PortfolioMode semantics (if applicable). If PortfolioMode=Archive, G.5 selection after Admit may return a QD archive (per ArchiveConfig) instead of only a Pareto set. Unless CAL authorises DominanceRegime=ParetoPlusIllumination (policy‑id recorded in SCR), IlluminationSummary is a report‑only telemetry summary and any coverage/regret are telemetry metrics (reported) that do not affect dominance.

R7 — GeneratorFamily branches (open‑ended). If S2 includes GeneratorIntent, SoS‑LOG MUST: (i) verify EnvironmentValidityRegion is declared and lawful; (ii) verify TransferRulesRef exists; if unknown ⇒ Degrade(scope‑narrow) or Abstain per family policy; (iii) treat the selection surface as pairs {environment, method}; publish coverage/regret and IlluminationSummary as report‑only telemetry (IlluminationSummary = telemetry summary; coverage/regret = telemetry metrics); dominance participation per R6.

R8 — Telemetry & Refresh hooks. On any illumination increase or archive change, publish the current editions and any actual edition increments for CharacteristicSpaceRef/DistanceDefRef/EmitterPolicyRef and the applicable policy‑id (Emitter/Acceptance); expose PathSliceId for refresh/decay in SCR only when an E.18 path slice is current.

Aphorism. “Admit on admissibility and sufficiency; degrade on uncertainty; abstain on inadmissibility.”