https://www.kobutra.com/notes/On building systems, running the work, and using AI in practice.en-ushttps://www.kobutra.com/notes/check-an-agents-work/A small regression test, an acceptance record and a review routine for separating finished code from a convincing completion report.https://www.kobutra.com/notes/check-an-agents-work/https://www.kobutra.com/notes/review-the-change/Follow a bug through two callers, reject a partial fix, and test the correction where the behavior belongs.https://www.kobutra.com/notes/review-the-change/https://www.kobutra.com/notes/shared-project-context/Keep one small project entry point, connect each client explicitly, and check the files and facts a fresh session retrieves.https://www.kobutra.com/notes/shared-project-context/https://www.kobutra.com/notes/before-automating/A worked example and a copyable worksheet for deciding whether a recurring task needs a script at all.https://www.kobutra.com/notes/before-automating/https://www.kobutra.com/notes/audit-your-stack/Check whether the project already solves the problem, using a read-only inventory and one concrete acceptance test.https://www.kobutra.com/notes/audit-your-stack/https://www.kobutra.com/notes/what-a-rule-is-protecting/A practical way to review a team rule before enforcing it, making an exception, or getting rid of it.https://www.kobutra.com/notes/what-a-rule-is-protecting/https://www.kobutra.com/notes/youre-absolutely-right/A paired-prompt exercise for telling a useful correction from an answer that merely follows your confidence.https://www.kobutra.com/notes/youre-absolutely-right/https://www.kobutra.com/notes/why-i-built-hydrant/Building another issue tracker doesn't require pretending the one I like is broken. It does require being honest about which decisions I want to own.https://www.kobutra.com/notes/why-i-built-hydrant/https://www.kobutra.com/notes/memory-needs-sources/Audit one remembered claim by tracing its source, separating inference from evidence, and checking what is still true before correcting it.https://www.kobutra.com/notes/memory-needs-sources/https://www.kobutra.com/notes/teach-a-procedure-not-a-biography/Turn a repeated support-writing task into a small Hermes skill, with explicit inputs, stopping rules and human checks for reuse.https://www.kobutra.com/notes/teach-a-procedure-not-a-biography/https://www.kobutra.com/notes/a-timeout-is-not-a-failure/Run a small retry experiment that separates a lost reply, a duplicate command and an edit based on an old version.https://www.kobutra.com/notes/a-timeout-is-not-a-failure/https://www.kobutra.com/notes/read-only-is-a-permission/Test an integration's authority directly: a read-only connection should fail to write even when the caller asks it to.https://www.kobutra.com/notes/read-only-is-a-permission/