The admission and rejection criteria are the core filter that makes CSBP useful. A practice only enters the runtime file if it clears every admission criterion. Rejection is not a failure — it is the system working correctly.Documentation Index
Fetch the complete documentation index at: https://mintlify.com/xxyoudeadpunkxx/csbp-codex-shared-best-practice/llms.txt
Use this file to discover all available pages before exploring further.
Admission criteria
A candidate is admitted when it is:- Recurring across sessions
- Global or environment-global
- Actionable during real work
- Preventive by default
- Expressible as a short operational instruction telling what to do
- Stable across work contexts
- Not already covered by
AGENTS.md - Not already covered by a stronger local instruction
- Likely to reduce recurring waste or error
Rejection criteria
Reject material that is:- Project-specific
- Session-specific
- One-off
- Vague
- Diagnostic-only
- Recovery-only
- Post-failure only
- Duplicate of an existing practice
- Duplicate of
AGENTS.md - Duplicate of local project instructions or project-local guidance
- Too broad to match reliably
- Too narrow to matter outside one case
- Conflicts with higher-authority instructions
- Depends on hidden or unstable context
- Reads like explanation instead of instruction
- Reads like policy instead of operational correction
Borderline cases
Handling borderline candidates
Handling borderline candidates
Borderline candidates should be narrowed or split. A pattern that is partly session-specific and partly global should be extracted to its global core. A pattern that covers two separate wrong behaviors should be split into two blocks. When in doubt, reject and reopen when more recurrence evidence exists.
Why strict criteria matter
A practice that passes the filter will be present in every future session where itsapplies_when condition matches. A weak practice creates noise and erodes trust in the layer. The filter exists to protect signal quality.