Kinetix: An Agent Harness Inside a Clinical System
Sixty tools, twenty-nine of them mutating, inside a system holding injury records. The Go that enforces one rule: the agent inherits the caller.
Biomechanics from Video08
Subject · 7 posts
Sixty tools, twenty-nine of them mutating, inside a system holding injury records. The Go that enforces one rule: the agent inherits the caller.
Biomechanics from Video08
Store agents as versioned, validated rows instead of writing them as classes, and rollback, diffs, audit, teams and lessons come free. Here is the bill.
Agent Harness04
Three measured refusals in a markerless movement pipeline, the gaps that are still open, and why a clinician should prefer software that says not measured.
Biomechanics from Video07
Read/write enforcement, principal scoping, approval gates, sandboxes and budgets: five safety properties, every one enforced in code, not in a prompt.
Agent Harness03
Why intent-named operations beat database schemas, auto-generated OpenAPI specs and one-command MCP servers when you hand an application to a model.
Agent Harness02
The five parts of an agent harness: capability surface, meaning, policy, approval and audit. Only two of them are about power.
Agent Harness01
A chatbot that is wrong is embarrassing. An agent that is wrong took an action. The security of a tool-calling agent is the security of what you connected it to.
LLM and Agent Security03