SOLUTION WORKFLOWS
From an idea
to work you can trust.
Start read-only with an estate assessment, then give business, engineering, security, and operations a shared process for moving agent initiatives forward.
START READ-ONLY
See your whole agent estate
in 14 days.
Grant a read-only role, receive a structured picture of every agent, runtime, gateway, tool and owner, and decide the first bounded workflow with evidence in hand.
What you grant
- A read-only role in your cloud account, created by you.
- List and Get permissions only.
- Explicit denies on invoke, memory contents, sessions and tokens.
- Revocable at any time; no credentials stored by the platform.
YOUR ESTATE / 14 DAYS
What the read-only sync and Catalog produce
What happens next
- 01Review the report with your platform, security and product owners.
- 02Choose the first bounded workflow and its evidence requirements.
- 03Continue into the design-partner programme, or stop; the role is yours to revoke.
Deliverables are limited to what the read-only sync and Catalog produce today: agents, runtimes, gateways, MCP tools, memory and policy engines by account and runtime; owners assigned or unassigned; policies and gateways; agents without a linked specification; approval records present.
01 / BUSINESS TO ENGINEERING
Start with a decision-ready plan.
Give an agent initiative a clear scope, accountable owners, and evidence requirements before implementation.
Example workflowA change review agent turns internal requests into proposed engineering changes.
Start with
Business objective and current process
Policies and data classifications
Expected workload and budget assumptions
- 01
Structure the objective into requirements, owners, dependencies, and acceptance criteria.
- 02
Identify knowledge sources and the information the agent may retain.
- 03
Draft the specification, tool boundaries, harness, and human decision points.
- 04
Map documentation requirements to owners and verification methods.
- 05
Review threats, access needs, and cost scenarios before committing to delivery.
Leave with reviewable evidence
Named owners agree on the scope, acceptance criteria, and unresolved risks.
02 / SPECIFICATION TO PULL REQUEST
From approved spec to pull request.
Give the Coding Expert an approved specification and receive a branch, tests and a pull request that your engineers review and merge.
Example workflowA team approves a Blueprint specification, starts a coding run against its repository, and reviews a pull request that reads as if one of its own engineers wrote it.
Start with
Approved specification version; Jira work items optional
Repository, existing or new, connected with a token
Limits from Build settings: budget, turns, duration, concurrency
- 01
Bootstrap one isolated session in the platform account and check out the repository.
- 02
Plan the change from the specification and any linked work items.
- 03
Implement the change in the persistent workspace.
- 04
Verify the change by running the tests in the workspace, retrying within the configured limits.
- 05
Publish a branch and a neutral pull request, then record the run.
Leave with reviewable evidence
A named reviewer merges; the Coding Expert never merges.
03 / ENGINEERING TO RELEASE
Release with a complete evidence trail.
Bring tool access, agent behavior, security decisions, and release evidence into one reviewable process.
Example workflowA tool-using agent reads project information and prepares changes for human approval.
Start with
Approved design and tool definitions
Skill, knowledge, and memory policies
Evaluation cases and release criteria
- 01
Define the tools and skills available at each workflow step.
- 02
Specify scoped access and actions that require explicit approval.
- 03
Review untrusted-input, tool-misuse, and information-retention threats.
- 04
Evaluate expected behavior, boundary cases, failures, and recovery.
- 05
Review results, security findings, documentation, and remaining exceptions.
Leave with reviewable evidence
Every acceptance criterion is backed by evidence or an accepted exception with an owner.
04 / OPERATIONS TO IMPROVEMENT
Keep long-running work accountable.
Connect daily operations to the evidence needed for dependable recovery and controlled improvement.
Example workflowA workflow gathers context, prepares a proposal, waits for review, and resumes after a decision.
Start with
Approved workflow and operating limits
Recovery rules and escalation paths
Evaluation baseline and security procedures
- 01
Define waiting, retry, recovery, and stopping behavior.
- 02
Inspect execution, tool activity, failures, and resource consumption.
- 03
Triage security findings against permissions and the threat model.
- 04
Route exceptions to the responsible owner and record the action.
- 05
Turn findings into evaluations and revisions to skills, specifications, memory rules, or controls.
Leave with reviewable evidence
Material changes return through the appropriate design, security, and release reviews.
START READ-ONLY
Start with a 14-day
estate assessment.
Grant a read-only role, see your whole agent estate, and decide the first bounded workflow with evidence in hand. Nothing runs in your accounts.