Check the work around an AI-generated change
An AI tool can produce good code against the wrong project. This field note explains how to check the target, permission and result before treating a task as finished.
Evidence Harness · August 2026
Writing
Practical notes on search and AI-assisted work
Explore how to choose useful website improvements, work with AI tools, and check the result. Use the linked essays, analyses and project resources to go deeper.
For visual analyses, implementation stories and practical methods, explore Insights →. Writing collects essays and reference destinations; Insights develops the analytical stories.
Themes
Start with a problem you recognize
Practical questions from search strategy, implementation and hands-on experiments.
Help readers find the next useful page
Use automation to suggest links, then check whether the destination answers the reader's next question.
Content operations · Internal links
Understand what search and AI discovery data can show
Keep crawling, search visibility, citations, and visits separate. State which source and observation window support each finding, and what remains unknown.
Measurement · Evidence limits
Direct AI-assisted work and notice when it needs you
Give tools a bounded task, inspect the proposed change, and verify delivery. Explore visual and optional audio cues that help present system events.
Implementation · Human review
Articles
Essays and project references
Explore the original destinations. Project homepages are labeled separately from articles.
The Signal Contract
Why agent work needs a Signal Contract plus multiple renderers so humans can notice without inspecting full traces.
Read at vibenet.ai →Constitutional cybernetics: governing what agents publish
How a governance layer decides what autonomous publishing systems are permitted to say.
Project at constitutionalcms.com →