G01-LT: Yes
Rationale
A constructive hierarchy avoids a complete global reachability table: assign contiguous ipn node-number ranges to subtrees. Each gateway keeps its own endpoint, immediate-child ranges and a parent default exit. ION documents narrowest-range exit selection after local CGR/direct-neighbor routing, and re-forwarding toward a reachable gateway. Provision only adjacent egress/contact data. A bundle ascends until a gateway contains the destination in a child range, then descends to it. Root gateways retain child aggregates rather than every destination; no global directory or replicated global contact graph is required by this construction.
Assessment method
Constructive documentary plausibility; no runtime or capacity experiment
Source context
Pinned ION ipnrc: exit semantics, routing precedence and gateway reachability
Outstanding qualification
Use adjacent LTP engines over the selected Encapsulation/AOS links with local engine/channel mappings. No global engine directory or IP underlay is introduced. Space-link identifier allocation and S03 are separate and unchanged. Architectural plausibility under an explicitly provisioned finite hierarchy, unique hierarchical node numbers and usable adjacent contacts within bundle lifetime. Every exit gateway needs an actual local egress plan or computable local route. Regional contact/trust administration is local, not a hidden global planner. No claim of automatic numbering, automatic convergence, arbitrary-topology routing, failure recovery, optimal routes, full ION/profile execution or measured global capacity. A failed child path may invalidate the witness; this is not a resilience proof. G05 remains Pending.
Public sources
Editorial evidence references
The following identifiers refer to research records not included in this public package; they are not public links.
- round306-sources.json
- round309-sources.json