Module skeleton 

Repository Skeleton: deterministic physical-layout evidence for startup.

The skeleton answers “what physically exists here” from the indexed file inventory — indisputable layout facts that ground the inferred architecture in the System Atlas. It is NOT a semantic layer and never overrides semantic evidence: components, flows, and contracts come from the graph, not from directory names.

Invariants: deterministic per file set (BTree iteration only), hard token-bounded (the caller passes the budget; overflow collapses lines, never silently exceeds), role-labeled via the shared scc_graph::components::component_role classifier.

Structs

Skeleton

Rendered skeleton plus honesty counts.

Functions

build_skeleton

Build the skeleton from indexed repo-relative paths. Priority order: every top-level entry first (mandatory, collapses with a count only past MAX_TOP), then depth-2 expansions of production/example/sdk trees (test/fixture/benchmark trees render as one labeled line each), then depth-3 expansions of priority tops only. Lines that do not fit the token budget are dropped and counted, never cut mid-line.

skeleton_budget

Skeleton budget policy: 10% of the startup total, floored so tiny repos still show their top level, capped so the skeleton stays in the hundreds of tokens. Receipt: default startup total is 20_000 → 800-token skeleton.