FIELD NOTE / INSTAGRAM
Three strips. One stack.
The short film, the complete written thought, and the evidence behind it.
The Instagram conversation link will follow its public release.
Three strips. One stack.
Day 103 - 2027-01-08 PT target - Instagram
Video caption
Three strips. One stack.
Agent protocol often means only the tools plane.
Interchange claims need layer names.
Hold the diagram honest.
Narration uses Eric's authorized AI voice clone.
#EricFieldNotes
Full written post / accessibility read
Picture three horizontal strips. Top strip: MCP tools and resources. Middle strip: a job start, stream, continue, cancel surface. Bottom strip: container flags or a microVM. The stack works when the seams stay visible.
In market talk, MCP becomes the default agent protocol label. Enforcement still sits in hosts, gateways, and policy. That is fine for tools. It is the wrong frame for canceling a harness job or choosing kernel isolation.
Before a vendor slide claims interchange, ask which row moved. Tool schema, job lifecycle, or substrate policy. If the answer is all of them, the slide is doing architecture by slogan.
Keep the three strips in the review board. Companion cards can illustrate the rows. The site overview film carries the same map. The durable habit is naming the layer before anyone merges the stack in a design review.
Narration uses Eric's authorized AI voice clone.
#EricFieldNotes
Four-beat scene transcript
1. Three strips. One stack.
Picture three horizontal strips. Top strip: MCP tools and resources. Middle strip: a job start, stream, continue, cancel surface. Bottom strip: container flags or a microVM. The stack works when the seams stay visible.
Visual: Do not draw one protocol arrow through all three.
2. The market label is noisy.
In market talk, MCP becomes the default agent protocol label. Enforcement still sits in hosts, gateways, and policy. That is fine for tools. It is the wrong frame for canceling a harness job or choosing kernel isolation.
Visual: Agent protocol often means only the tools plane.
3. Draw the seams before the demo.
Before a vendor slide claims interchange, ask which row moved. Tool schema, job lifecycle, or substrate policy. If the answer is all of them, the slide is doing architecture by slogan.
Visual: Interchange claims need layer names.
4. Hold the diagram honest.
Keep the three strips in the review board. Companion cards can illustrate the rows. The site overview film carries the same map. The durable habit is naming the layer before anyone merges the stack in a design review.
Visual: Name the layer before you merge the stack.