Flow and authority
Inspect orchestration, tool permissions, identity boundaries and human approval. Define what the agent may do and what the application must enforce.
Agentic applications · 01 · The problem and the decision
Agentic architecture reviewWhat stops the agent calling a tool it was not given?
The demo works. The production decision is still stuck on reliability, permissions, ownership or cost. Turn those questions into a design your engineering team can build and operate.
For ISVs adding agents and enterprise AI teams whose pilot has stalled before production.
3–4 weeks elapsedOne agreed agent application and its priority use caseA named architect accountable
02 · What we check
Agree the scope. Inspect the evidence.
We agree the priority architecture questions and depth, then trace the relevant decisions and actions. The review tests those choices against the use case and constraints you actually have.
Quality and failure
Read traces and evaluation material. Review retries, timeouts, fallback, state and the evidence needed to judge a change.
Operating model
Review data boundaries, observability, dependencies and available latency and cost measurements. Separate measured behaviour from estimates.
What we need from you
- The agreed use case, architecture or prototype, relevant code and representative traces.
- Access to the application owner and the people responsible for security and operations.
- Known data, deployment and integration constraints, plus available evaluation examples.
Scope and boundaries
- A production build, broad model benchmark, legal assessment and detailed implementation-ticket engineering are separate work.
- The proposal identifies the agent workflow, integrations and review questions included. Additional use cases and integrations require an agreed extension.
03 · What you get
A decision you can act on.
- A target architecture outline with responsibilities and trust boundaries for the priority use case.
- A decision record for the agreed architecture questions.
- Recommended evaluation and observability checks, with unknowns recorded.
- Prioritised build actions and a go/no-go recommendation for the agreed next step.
04 · Relevant work and a sample
See the thinking behind the review.
A bounded flow for network operations
For Nokia, working with a Tier-1 Nordic operator, Atsky designed the situation-enrichment agent as a four-step flow: retrieve, annotate, recommend and format. The NOC retains the decision; tracing and in-tenancy inference form part of the design.
Engineering choices you can inspect
Atsky Voice is an Atsky demonstration developed in partnership with Telnyx. It provides an example of session boundaries, tool use and disclosure in an agent application. It is not evidence that a customer bought this review or achieved a compliance outcome.
05 · Duration and price
A defined engagement. An agreed scope.
From €10,000Starting price, excluding VAT
From €10,000, excluding VAT. We quote a fixed fee after agreeing the application, workflow and integration inventory, access and review depth. The proposal confirms the elapsed delivery window around the evidence and people required. Implementation, detailed ticket engineering and additional scope are separate.
We agree the included scope, deliverables and fixed fee in the proposal before work starts.
- Duration
- 3–4 weeks elapsed
- Base scope
- One agreed agent application and its priority use case
- Your data
- Read-only access, in a workspace that holds only your engagement. If your policy requires it, we work with EU-only processing and zero data retention. Any extra cost is named in the proposal.
Our own AI-assisted tooling collects evidence and drafts findings; a named architect checks and signs them. How we work and handle data →
06 · Request a working session
Start with the question you need to resolve.
In 45 minutes, walk through the pilot, what blocks production and a relevant architecture example. Agree which design decision the review needs to resolve.
This requests a 45-minute conversation. We confirm a suitable time with you.
Is the immediate blocker engineering evidence for your DPO or counsel? Explore the AI engineering-readiness review.