Discussion about this post

User's avatar
G Froede's avatar

"Workflow design becomes authority design" is the most useful line here, and the read / recommend / draft / execute split is where I'd start. In a construction office the line is clear in practice: an agent drafting an RFI or a daily site report is cheap to review, but the moment it sends that document it becomes a contractual record, so the approval belongs at the send, not at the draft. Your Agent Visibility Gap shows up there too — a "task complete" summary is useless if it doesn't say which quantity, date or scope item the agent changed along the way. When approvals scale with the risk of the action, who assigns the risk tier in your view: the agent classifying its own next step, or a fixed list a human owns — given that self-classification is itself one of the judgments we're trying to bound?

2 more comments...

Ready for more?