Vision Vault SystemsWhere trust meets technology

Proof of work

Six builds. Different worlds, same standard.

Enterprise and federal engagements are shown with real metrics and anonymized clients, per engagement agreements. EnChaptered is our own product — built, shipped, and public.

Web UI & REST API · 4 months · Federal agency

Rebuilding a regression suite the team had learned to route around

  • Rebuilt the framework on DRY principles — class count cut 70%
  • Centralized config management across environments
  • Automated smoke & regression gates on build and UAT pipelines
  • GitLab Runners + Docker for parallel execution
  • Automated reporting integrated directly into CI/CD
96.5%
Pass rate (from 45–50%)
65 min
Full run (from 10+ hrs)
650+
Test cases (from 350)
2×/mo
Releases (from monthly)
"This overhaul turned our flaky regression suite into a robust quality gate integrated into modern DevOps pipelines." — Automation Architect, federal agency engagement
ETL Validation · Big Data QA · 3 months · Federal healthcare data program

Turning a five-day manual regression cycle into an automated afternoon

  • Built a custom PySpark + AWS EMR validation framework from scratch
  • Parameterized SQL and YAML-config-driven test scenarios
  • Automated EMR cluster creation and auto-shutdown
  • Automated DataFrame comparisons — exact row/column mismatch detection
  • Centralized reporting with full audit trail
24×
Faster regression (6 days → 6 hrs)
350+
Test cases (from 128)
40+
Scenarios (from 26)
16M+
Rows automated
"We built the first bridge between traditional QA and Big Data validation — enabling scalable, automated quality assurance for massive datasets." — Lead QA Consultant, federal healthcare data program
ETL & Big Data Validation · PySpark on Databricks · <6 months · Enterprise data platform, anonymized

Building a medallion-architecture validation framework from zero requirements

  • Built a YAML-driven PySpark framework on Databricks from a standing start — no existing framework or requirements to build on
  • One YAML mapping per table auto-generates the full test suite — 40+ validation types (null checks, duplicate checks, PK/FK checks) tailored by table type, environment, and data layer
  • Validates 150+ tables across Bronze, Silver, and Gold layers, now gating CI/CD
  • Reporting evolved from flat text logs to structured summary/detail tables, with a live Databricks dashboard in progress
  • Also caught critical source-to-target mismatches during a Postgres-to-Databricks migration, working directly with the dev team to root-cause and fix before the legacy database was retired — on schedule
150+
Tables validated across Bronze, Silver & Gold
40+
Validation types enforced per table
90%+
Table coverage, from a standing start
<6 mo
Zero to CI/CD-gated framework
Next · Productization assessment

The framework works, but it only runs inside a Databricks notebook. We audited it module by module and found the coupling concentrated in one small file — a hardcoded naming convention roughly every six lines. The fix is to compile each check down to plain SQL instead of Spark DataFrame calls. The same suite then runs from a laptop, from CI, or on a cluster — and finally gets a unit-test suite that doesn't need one.

The assessment also surfaced something nobody had raised. The framework captures real failing values into its results tables. The moment an AI agent can read those tables, source data becomes text a model treats as instruction — an indirect prompt-injection path running straight through a data-quality report. A per-column redaction policy is now a prerequisite, not a follow-up.

Scoped from there: a portable check library, a ten-tool MCP server so a failed run can be triaged conversationally instead of by hand, and the existing root-cause runbooks packaged as agent skills.

Salesforce Lightning + Experience Cloud · 4 months (ongoing) · Enterprise program

VisionQA: an AI-powered generator that stops broken automation before it ships

  • IR architecture — a single JSON source of truth, edit once, propagates everywhere
  • Rex validator: 16 semantic rules, blocks generation in CI on failure
  • Auto-detects hardcoded record IDs before they break in staging
  • Locator healing re-ranks fallbacks after a platform release, no code touched
  • Six documented interaction patterns, reusable across every app
<5 min
Framework generation
16
Validation rules enforced in CI
0
Manual edits for locator healing
6
Patterns documented & reusable
"What used to take two weeks to patch after a platform release now takes an afternoon. The CI gate catches what our code reviews were missing." — Lead SDET, enterprise Salesforce engagement
Salesforce Lightning · AI-Augmented Migration · 14 months · 5 engagements, anonymized

Migrating and building Salesforce Lightning automation where most QA teams won't

  • Delivered 5 Salesforce Lightning automation engagements in 14 months — 4 frameworks built from scratch, 1 fully migrated off a legacy suite
  • Built AI agents on GitHub Copilot to analyze existing test cases and user flows, then auto-convert them into Playwright, Java, and Cucumber with Allure reporting
  • Migrated suite grew ~50% (70 → 100 test cases) while preserving full existing coverage throughout the cutover, landing at a 97% pass rate
  • Automated in Salesforce Lightning specifically — dynamic elements and complex flows that lead most QA teams to skip automation entirely
  • Trained non-technical QA staff across 3 teams to run and extend the frameworks themselves; they're still expanding them independently today
5
Frameworks delivered in 14 months
~50%
Coverage growth (70→100 cases), zero coverage lost
97%
Pass rate on the migrated suite
3
Teams trained — still expanding frameworks on their own
Consumer AI Product · Next.js + Gemini API · Public project

EnChaptered — an AI storybook generator, built and shipped solo

  • Full-stack Next.js app: landing page, live demo, waitlist capture
  • Gemini API generates a personalized, age-appropriate story from a child's name and interests
  • Resend email pipeline for parent and internal notifications
  • Mobile-first build — most traffic is parents on their phones
  • Deployed on Vercel and iterated against real signups
<10s
Time to a generated story
Solo
Design → API → deploy, one builder
2–8
Target age range
Live
Shipped on Vercel, real users

Have something that needs this level of scrutiny?

Start with a free diagnostic