Blog
A read-only prompt is not a permission boundary
Separate task intent, exposed tools and operating-system permissions before asking an agent to inspect a project.
A checkpoint is not a verified code change
Review session history, recovery state, project changes and actual tests as four different kinds of evidence.
Accepting an AI edit is not the same as saving a file
Follow a suggested edit from proposal through acceptance, the working copy and a deliberate save.
When a local model fails, the route should stay explicit
Review the model destination and shared context before changing from a local route to a remote service.
Running, listening, reachable, healthy: four different checks
Choose the right check for a process, listener, reachable service or useful health response.
What clean Markdown extraction can still leave out
Inspect provenance, structure, warnings and truncation before relying on extracted Markdown.
Keep source provenance when web research becomes a note
Keep source links, short quotations and your own interpretation distinct in a research note.
Saved, approved, started, completed: automation states
Keep saved drafts, reviewed versions, invocations and completed runs separate across automation formats.
Retry an uncertain operation without duplicating work
Preserve request identity and inspect existing work before retrying an uncertain action.
A keyboard workflow that keeps the task in front of you
Practice finding one item, saving one useful note and returning to the task with focus intact.
What we borrowed from five documentation systems
Borrow task flow, focused page types and clean exports without copying another documentation system.