Identity
Who is the user?
HARNESS ONE / ENTERPRISE
Move work forward.
Keep control of how it happens.
Define what agents can access, which actions they can take and when your team needs to approve. Build those boundaries into the environment where the work happens.
Discuss your requirementsAgent
Which role does it serve?
Data
What can it access?
Actions
What can it execute?
Approval
Who must authorize?
Audit
What is recorded?
01 / ACCESS & AUTHORITY
Know who can do what.
An agent’s authority follows the business context, the user and the action. Define the scope before connecting the capability.
- Identity and role
Establish who is using the agent and which business role it serves.
- Data and action permissions
Specify the information it may access and the operations it may execute.
- Approval boundaries
Identify decisions and actions that require a person’s review or authorization.
02 / BUSINESS CONTEXT & SYSTEMS
Make the business explicit.
Your definitions, rules and processes shape how an agent interprets information and operates through systems.
- Meaning and calculation
Agree business vocabulary, metric definitions and deterministic calculation requirements.
- System capabilities
Map the sources, connectors and execution tools required for the agent’s role.
- Workflows and exceptions
Define how work progresses, when it stops and where an exception is escalated.
03 / EVALUATION & OPERATIONS
Keep the outcome in view.
Evaluate the agent against the work it is expected to perform and use operational evidence to improve the environment.
- Business scenarios
Define normal cases, edge cases and expected outcomes with the teams who own the work.
- Execution visibility
Follow actions, tool use, quality, latency, cost and failures.
- Change and ownership
Review new versions, test for regressions and establish responsibility for ongoing operation.
THE OPERATING STANDARD
Reliability is part
of the environment.
Governed
Explicit permissions, policies and approval boundaries define how agents work.
Grounded
Business context and logic are represented explicitly in the operational environment.
Evaluated
Behavior is tested against business scenarios and their expected outcomes.
Observable
Tool use, actions, quality, cost and failures can be traced and improved.
WORKING WITH YOUR TEAMS
Start with a defined
operating scope.
Business owners and technical teams bring complementary requirements to the same environment.
Map the work
Define the business role, expected outcomes, relevant information and systems.
Define the environment
Identify the Harness, domain logic, capabilities, permissions and evaluation scenarios.
Agree the operating requirements
Review deployment constraints, data handling, integration scope and responsibilities together.
BUILT AROUND YOUR BUSINESS
Bring your operating requirements.
Start a conversation about your business, systems and the responsibilities you want agents to take on.