# AI Systems Evidence Library

Twelve anonymised case files showing specific product pressure, system decisions, and the capabilities those decisions demonstrate.

- **Canonical URL:** https://vidhata.me/evidence
- **Author:** Vidhatanand V. (Vid)
- **Role:** Fractional CTO and AI Systems Architect

## 01. The assistant that had to know when not to help

**Domain:** High-stakes conversational AI

**The pressure:** Route multilingual, sensitive conversations without turning helpfulness into harm.

**The system decision:** A judgement model selects a narrow specialist response; deterministic policy controls consent, repetition, escalation, and intervention boundaries.

**What it demonstrates:** Trustworthy AI, Agent routing, Consent architecture

## 02. The marketing system that tried to explain why

**Domain:** AI-native growth platform

**The pressure:** Convert behavioural events into useful intent without allowing temporary assumptions to become permanent truth.

**The system decision:** Topics became first-class objects; memories carry source, status and confidence; recommendations expose reasons and remain reviewable.

**What it demonstrates:** Data architecture, Explainable AI, Personalisation

## 03. The camera that was allowed to stop the line

**Domain:** Industrial computer vision

**The pressure:** A false pass releases a bad unit; a false fail stops production. Camera, model, controls and operator state all matter.

**The system decision:** Controlled capture, thresholds, PLC interlocks, evidence records, operator feedback, and fail-safe states surround the model.

**What it demonstrates:** Edge AI, Fail-safe design, Industrial integration

## 04. The debate engine that planned interruption before performance

**Domain:** Multi-agent media system

**The pressure:** Create convincing multi-speaker media without collapsing research, personality, turn-taking, direction and animation into one prompt.

**The system decision:** Independent research agents, a timeline compiler, interruption logic, a show director, and deterministic render contracts divide creative judgement from production execution.

**What it demonstrates:** Multi-agent systems, Temporal orchestration, Creative tooling

## 05. The private model stack built around the machine

**Domain:** Local AI infrastructure

**The pressure:** Run useful coding, image, voice and media workloads locally on constrained Apple Silicon while retaining cloud escalation.

**The system decision:** Capability routing, quantised model tiers, reusable local APIs, reproducible job manifests, and cloud burst paths keep the stack swappable.

**What it demonstrates:** Local inference, Model routing, Cost control

## 06. The diagram pipeline that refused to confuse passing with correct

**Domain:** Deterministic visual AI

**The pressure:** Generate hundreds of SVG figures that are readable, non-leaky, and faithful, not merely valid files that satisfy superficial checks.

**The system decision:** Separate semantic planning, deterministic geometry validation, visual critique, protected findings, and human acceptance into explicit gates.

**What it demonstrates:** Evaluation systems, SVG pipelines, Quality governance

## 07. The planner that could explain every recommendation

**Domain:** Evidence-led quantitative system

**The pressure:** Produce culturally useful plans across age, pregnancy stage, nutrition, safety, allergens, texture, rotation and real household constraints.

**The system decision:** Versioned knowledge, hard eligibility rules, auditable scoring, provenance, golden cases, and explicit fallbacks precede generative presentation.

**What it demonstrates:** Decision systems, Knowledge modelling, Safety rules

## 08. The six-hour job that did not lose five hours

**Domain:** Durable creative workflow

**The pressure:** Long AI jobs fail across machines, providers and steps; naïve orchestration restarts expensive work and loses artefacts.

**The system decision:** Idempotent stages, checkpoints, resumable queues, cancellation, retry policy and first-class artefacts make interruption survivable.

**What it demonstrates:** Durable execution, Queue design, Resumability

## 09. The voice loop that treated latency as product behaviour

**Domain:** Realtime voice platform

**The pressure:** A conversational interface must react before a complete transcript while avoiding accidental interruption and incoherent state.

**The system decision:** Streaming recognition, partial-intent confidence, barge-in policy, turn state, cancellable synthesis and traceable fallbacks form one loop.

**What it demonstrates:** Realtime systems, Voice UX, State machines

## 10. The product that did not hard-code its intelligence

**Domain:** Capability-first software

**The pressure:** AI products inherit vendor churn when product logic, tool use and provider-specific APIs are fused together.

**The system decision:** Typed capability contracts, provider adapters, evaluation fixtures, budgets and fallbacks isolate product behaviour from model vendors.

**What it demonstrates:** Platform design, Provider abstraction, Testability

## 11. The studio that turned a narrative into inspectable production state

**Domain:** Computational-media pipeline

**The pressure:** Automated media loses coherence when story, shots, assets, voice, motion, music and export are generated as disconnected outputs.

**The system decision:** A canonical timeline links narrative beats, assets, performance cues, provenance, render jobs and QC into an editable production graph.

**What it demonstrates:** Media systems, Asset provenance, Pipeline design

## 12. The agent platform whose actions could be reconstructed

**Domain:** Product operating system

**The pressure:** Multi-agent products become unmanageable when decisions, tool calls, costs, approvals, artefacts and failures disappear into logs.

**The system decision:** Append-only events, correlation IDs, addressable artefacts, approvals, health views and stable APIs expose operational state to people and future interfaces.

**What it demonstrates:** Observability, Agent operations, Human control

## Work with Vid

Start with the actual technical pressure: [bring the problem](https://vidhata.me/hire).