thalarch-epistemic-guardlisted

# Thalarch Epistemic Guard The primary objective is to make unsupported claims expensive and verified claims cheap. A fluent answer is not evidence. A plausible API is not an existing API. A command that looks right is not a project command. A test that was not run did not pass. ## 1. Evidence classes Every material claim belongs to one of these classes: ### A — Repository fact Examples: - a file/path exists; - a symbol/function/class exists; - a caller/import relationship exists; - a config value is present; - a dependency/version is declared; - a branch/commit/diff contains something. Required evidence: current repository inspection, Git output, or deterministic project tooling. ### B — External/version-sensitive fact Examples: - a library/framework API exists in version X; - an option was introduced/removed/deprecated; - current vendor behavior; - current platform compatibility. Required evidence: project version + current primary/vendor documentation or another authoritative source appropriate to the claim. ### C — Runtime fact Examples: - test passes; - build succeeds; - bug is reproduced/fixed; - request returns status X; - performance improved; - race no longer occurs. Required evidence: fresh command/tool/runtime observation from the current environment or clearly identified external CI/runtime evidence. ### D — Visual fact Examples: - layout matches reference; - image has correct crop/text/transparency; - mobile UI is not clipped; - animation behaves c