This guide walks through installing the three CSBP files, wiring the entry point into yourDocumentation 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.
AGENTS.md, and verifying the setup works in a live Codex session. By the end you will have a functioning CSBP layer ready to accept its first practice formation pass whenever you need one.
Get the files
Copy Keeping them in a dedicated
CSBP-entry-point.txt, shared-best-practice.txt, and shared-best-practice-compiler.txt from the CSBP repository into your project. The recommended directory layout keeps all three files together under .codex/memories/:memories/ directory separates CSBP from other Codex configuration and makes the load order easy to audit.Bootstrap from AGENTS.md
Wire The exact bootstrap line depends on your host environment contract. What matters is that
CSBP-entry-point.txt into your .codex/AGENTS.md so a fresh Codex session reads it before using CSBP. The reference should appear near the top of the file, before any task-specific instructions:CSBP-entry-point.txt is read first, every session, before any CSBP runtime behavior is expected.Verify the entry point loads
When Codex reads
CSBP-entry-point.txt, CSBP is active for the session. No special invocation is needed beyond the reference in AGENTS.md. The entry point defines the system, establishes the authority order, sets the read order, and routes Codex into runtime mode automatically.After reading the entry point, Codex loads shared-best-practice.txt for runtime use. This happens as part of the normal session bootstrap — you do not need to ask for it separately.Check the runtime file
At this point If Codex reads the runtime file and finds no active relevant practices, it continues without CSBP runtime guidance. No active match means no forced behavior. An empty runtime file is a healthy starting state, not an error.
shared-best-practice.txt contains no active practices. That is expected — the empty state is valid. The file begins with its header block and the role and authority definitions, but no promoted practice blocks appear yet.The empty state marker from the file reads:Open practice formation (when ready)
The compiler is not loaded during normal runtime. At that point, Codex reads
shared-best-practice-compiler.txt stays out of the session until practice formation work is explicitly required.When you are ready to evaluate a candidate practice — because you have noticed a recurring pattern, a repeated mistake, or a working default that keeps being rediscovered — ask Codex to evaluate it. For example:shared-best-practice-compiler.txt and begins the formation pass: evaluating recurrence, scope, actionability, and authority fit, then proposing a normalized practice block for your review. Nothing enters shared-best-practice.txt until you approve it.What happens next
Practice Formation
Learn how the compiler evaluates candidates, what gets admitted or rejected, and how to walk a pattern through the full formation lifecycle.
Runtime Behavior
Understand how active practices are matched to current work, how the read order works, and what happens when there are no relevant active practices.
CSBP-entry-point.txt and shared-best-practice-compiler.txt are fixed system-definition layers — never modify, rewrite, or extend them. All runtime practice changes belong in shared-best-practice.txt, and only after a practice has passed through the formation path with operator approval.