AI-Assisted Delivery
The AI drafts the configuration; the engineer reviews and approves. X10 serves as the enabler behind the approach.
The AI-assisted delivery process. The AI lets a domain expert describe an outcome (e.g., "Build a pipeline to drop null fields from Palo Alto firewall logs and route to S3"), and the system generates the required configuration.
The human expert reviews the dry run. If it's correct, they approve it.
This allows us to deliver complex, customized solutions faster while maintaining the high quality and accountability our customers expect.
The AI as drafter
The AI does the mechanical mapping of intent to configuration. It drafts the work.
The engineer as reviewer
A senior VisiCore consultant reviews the drafted configuration against the customer's actual architecture and security posture.
The ROI (illustrative, not measured benchmarks)
From Andrew's whitepaper. Actual times depend on environment complexity and review depth.
| Operation | GUI baseline | AI-Assisted | Time saved |
|---|---|---|---|
| Building a pipeline | 3–6 hours | 30–60 min | ~85% |
| Configuring a datasource | 1–2 hours | 10–15 min | ~85% |
| Building dashboards | 2–4 hours | 30–60 min | ~80% |
| Health check across worker groups | 2–4 hours | 10–20 min | ~85% |
| Root-cause correlation | half a day+ | 15–30 min | ~90% |
Per-engineer recovered capacity: 4–6 hours/week, 200–280 hours/year. These are directional until we publish measured numbers from actual engagements — which is the single highest-leverage near-term task, and it needs no customer.
The control loop (why experts don't get slower)
The METR study found experts got slower by over-trusting AI output. This workflow makes that failure mode structurally hard — the expert is the gate. See the full evidence.
Work assignments
Owners and sequence only — task detail lives in the internal project plan (Epic E3, E1.T4).
| Stream | Owner |
|---|---|
| Core integration and API hardening | Andrew |
| REST wrappers for X10 use | Paul |
| Background-job scheduling (proactive analyses) | Andrew + Paul |
| Customer documentation | Andrew + Jacob |
The compliance gate
External deployment is blocked by customer compliance, not the tech. It cannot ship at Deloitte/World Pay until consent and data-boundary questions are answered. The internal-margin use is not gated by this and can proceed now. Full detail: The compliance gate.