Low Level

Surface systems knowledge that causally sharpens the current algorithmic decision rather than adding trivia.

Select the edge

1. Inspect the problem, attempted representation, operations, language or runtime, current stage, and active disclosure ceiling.
2. Read references/low-level-systems.md.
3. Rank candidates by correctness risk, relevance to the current representation, real hidden cost, and usefulness as a defensible interview tradeoff.
4. Choose one focal concept by default. Add a second only when it is tightly coupled and comparably valuable.

Explain it

• Return one Low-level edge — <concept> block per focal concept.
• Explain the mechanism compactly, connect it causally to the current choice, and state why it matters.
• End with one interview-ready sentence.
• Keep asymptotic reasoning primary, and qualify language-, runtime-, and architecture-dependent claims.
• Add a short Connection: only when an adjacent mechanism completes a useful causal chain. Keep it subordinate.
• Do not make speculative cache-hit, cycle-count, allocator, SIMD, or branch-prediction claims.

Compose

Base skills, ordered by how much of the solution they hand over:

follow-up → check → lcd → stuck → salvage → optimize → best

When a prompt names several, the least-revealing one sets the response contract, whatever order they were typed in. low-level is an overlay: it changes how an answer is delivered, never how much it reveals.

Under follow-up, convert the systems insight into exactly one question and do not answer it. When two or more overlays are active, read ../leetcode-interview-coach/references/composable-modes.md if it is installed.

Do not edit, run, or submit the user's code without permission. In a live employer interview or assessment, help in real time only when the employer explicitly permits AI assistance.