Before a workflow touches customers, business data, or money, you should be able to see what enters, where a person decides, what gets recorded, and how work continues if automation stops.
Free 30-minute Automation Review. Leave with one mapped workflow bottleneck, one human approval point, and one practical next step.
CONTROL PATH
VISIBLE BY DESIGN
01Signal
source attached
02Draft
draft prepared
03Approve
human approval
04Act
scoped action
05Log
result recorded
AI prepares; a person approves; the system records the result.
WHAT YOU CAN INSPECT / 04
ILLUSTRATIVE · SYNTHETICFour practical questions, answered below.
Connected to its public source and excerpt below.
A workflow handoff is under review.
Pattern grounded in an internal Radar workflow.
A synthetic excerpt demonstrates source attachment; it is not an actual quote, a claim of signal accuracy, or a business outcome.
Prepared work waits for review below.
REVIEW ITEM
Context ready for review
The system prepares a recommendation and its source trail. A person decides whether anything should happen next.
Pattern grounded in an internal approval-queue workflow.
Synthetic content shows the control pattern; it is not a customer record or live draft.
A read-only mirror surfaces drift below, never a silent rewrite.
Observation is separated from the source system. Drift becomes a review item, not a silent overwrite.
Pattern grounded in an internal marketing sync view.
Qualitative sample states replace live run data, tables, and operational counts.
Discloses its role, its bounds, and the handoff below.
AI assistant
POWERED BY AI
Pattern grounded in a public production AI assistant.
The sample shows disclosure and handoff controls, not private prompts or filtering rules.
Governance across all four patterns
Every pattern is working-system evidence, sanitization complete. Permission is internal-approved except the disclosed AI handoff pattern, which is public-approved.
Our own approval queue
Our product · sample data
Every action can be logged. A record includes the prepared item, approval state, result, timestamp, and owner.
TRUST LAYERS / 03
Current website facts, delivery defaults, and workflow-specific production evidence are different kinds of trust. The status text on every row keeps those boundaries visible.
STATUS LEGEND · TEXT AND COLOUR
01
Observable boundaries in the public website shipped today.
This site shows public service content and examples labelled as illustrative and synthetic. It does not prove that a production workflow is live.
Analytics and advertising measurement are separate choices. A relevant vendor library loads only after you grant that choice.
The Automation Self-Assessment runs in the browser. Its V1.2 answers and result are not submitted; the dormant, default-off legacy capture foundation is disconnected from the interface.
The Contact page has no form or onsite submission path. It captures nothing on the page.
Microsoft Bookings opens on Microsoft’s site. The email link opens your email app, and nothing is sent unless you choose to send it.
The current Privacy notice documents the website, Self-Assessment, consent, Bookings, Teams, and email boundaries.
Read the current Privacy notice02
Delivery defaults; implementation details vary by workflow, tools, and boundary.
Source and context stay with prepared work by default; exact fields and storage vary by workflow.
A person approves before an external action touches customers, data, or money; the role and escalation path vary by workflow.
Credentials are scoped to the smallest action needed; exact permissions and rotation ownership vary by workflow.
Every action can be logged; the actual log fields, retention, and observability design vary by workflow.
Stop conditions and a manual fallback are part of delivery by default; exact triggers and recovery steps vary by workflow.
Workflow documentation, a runbook, an access inventory, and handover are included by default; transferability and exit details vary by workflow.
03
This label names the required evidence gate, not a current certification or a universal implementation claim. Unknown or configuration-dependent facts stay variable until verified.
Before production, verify the selected model and vendor, plus the applicable training setting, in workflow-specific documentation.
Before production, verify what data enters, its categories, where it moves, and the purpose for each processing step.
Before production, verify the subprocessors that apply to the workflow and the narrow purpose each one serves.
Before production, verify actual retention settings, deletion paths, and the owner responsible for review.
Before production, verify the workflow’s hosting, residency, and data-location facts without inferring them from architecture or intent.
Before production, verify the exact credential permissions, permitted actions, boundaries, and rotation owner.
Before production, verify the approval owner, gated actions, review context, and escalation path.
Before production, verify the logs and observability that actually exist, including fields, access, retention, and review ownership.
Before production, verify stop conditions, the manual fallback route, recovery steps, and the responsible person.
Before production, verify ownership, transferability, handover materials, operating access, and the exit path.
QUESTIONS TO VERIFY / 08
The answer is specific to each workflow — verify it before production. Not certification, legal advice, or a universal infrastructure claim.
What enters the workflow, and where does it move?
Why does each external service receive data?
What may be retained, and for how long?
What is the smallest permission the workflow needs?
Who decides before an external action happens?
What evidence remains after a decision?
How does work continue when automation stops?
What can the client operate and transfer?
Mladen Ranković · AgenticMotion by Qualiteh
13+ years industrial quality & operations · VDA 6.3:2023 Process Auditor (VDA QMC) · IATF 16949 Internal Auditor · Lean Six Sigma Green Belt
AUTOMATION REVIEW
We map the bottleneck, mark the decision point, and name one practical next step.
Free 30-minute review. Leave with one mapped workflow bottleneck, one human approval point, and one practical next step.