Your Agent Harness Has Consumers. Put Them in the Architecture Model
Thoughtworks Radar 35 puts enterprise harnesses in Assess. Map shared agent context, consumers and rollback ownership before scaling the platform.
In this analysis
- An emerging platform, not a settled standard
- Model the dependency that actually changes behavior
- Test an upgrade across two consumers
- Keep shared ownership from becoming shared delay
Build your architecture platform acceptance criteria
Related analysis
- Meta’s Thin Orchestrator Makes the Workflow an Architecture Control
- MCP’s New Roadmap Makes Agent Identity an Enterprise Architecture Concern
- Information Mapping: The Data Backbone Your EA Tool Must Support
Enterprise Agent Harness: Map the Change Impact — Vantograph