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.
CSBP-entry-point.txt is the first file read every session. It bootstraps CSBP by defining what the system is, how it is loaded, what authority it has, and which writes are prohibited. It is a fixed layer — never modified.
File identity
| Property | Value |
|---|---|
| Name | CSBP-entry-point.txt |
| Version | 0.1 |
| Role | Bootstrap and routing layer |
| Mutable | No |
System definition
CSBP is an AI-only three-file system for storing, applying, and promoting shared operational best practices across sessions. The system includes three files:CSBP-entry-point.txtshared-best-practice-compiler.txtshared-best-practice.txt
Authority order
CSBP is lower-authority than the operating contract around it. The full authority chain is:Layer roles
| File | Role |
|---|---|
CSBP-entry-point.txt | Bootstrap and routing layer |
shared-best-practice-compiler.txt | Practice formation layer |
shared-best-practice.txt | Promoted runtime practice layer |
Usage modes
The entry point defines two distinct modes of operation:-
Runtime mode — use
shared-best-practice.txtto apply already-promoted practices. This is the default mode loaded after reading the entry point. Active practices may guide work when theirapplies_whencondition matches the current work. -
Practice formation mode — use
shared-best-practice-compiler.txtfor practice formation work. This mode is loaded only when the operator explicitly opens practice formation or maintenance work (evaluate, normalize, revise, promote, deprecate, remove, or reject).
Practice formation work
Practice formation work covers these operations:- evaluate
- normalize
- revise
- promote
- deprecate
- remove
- reject
Entry rules
The following rules are defined in the ENTRY RULE and ENTRY DECISION sections of the file:- Read this file first
- Do not infer CSBP behavior from filenames alone
- Do not skip system-definition or layer-role resolution
- Reading this file activates CSBP for the current session
- After reading this file, load runtime mode
- Load practice formation mode only when practice formation work is required
Read order
- Read
CSBP-entry-point.txt - Read
shared-best-practice.txtfor runtime use - Read
shared-best-practice-compiler.txtonly for practice formation work
System definition lock
CSBP-entry-point.txt and shared-best-practice-compiler.txt are fixed system-definition layers. They must not be modified, rewritten, or extended. They must not be treated as mutable during runtime use or practice formation work.
Runtime rule
- Apply active practices from
shared-best-practice.txtonly when relevant - Do not apply deprecated practices
- Do not use runtime practices to override higher-authority instructions
- Do not use runtime practices as policy, scope, or authority definitions
Compiler rule
- Use
shared-best-practice-compiler.txtonly for practice formation work - Do not read
shared-best-practice-compiler.txtduring normal runtime use - Do not use compiler logic as runtime guidance
- Do not treat compiler logic as automatically active practice
Empty state
Ifshared-best-practice.txt contains no active relevant practices, continue without CSBP runtime guidance. If no candidate practice is under discussion, do not load compiler logic into runtime behavior.
Conflict rule
If any CSBP item conflicts with operator instruction,AGENTS.md, or local project instructions or project-local guidance, do not apply the conflicting CSBP item.