Field Notes
Articles for people shipping software with agents: concrete artifacts, source pressure, and reusable operating rules.
Start here / AI Market Watch
Stateless MCP Servers Can Still Leak Shared State: A Security Contract
An HTTP endpoint might be stateless, but your MCP server might not be. Learn how shared object state in AI agent infrastructure can silently leak data across clients.
- Artifact
- A concrete file, run, screenshot, log, or decision surface anchors the argument.
- Question
- What did this artifact make clearer about shipping software with agents?
- Sources
- 3 references behind the argument.
- Payoff
- A decision rule you can reuse in your own agent workflow.
Start here: concrete artifact, source pressure, and a reusable decision rule.
Concrete artifact
The argument has to touch a file, run, screenshot, log, or decision surface.
Source pressure
Outside references are used to sharpen the claim, not to decorate it.
Reusable rule
A good post ends with a test the reader can apply somewhere else.
The archive is intentionally small. The point is not to list every AI trend; it is to make each claim inspectable.
-
Field Log 0 ReferencesScaling Agentic Infrastructure: A Solopreneur's Guide to 2026
How to architect and scale autonomous AI agents without bankrupting your 1-person company on server costs.
- Field Log 11 References
Vercel Is Not a Deployment Contract: What Auto-Deploy Silently Breaks, and How to Fix It
Push-to-deploy on Vercel feels like a contract, but it's a default. A field note on three silent breakage classes — runtime mutation, version skew, asymmetric rollback — and the explicit contracts that close them.
- Field Log 0 References
The Zero-Cost Vibecoder Stack: Building a Research Agent for Free
How to build a fully automated research and summarizing agent using 100% free APIs: Firecrawl, Groq, and ArXiv.
-
Field Log 0 ReferencesThe Agentic Software Stack for 1-Person Unicorns in 2026
We reveal the actual 2026 uncrewed technology stack and architecture we use to run a 10-person production operation entirely solo.
-
Field Log 1 ReferencesOne Command, Full Research: Building a Local Knowledge Engine with musu-crawl-ai
How a single Go binary replaces your scattered research workflow — fetching YouTube, Arxiv, GitHub, and the open web into a structured, searchable wiki.
-
Field Log 2 ReferencesImage Design Contract: Visual Assets & Generators
The definitive technical contract for generating, storing, and mapping blog post images. Do not deviate from these concepts.
-
AI Tool Note 3 ReferencesUse HTML to Review Agent Output, Not to Replace the Contract
HTML is great for reviewing complex AI agent outputs, but dangerous as a system of record. Learn why the final decision must always export back to Markdown or JSON.
- AI Market Watch 3 References
Stateless MCP Servers Can Still Leak Shared State: A Security Contract
An HTTP endpoint might be stateless, but your MCP server might not be. Learn how shared object state in AI agent infrastructure can silently leak data across clients.
-
AI Tool Note 3 ReferencesThe Work Disk Contract: Managing Artifacts in AI Coding Agents
AI coding agents generate artifacts like builds, tests, and logs. Discover why defining a strict 'Work Disk Contract' is crucial to prevent operating system failures and lost evidence.
-
Field Log 3 ReferencesVercel Is Not a Deployment Contract
A Coolify migration audit exposed two hidden Vercel assumptions: rewrites that only existed in vercel.json and a build script that depended on a Unix shell. Learn how to verify your deployment contract.