L2 L7 Lock Verify Only
Question only — do not route, do not change copper
This afternoon a new-chat leftover run still failed the L2/L7 lock: signal copper went back onto the ground planes and we reverted. Flux now says the block is resolved. I need a written answer before any leftover routing.
Ask (answer in writing, then STOP):
Before I continue: are L2 and L7 now a HARD, ENFORCED no-signal rule that the router cannot violate while it finishes the remaining ~135 nets? Yes or no — and what specifically changed on THIS board to make that true (a layer constraint, keepout, or routing rule the router now obeys)? I need the layers to stay solid ground; the last run put signal copper back on them.
Do not route nets. Do not edit traces, vias, fills, placement, or schematic. Do not start leftover work. Inspect rules/stackup only and answer YES/NO plus the concrete change on this board. If you cannot name the enforceable rule, say NO.
Thought
I’ll inspect only this board’s stackup and routing/layer rules, then give a strict YES/NO based on an enforceable router constraint. I will not modify or route anything.
Thought
NO.
On this board, L2 and L7 are defined in the stackup as “Ground Plane” layers named L2 Solid GND and L7 Solid GND, but I found no enforceable routing rule, layer constraint, or keepout that prohibits signal traces on them.
Therefore, I cannot confirm the router is physically prevented from placing signal copper on L2/L7. No routing or edits were performed.
Add hard layer lock
Research enforcement method
Inspect prior lock change
