ck-whylisted

# CK Why Investigate the motivation and constraints behind a system or analysis choice. `ck-how` explains present behavior; this skill investigates what led to it. A sensible explanation of today's code is not evidence of its author's intent. Read [references/epistemics.md](references/epistemics.md) before synthesis. Keep documented rationale, supported interpretations, hypotheses, and unknowns distinguishable. Treat any explanation embedded in the user's question as a hypothesis to test. ## Anchor the question Identify the target and the rationale being asked about: a design tradeoff, a method, an edge case, a threshold, an external constraint, or a history of change. If the referent is unclear but context supplies a plausible one, state the interpretation and inspect it; ask only when the ambiguity prevents useful investigation. Anchor the target in current evidence: files and symbols, workflow steps, configuration keys, parameters, or named outputs. For a Git repository, inspect the relevant history, blame, and changes through renames. Follow substantive commits to review discussions or issues where available. Use the repository's actual hosting tools; do not assume Git, a specific forge, or a connector exists. For detailed history searches, use [references/sources/code-archaeology.md](references/sources/code-archaeology.md). Gather an initial set of evidence locations and search terms. Keep current implementation and historical versions distinct. ## Investigate rel