Repository navigation

The third state of `0 -> 1`: a derived module's binding to its generator's declared input - #10871

Merged

briansrls merged 9 commits into

mainfrom

fix/derived-binding-classification

Sep 9, 2026

Merged

The third state of `0 -> 1`: a derived module's binding to its generator's declared input#10871
briansrls merged 9 commits into
mainfrom
fix/derived-binding-classification

Commits on Sep 9, 2026
- The third state of `0 -> 1`: a derived module's binding to its generator's declared input
  
  authored and
  Brian Searls
  committed
  6b104a5
- Enumerate the new declaration, and state the partition where the partition is stated
  
  Brian Searls
  and
  claude
  committed
  e5802ed
- Re-home the doc block: the set-disposition paragraphs describe binding_disposition
  
  Brian Searls
  and
  claude
  committed
  724ccc1
- Remove a fabricated default from an auto-admission path; the generator owns its module name
  
  Brian Searls
  and
  claude
  committed
  3c1f517
- Enumerate ROSTER_MODULE in the generator's own roster, with the removal receipt
  
  Brian Searls
  and
  claude
  committed
  2a9be56
- Merge main: the ROSTER_MODULE constant arrived independently, so keep one and union the reasoning
  
  Brian Searls
  and
  claude
  committed
  1676804
- State the arm's residual risk in the tree, not in a review thread
  
  Brian Searls
  and
  claude
  committed
  b9478d4
- Disclose that the arm answers for ONE generator, and name what a second would need
  
  Brian Searls
  and
  claude
  committed
  9cb7c65
- Merge main: the wave now DOES consume ROSTER_MODULE, so main's correction needed correcting
  
  Brian Searls
  and
  claude
  committed
  f584dbf