CSBP gives recurring guidance a smaller, reviewable layer instead of forcing everything into the host contract.
AI-only protocol kit
Promoted runtime layer
Three-file structure
Shared practice that stays usable.
CSBP gives recurring Codex guidance a proper home: explicit, reviewable, and operator-approved.
It keeps good practice alive without dumping everything into AGENTS.md or leaving it to chat history.
Why it stays useful
Keep recurring guidance in reach.
The problem is simple: useful operating habits keep getting rediscovered, then lost again. CSBP gives them a controlled place to live so they can stay available across Codex sessions without becoming automatic sprawl.
Without CSBP
Signal drops back into chat.
Good guidance gets repeated manually because it never receives a stable runtime home.
With CSBP
Shared practice stays available.
Recurring rules stay readable, inspectable, and easy to carry across future sessions.
What changes
Useful guidance stops relying on luck.
You get a narrow shared layer for habits that matter, instead of hoping they resurface later.
How it stays controlled
Built in three files, held in order.
CSBP works because it separates activation, runtime practice, and formation logic. The system stays understandable because each file has one job and the authority order is explicit from the start.
Core files
CSBP-entry-point.txt
Turns the system on, sets authority order, and routes the correct mode.
shared-best-practice.txt
Stores promoted runtime guidance only. Active entries apply when relevant.
shared-best-practice-compiler.txt
Evaluates, rewrites, promotes, deprecates, rejects, and removes candidate practices during formation work.
Authority order
CSBP stays below the host contract.
How practice becomes live
Candidate first. Runtime later.
CSBP does not turn every good idea into a permanent rule. It gives candidate practice a review path first, then makes promotion an explicit operator decision.
A recurring issue, omission, or pattern enters discussion.
Usefulness, recurrence, scope, and overlap with stronger rules are checked.
The idea is rewritten into a short, preventive, runtime-ready instruction.
The operator decides whether the candidate belongs in runtime.
The practice lands in the runtime file with a stable final form.
Where it helps
Useful when repeated work keeps slipping away.
CSBP is most useful when an environment keeps producing the same good operational guidance, but has no clean place to keep it reusable. It fits best where guidance needs review, durability, and a smaller blast radius than rewriting the host contract.
Long-lived sessions
When chat keeps carrying too much weight.
Repeated lessons stop living as scattered reminders and start living in a shared layer.
Shared environments
When the same behavior should survive across sessions.
You get a stable runtime reference without turning the host contract into a policy document.
Prompt hygiene
When AGENTS.md should stay narrow.
The host contract stays focused while recurring best practice gets a place designed for review and promotion.