Repository navigation
docs: add field validity checklist - #66
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adds a field validity checklist for claims that may affect real-world prioritization, operations, funding, policy, tooling, or field practice.
Why
A claim can be well-sourced and still fail when applied locally. This checklist forces contributors to name the actor, decision, setting, capacity assumptions, failure modes, and cheapest field check before treating desk evidence as actionable.
Scope
Docs-only. No schemas, workflows, generated files, or problem packs changed.
Review focus
Please review whether the checklist is specific enough to catch operational overreach without turning every desk-research claim into a deployment study.