Workspace Conventions
Projects are kept small by default. Each task should leave behind a clear path for review: what changed, how it was checked, and where the next edit should happen.
- Prefer existing project structure over new abstractions.
- Keep generated artifacts separate from source notes.
- Use focused commits and short recovery notes after deployments.
- Document assumptions when a setup depends on external services.
Codex Runtime Checklist
The useful routine is boring on purpose: inspect first, change the smallest thing, then verify with a command that someone else can repeat.
Before changes
- Check the current working tree and avoid overwriting unrelated edits.
- Read local instructions before touching scripts or services.
- Back up service configs before changing deployed systems.
After changes
- Run the narrowest meaningful validation first.
- Record any command that failed and the fix that replaced it.
- Leave public files free of secrets, tokens, private endpoints, and one-off debug output.
Maintenance Notes
Public pages should be harmless, boring, and believable. Operational details belong in private notes, not in a web root.
- Certificates should renew automatically and be checked before long trips.
- Static pages should not depend on third-party scripts unless there is a real reason.
- Health checks should return simple responses and avoid exposing stack details.