| author | Alan Dipert
<alan@tailrecursion.com> 2025-12-28 02:39:03 UTC |
| committer | Alan Dipert
<alan@tailrecursion.com> 2025-12-28 02:39:03 UTC |
| parent | 7a4d115b360b11db0e417ce24783a9630d989423 |
| AGENTS.md | +1 | -0 |
| md/Coherence.md | +2 | -0 |
diff --git a/AGENTS.md b/AGENTS.md index 00ad733..f8ce466 100644 --- a/AGENTS.md +++ b/AGENTS.md @@ -17,6 +17,7 @@ Welcome! This document describes how automated helpers should operate when worki - Ensure `tools/mdlink2html.awk` and build helpers continue to support wiki-style intra-site links. - Keep the generated `out/Index.html` in sync; the `tools/gen_index.sh` helper runs automatically from `make`. - Keep updates idempotent: don’t delete generated output or vendor directories unless instructed. +- When in doubt about improvements, have the AI tour the site like a new reader (browser pass, no edits) and capture TODOs for confusing spots or visual glitches before proposing changes. ## Blog Post Style Guidelines diff --git a/md/Coherence.md b/md/Coherence.md index 8006e22..abd2e12 100644 --- a/md/Coherence.md +++ b/md/Coherence.md @@ -22,6 +22,8 @@ The biggest gains come from **non-code artifacts** that lock intent in place bef Codex needs the same feedback loop I have. If I’m building a site, it should see the browser. If I’m building a CLI, it should run in a close match of the target environment. If I’m stuck manually validating everything, I’ve kept myself in the loop and throttled iteration. +I also send Codex through the site as a new reader to collect rough edges and TODOs—confusing flows, broken links, odd formatting—before touching content. That keeps its work queue self-filling instead of relying on my memory. + Commits record outcomes, not dead ends. I start and end work by logging an issue in `git-bug` (or similar) so failed approaches and constraints live beside the code. Without that memory, Codex will “fix” problems by creating new ones forever. The failure smell is simple: Codex keeps producing more work for me instead of less. When that happens, stop generating code, rebuild the artifacts, and restore alignment. Coherence keeps intent, artifacts, and execution in lockstep—humans set direction and taste; Codex supplies execution and endurance.