FIELD NOTE / INSTAGRAM
A turn card versus a job card.
The short film, the complete written thought, and the evidence behind it.
The Instagram conversation link will follow its public release.
A turn card versus a job card.
Day 105 - 2027-01-10 PT target - Instagram
Video caption
A turn card versus a job card.
Sandbox menus sit beside the job, not inside MCP.
Same harness, different caller.
Keep draft visible.
Narration uses Eric's authorized AI voice clone.
#EricFieldNotes
Full written post / accessibility read
Draw two cards. Left card: prompt in, tokens out. Right card: start, stream, continue, cancel, files back. The right card is the job contract shape. UHP drafts that shape. Keep draft on the badge.
When a vendor ships a managed harness with sandbox partner options, they are selling a job surface plus substrate choices. That is useful product surface and also an integration tax if every experiment picks a different substrate.
An IDE hosting a full harness through a client protocol is a different door than a product API driving a job. Both can be valid. Neither replaces naming the layer.
Until a conformance suite exists, treat interchange claims as marketing. Prefer additive, responses compatible task surfaces when exposing agents to products.
Narration uses Eric's authorized AI voice clone.
#EricFieldNotes
Four-beat scene transcript
1. A turn card versus a job card.
Draw two cards. Left card: prompt in, tokens out. Right card: start, stream, continue, cancel, files back. The right card is the job contract shape. UHP drafts that shape. Keep draft on the badge.
Visual: Only one has cancel and collect.
2. Managed harnesses productize the right card.
When a vendor ships a managed harness with sandbox partner options, they are selling a job surface plus substrate choices. That is useful product surface and also an integration tax if every experiment picks a different substrate.
Visual: Sandbox menus sit beside the job, not inside MCP.
3. IDE plug-in is another door.
An IDE hosting a full harness through a client protocol is a different door than a product API driving a job. Both can be valid. Neither replaces naming the layer.
Visual: Same harness, different caller.
4. Keep draft visible.
Until a conformance suite exists, treat interchange claims as marketing. Prefer additive, responses compatible task surfaces when exposing agents to products.
Visual: Interchange waits on conformance.