domains / families / general / thinking-circle-of-competence

thinking-circle-of-competence

separate

Use when a specific claim may lack grounding. Check evidence boundary, size wrongness cost, then answer, fetch, or abstain — never confabulate.

When to use

• About to assert a specific fact (API, path, number, config, version behavior) without a citable source from this session.
• The claim is about this codebase or system and you have not read or run the relevant artifact.
• Pattern reconstruction would sound complete but is unconfirmed.
• Cost of a wrong confident answer is material (security, data, irreversible action, trust).

When not to use

• Claim is grounded in something you read, ran, or can cite this session, or is stable universal knowledge — answer without false humility.
• Error cost is trivial and reversible and you will flag the claim as unverified.
• Grounding is one cheap fetch away — fetch first; abstention is not an excuse to skip a check.
• User explicitly wants labeled brainstorming or hypotheticals.

Skill page

Source