Performance.

27 years across commercial, international, defense, and intelligence. On AWS since 2014. The credentials that buy me the right to have an opinion are below — past performance from Leidos (2014–2026), then current performance, the operating model running today.

Past Performance

01 · US Air Force

Aligned a $4B+ digital infrastructure consortium

› Shaped enterprise technology and acquisition strategy across a $4B+ Air Force initiative
› Aligned teams from five large corporations and government stakeholders into a unified digital infrastructure direction
› Enabled coordinated capture and execution across a multi-company consortium

02 · Corporate Leadership

Advised three Sector CTOs across $2B – $3B+ portfolios

› Aligned executives, technologists, and partners on technology investment and architecture direction
› Shaped strategy before major commitments were made
› Worked across competing priorities to produce coordinated movement

03 · US Army

Led the Army's first on-prem to AWS classified cloud migration

› Architected and delivered the solution end-to-end in a mission-critical environment
› Reduced cloud spend and software licensing costs by 50%
› Delivered $2M+ in annual savings

04 · Multi-Organization Initiatives

Recovered and accelerated complex, multi-org programs

› Built alignment across competing stakeholders with no natural single owner
› Re-established momentum where progress had stalled
› Translated executive intent into coordinated cross-organization execution

Current Performance

01 · The company

Wolfberg LLC

› LLC formed in 2026; legal entity, brand, website, and deploy stack built end-to-end via the operating model
› One operator + three Claude instances coordinating end-to-end
› Live at wolfberg.ai; the company itself runs on Keystone + Capstone

See the brief

02 · The brain

Capstone

› Memory files, canonical pages, and session protocols carry context across every session
› Three Claude instances coordinate through it: Capstone (strategy), Code (execution), Design (visual)
› Architecture is public; brain contents stay private — what competitors can't copy is how the components work together

See Capstone →

03 · The infrastructure

Keystone

› Built solo in 41 hours for $40 in API costs
› AI-native operational platform on AWS; the substrate used the way it was designed to be used
› Scales to a million users with four code changes; no re-architecture

See Keystone →

04 · The pipeline

Refactory

› Six-agent AI pipeline: Cartographer, Architect, Migrator, Verifier, Cutover Pilot, Concertmaster
› Refactors legacy applications to cloud-native serverless architecture, on contract
› Pluggable target topology — Keystone is the optimized attach, not the required destination

See Refactory →

These four are proof the way of working does what it claims. The full argument lives in the evidence.

Cloud bill scaling linearly? Roadmap measured in quarters? Let's talk.

Start the conversation