Constraint-Led Method -- Schema Gaps (method level, all problems)
================================================================
Compacted 2026-10-02 with D's approval.  The full register (G1-G22 with
their findings, scores and dated updates, 1,295 lines) is in git history;
this file keeps only what is still open.  Ids are stable and never reused:
a citation of any Gnn elsewhere refers to that entry in history.

PURPOSE
-------
A schema gap is a question about problem structure the static profile
failed to ask, found by surprise (M5), stated domain-generally rather than
as a patch for one problem.  solving-advisor.md, Subgoal dialogue step 5,
files new gaps and complex development needs here.  Recording a need is not
implementation approval; agree new work with D separately.

ENTRY FORM FOR NEW GAPS
    Gnn -- <title>                                       [OPEN]
    Origin     <problem>, <task or stage>, <date>
    Found      how it was found
    Missed     what the schema missed
    Question   the question that should have been asked
    Fix        a domain-general fix (proposed, not implemented)
    STATUS     OPEN / CLOSED, with dated updates beneath
The next free id is G23.

CLOSED BY THE 2026-10-02 COMPACTION
-----------------------------------
G3, G4 and G10 concerned the prediction-register apparatus (value
predictions, leakage through scoring text, partitioning register section
4).  The register was retired 2026-09-25; D closed them 2026-10-02.
Already closed or resolved before compaction: G1, G2, G5, G6, G7, G11,
G13, G14, G18, G19 (for supplied scenarios), G20, G21, G22.
G9 (a keeper can serve a non-movement passage) was RESOLVED 2026-10-02 at
SD's scope (T43): SD keys services on controlled devices, not traversal
arcs, covering gates, traversal-clause drives and receivers.  Checked on
crelay-topo's profile: gate8 (on the route) needs receiver1 active; every
receiver1 chain needs gate4 open; gate4 open == a body on plate3, which is
G9's original case.  Not claimed by SD, as before: how long the body must
stay (simultaneous availability).

OPEN GAPS
---------

G8 -- No extractor owns the segment axis                    [OPEN]
    Origin     crelay-topo, 2026-09-19.
    Question   Which state bit opens and closes an epoch (e.g. a recorder
               cycle), and across that boundary which objects, facts and
               capabilities are created or destroyed rather than changed?
    Fix        Report, per dynamic relation, updates that delete its
               propositions wholesale and the guarding condition; the
               epoch bits and what does not survive them follow.
    Status     Open.  Segments are still supplied by the caller (RO, CP's
               :reservations, BT's single supplied event); none is
               extracted.

G12 -- Destination and transition premises not supplied by a cut [OPEN]
    Origin     crelay-topo, 2026-09-20.
    Question   What derivation obliges each cargo object to reach a
               particular region, and which concrete transitions are
               covered by the graph used to claim its keeper cannot follow?
    Status     Open, addressed in part.  S4 prints explicit destinations,
               conditional pressure demand and graph-only cut candidates;
               RO and CP (T44) check caller-stated allocations and
               reservations.  Not done: destinations or reservations are
               not derived, their necessity is not established, and reach,
               transport and replacement witnesses are not evaluated.

G15 -- Launch configuration and propagation across a traversal [OPEN]
    Origin     crelay-topo, 2026-09-22.
    Question   Before assigning a realization or budget to a region-graph
               traversal, what launch elevation or support does its
               movement predicate require, and do the controller changes
               needed to clear the barrier preserve that configuration
               through propagation until the crossing?
    Status     Open.  BT (T45) answers the controller-transition and
               propagated-successor part for one supplied event; nothing
               assigns a launch configuration to a traversal.  The
               advisor's Subgoal dialogue (check each transit state apart
               from the final state) is the procedural stopgap.

G16 -- A route arc names a door, not the work of opening it [OPEN]
    Origin     crelay-topo, 2026-09-24.
    Question   For each device a route must cross, where must an actor be
               to operate its controller; is that on the route; and if not,
               what route, keepers and return does the excursion need?
    Status     Open, addressed in part.  SD (T43) joins passage services to
               their providers and premises and flags NEEDS ... FIRST.  Not
               joined: switch and toggle reach sites to the route,
               placement or pickup from outside the site's region, and an
               excursion's return with cargo.

G17 -- A relay chain needs relay-to-relay sightlines and a body cost [OPEN]
    Origin     crelay-topo, 2026-09-24.
    Question   For a receiver-controlled device, which relay chains connect
               a source to the receiver, under which device states, and
               which bodies, risers and pressure supports does each commit?
    Status     Open, addressed in part.  RC (T16) enumerates the chains.
               Not done: feeding RC into S4's receiver row and into the T6
               budget.  Stays open until those joins exist or D decides
               they are not needed.

NOTE -- Continuation prerequisites (rumin-topo, 2026-10-01)
-----------------------------------------------------------
Which prerequisites of the intended next subgoal, or already-known later
dependencies, does a proposed endpoint preserve or lose?  Resolved as
procedure: solving-advisor.md, Subgoal dialogue step 2 (look ahead; preserve,
replace, restore when relied on, or deliberately abandon).  BT can expose a
support loss for one supplied event.  Automatic derivation of continuation
prerequisites is not implemented or authorized.
