FIELD NOTE / X
UHP puts the unit on a job.
The short film, the complete written thought, and the evidence behind it.
The X conversation link will follow its public release.
UHP puts the unit on a job.
Day 105 - 2027-01-10 PT target - X
Video caption
UHP puts the unit on a job. Do not collapse those interfaces. IDE plug-in is not the same as product job drive. Watch conformance, not marketing. Narration uses Eric's authorized AI voice clone. #EricFieldNotes
Full written post / accessibility read
UHP, draft dated September twelfth twenty twenty six, puts the unit of exchange at a job or task. A product picks a harness, starts work, streams progress, continues via a prior response, cancels, and gets files back. That is a product to harness contract. It is not a model API.
Model APIs give you a turn. UHP shaped surfaces give you a running agent with its own tools and session. Products want a job surface, not only a token stream. That pattern shows up in managed harness APIs and IDE harness plug-in surfaces alike.
JetBrains framing of Agent Client Protocol plus a registry is an IDE plug-in surface for third party harnesses. UHP is how a product drives a harness job. Long term coexistence outcomes are untested. Do not collapse them into one protocol box either.
UHP is still a draft. The thing to watch is a conformance suite across vendors, not marketing interchange claims. Production conformance is a watch item, not a fact I can claim from the draft text alone.
Narration uses Eric's authorized AI voice clone.
#EricFieldNotes
Four-beat scene transcript
1. UHP puts the unit on a job.
UHP, draft dated September twelfth twenty twenty six, puts the unit of exchange at a job or task. A product picks a harness, starts work, streams progress, continues via a prior response, cancels, and gets files back. That is a product to harness contract. It is not a model API.
Visual: Not a model turn. A running harness task.
2. Model APIs give turns. Jobs give sessions.
Model APIs give you a turn. UHP shaped surfaces give you a running agent with its own tools and session. Products want a job surface, not only a token stream. That pattern shows up in managed harness APIs and IDE harness plug-in surfaces alike.
Visual: Do not collapse those interfaces.
3. ACP is adjacent, not identical.
JetBrains framing of Agent Client Protocol plus a registry is an IDE plug-in surface for third party harnesses. UHP is how a product drives a harness job. Long term coexistence outcomes are untested. Do not collapse them into one protocol box either.
Visual: IDE plug-in is not the same as product job drive.
4. Watch conformance, not marketing.
UHP is still a draft. The thing to watch is a conformance suite across vendors, not marketing interchange claims. Production conformance is a watch item, not a fact I can claim from the draft text alone.
Visual: Draft status stays on the label.