Entry Point Reference: CSBP Bootstrap and Routing Layer
Reference for CSBP-entry-point.txt: the bootstrap and routing layer defining system identity, authority order, load order, modes, and write restrictions.
Use this file to discover all available pages before exploring further.
CSBP-entry-point.txt is the bootstrap and routing layer for the entire CSBP system. It is read first, every session. Reading it activates CSBP for the current session and establishes everything that governs how the remaining files are loaded and used: what CSBP is, which layer has what role, what the authority order is, which usage mode is active, and what may never be written or changed at runtime. No other file in CSBP can be understood correctly without this one being read first.
CSBP-entry-point.txt is a fixed system-definition layer. Do not modify it, rewrite it, or extend it — during runtime use, practice formation work, or at any other time. The same restriction applies to shared-best-practice-compiler.txt. Runtime practice changes belong exclusively in shared-best-practice.txt, and only after passing through the compiler path with operator approval.
The entry point establishes what CSBP is: an AI-only three-file system for storing, applying, and promoting shared operational best practices across sessions. It names the three files that make up the system and requires that no prior CSBP context be assumed. CSBP behavior must not be inferred from filenames alone.
operator instruction > AGENTS.md > local project instructions or project-local guidance > CSBP
CSBP is always the lowest-authority layer. If any CSBP item conflicts with operator instruction, AGENTS.md, or local project instructions or project-local guidance, the conflicting CSBP item is not applied.
Apply active practices from shared-best-practice.txt only 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.
Use shared-best-practice-compiler.txt only for practice formation work. Do not read it during normal runtime use. Do not use compiler logic as runtime guidance. Do not treat compiler logic as automatically active practice.
If shared-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.
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.
Do not modify CSBP-entry-point.txt. Do not modify shared-best-practice-compiler.txt. Runtime practice changes must follow shared-best-practice-compiler.txt. Do not add or revise a runtime practice without operator approval. Do not promote, deprecate, or remove a practice without operator approval.
NAMECSBP-entry-point.txtVERSION0.1OBJECTbootstrap the CSBP system for the current sessionSYSTEM DEFINITIONCSBP is an AI-only three-file system for storing, applying, and promoting shared operational best practices across sessionsCSBP includes:CSBP-entry-point.txtshared-best-practice-compiler.txtshared-best-practice.txtassume no prior CSBP contextdo not rely on chat-local inference to understand CSBPAUTHORITYoperator instruction > AGENTS.md > local project instructions or project-local guidance > CSBPLAYER ROLESCSBP-entry-point.txt: bootstrap and routing layershared-best-practice-compiler.txt: practice formation layershared-best-practice.txt: promoted runtime practice layerUSAGE MODESruntime mode: use shared-best-practice.txt to apply already promoted practicespractice formation mode: use shared-best-practice-compiler.txt for practice formation workPRACTICE FORMATION WORKevaluatenormalizerevisepromotedeprecateremoverejectENTRY RULEread this file firstdo not infer CSBP behavior from filenames alonedo not skip system-definition or layer-role resolutionENTRY DECISIONreading this file activates CSBP for the current sessionafter reading this file, load runtime modeload practice formation mode only when practice formation work is requiredREAD ORDER1. read this file2. read shared-best-practice.txt for runtime use3. read shared-best-practice-compiler.txt only for practice formation workSYSTEM DEFINITION LOCKCSBP-entry-point.txt and shared-best-practice-compiler.txt are fixed system-definition layersdo not modify themdo not rewrite themdo not extend themdo not treat them as mutable during runtime use or practice formation workRUNTIME RULEapply active practices from shared-best-practice.txt only when relevantdo not apply deprecated practicesdo not use runtime practices to override higher-authority instructionsdo not use runtime practices as policy, scope, or authority definitionsCOMPILER RULEuse shared-best-practice-compiler.txt only for practice formation workdo not read shared-best-practice-compiler.txt during normal runtime usedo not use compiler logic as runtime guidancedo not treat compiler logic as automatically active practiceEMPTY STATEif shared-best-practice.txt contains no active relevant practices, continue without CSBP runtime guidanceif no candidate practice is under discussion, do not load compiler logic into runtime behaviorCONFLICT RULEif any CSBP item conflicts with operator instruction, AGENTS.md, or local project instructions or project-local guidance, do not apply the conflicting CSBP itemWRITE RULEdo not modify CSBP-entry-point.txtdo not modify shared-best-practice-compiler.txtruntime practice changes must follow shared-best-practice-compiler.txtdo not add or revise a runtime practice without operator approvaldo not promote a practice without operator approvaldo not deprecate or remove a practice without operator approval