Specified
Interfaces, permission model, evidence requirements, failure modes and the conformance checks a release must pass.
Workspace & infrastructure · Prototype
Capabilities with boundaries attached.
Each capability in EnterpriseHarness is specified as a contract: scope, permission, evidence and failure behaviour.
01
The five contracts
Numbered for reference; the order is not a priority.
- 01. Enterprise and agent workspaces
-
Implemented through one permission model that applies to the human interface and the machine interface alike.
Scope is attached to the capability, not to the caller, so delegation does not widen it silently.
Surfaces REST · MCP · CLI
- 02. Multi-agent orchestration and delegated tasks
-
Specified with its own failure modes, limits and evidence requirements before it is exposed to an agent.
Operators can inspect the capability before it runs and review its record afterwards.
Surfaces REST · MCP · CLI
- 03. Execution budgets and checkpoints
-
Implemented through one permission model that applies to the human interface and the machine interface alike.
The same capability is reachable from the application, the API and the agent surface without a second implementation.
Surfaces REST · MCP · CLI
- 04. Policy-driven approvals and supervision
-
Specified with its own failure modes, limits and evidence requirements before it is exposed to an agent.
Operators can inspect the capability before it runs and review its record afterwards.
Surfaces REST · MCP · CLI
- 05. Application, plugin and workflow runtime
-
Implemented through one permission model that applies to the human interface and the machine interface alike.
Scope is attached to the capability, not to the caller, so delegation does not widen it silently.
Surfaces REST · MCP · CLI
02
What is specified, and what is not
A capability in a specification is not a shipped feature.
Not claimed
Running deployments, measured performance, third-party certifications or integration approvals.