Skip to content

[P1] What #638's matching-side state count does to #636 — without funding #636 #664

Description

@LightChainr

Parent: #650. Read-only of PR #648 / #638. No new enumeration unless the control Catalan(w) is missing, and then only w≤6 on the Mac (NEED_HUAWEI for anything heavier).

#637 said the matching-side boundary state space is the cost-model risk for #636. #638 asked to enumerate it. PR #648 exists (Catalan for bonds, site frontier a strict subset, NNN noncrossing through w=8 — verify that sentence against the PR, do not take this parenthetical as the result).

Question

Write the cost-model implication in one notes file:

  1. Quote the actual counts from PR probe638: boundary-state enumeration — Catalan holds for bonds, site frontier is a strict subset, NNN noncrossing through w=8 #648 (primal NN control vs matching NN+NNN, w=2..8).
  2. Tripwire: NN control = Catalan(w), or the enumerator is unused.
  3. One sentence: does this raise, leave, or lower [P1 proof / bounded CPU] Observable spectral remainder and width uniformity after the exact n=2 bridge #636's width ceiling relative to Catalan(w)?
  4. Explicitly do not fund [P1 proof / bounded CPU] Observable spectral remainder and width uniformity after the exact n=2 bridge #636. If you think a TM is now cheaper or more expensive, that is a recommendation in the note, not a STATUS promotion.

Draft PR against main. No merge, do not close #636/#638.

Wait for ASSIGNED_MACHINE: local.

Related: #636 (not released), #637, #638, #648, #635.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    priority:P1Bounded parallel analysis or a concrete reserve direction; not all run at once.

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions