TAG
#Harness
2026-10 2 posts
-
Every Organization Needs an Agent Runtime
Part 2 of 4: why even air-gapped organizations will run a general-purpose agent runtime on work PCs, and how to connect it to internal models and tools.
-
Separating the Worker from the Tool
Part 1 of 4: work spans products, so general-purpose agents become workers and products their tools. What to expose, and where software keeps its value.
2026-05 4 posts
-
Requirements as Latent State
A requirement is a latent state and the user's sentence a noisy observation. What follows for EARS, spec-driven development, harnesses, and when to ask.
-
Skill and Harness
A skill compresses how to behave; a harness organizes how to tell if that behavior nears the goal. Why the two still contain each other in practice.
-
Harness as Environment
A vector DB full of experience does not make an agent adapt. That takes a harness: what may change, how success is judged, how far a failure rolls back.
-
Weights, Prompts, Codes as Parameters
If agent problems are POMDPs, weights, prompts, and code are parameters at three layers of one policy space. Why the layers opened in that order.
No matching posts.