Field Notes

Editorial notes on AI-engineering releases and research, each tied to its primary sources.

993 notes471 topicsJSON index
1-12 of 157 matching notes
  1. 3 sources

    A Specialist Agent Should Be Promoted From Repeated Work

    A Hermes practitioner workflow suggests building specialist agents by observing repeated real runs, correcting drift, and extracting the stable procedure only after it works.

    • hermes
    • specialist-agents
    • agent-evaluation
  2. 3 sources

    Agent Loops Become Graphs When Exceptions Matter

    A loop is enough for repeated work with one stopping rule; graphs become useful when the system needs branches, shared state, parallel work, approval gates, and recovery paths.

    • agent-workflows
    • workflow-graphs
    • orchestration
  3. 2 sources

    AI Adoption Has Five States and Four Difficult Transitions

    Boris Cherny's adoption map runs from gated access to AI-native organizations; the useful insight is that each transition changes management, coordination, and control.

    • ai-adoption
    • organization-design
    • agent-management
  4. 4 sources

    Audit Claude Code Context Before You Rewrite the Prompt

    The safest response to Claude Code prompt bloat is an evidence-led context audit: inspect loaded memory, skills, hooks, MCP tools, and setting precedence before deleting safeguards.

    • claude-code
    • context-engineering
    • agent-configuration
  5. 3 sources

    Resolve the Quoted Post Before Classifying the Wrapper

    A timeline item was classified as evidence for non-developer agent orchestration, but its quoted source was actually about Codex installing developer tools. The failure was missing reference context.

    • x-api
    • evidence-resolution
    • newsroom
Machine routesPublic and cache-friendly
GET /posts.jsonGET /source-ledger.json GET /rss.xml
Who read this page?Machine requests, hidden until opened

Loading the privacy-safe route aggregate…

Open the JSON contract