Federal overlays are interpretive continuity surfaces that help Atlas describe nationally coordinated infrastructure influence without converting federal presence into canonical corridor authority.
This framework defines how federal overlays reinforce continuity interpretation across jurisdictions while remaining subordinate to the Atlas topology contract, corridor-group placement, foundation-layer classification, and completion-layer participation.
Federal overlays describe national-scale infrastructure systems that reinforce corridor continuity across jurisdictions. They support interpretation, strengthen adjacency confidence, clarify infrastructure dependence, and extend continuity visibility.
They help Atlas describe nationally coordinated infrastructure influence without altering the canonical topology contract.
A federal overlay is infrastructure continuity derived from nationally coordinated systems including national laboratories, defense infrastructure, DOE transmission corridors, interstate transmission designation, federal compute systems, and federal logistics networks.
Federal overlays may strengthen interpretation across multiple jurisdictions, but they do not independently create corridor placement authority.
The topology trio remains authoritative. Federal overlays may strengthen the plausibility, continuity, or bounded stability of a reading, but they may not convert support into canonical placement authority.
Shared overlay visibility does not imply identical corridor-role strength, foundation participation depth, or completion-layer placement.
National laboratory overlays include DOE national labs, federally administered research campuses, and federal experimental infrastructure complexes.
They do not independently establish anchor placement and do not replace canonical topology or evidence requirements.
DOE overlays include national transmission initiatives, federal energy corridor designations, grid modernization backbone participation, and regional transmission reinforcement planning corridors.
DOE overlays do not independently assign corridor origin authority.
Defense overlays include military logistics corridors, defense compute infrastructure, defense research facilities, and strategic mobility systems.
They must remain interpretation-support structures only and may not independently assign corridor roles.
Designation overlays include federally designated transmission corridors, regional transmission priority zones, and multi-state infrastructure reinforcement surfaces.
A designation may matter structurally without becoming topology origin authority by itself.
Federal compute overlays include national computing facilities, federal HPC systems, DOE compute backbone infrastructure, and defense compute clusters.
Federal logistics overlays include strategic freight coordination corridors, military logistics alignment systems, federal emergency transport continuity infrastructure, and interstate mobilization corridors.
Federal overlays must defer to:
Overlay visibility strengthens interpretation clarity but does not modify placement authority. Overlay relevance may influence interpretation, but it may not alter the trio fields or their authority.
Federal overlays may:
Federal overlays commonly stack with:
Overlay stacking must remain explicit. Implicit cross-foundation inheritance is not permitted. When multiple overlays affect the same jurisdiction, dominant overlay dependence must remain explicitly identifiable.
Federal overlays may appear as:
They must not convert signals into evidence, replace corridor-role classification, or override topology placement. Signal taxonomy remains authoritative.
Federal overlays may strengthen:
Overlay presence must not create deployment readiness inference, certification posture inference, or corridor sufficiency inference. Trust dimensions remain non-scoring interpretive structures.
Builder-mode interpretation may reference overlays to:
Builder Mode must not treat overlays as siting authority signals. Deployment posture remains evidence-bound.
The renderer may:
The renderer must not:
A jurisdiction package is federal-overlay compliant when:
Non-compliance occurs when: