Skip to main content
Truvisory
§ Insights / Field notes

What’s actually shipping in 2026.

Field notes from active builds. Architecture decisions made under deadline. Federal acquisition signal worth listening to. The opposite of vendor-blog content.

Not sure where to start? Take the 1-min AI Readiness Scorecard →

▶ Featured · Build log

At 5% GPU utilization, the math doesn't work. Here's what does.

Tony Adams · 14 min read ·

The Cast AI 2026 State of Kubernetes Optimization Report quietly buried the most important number in the AI infrastructure conversation this year. Across 23,000 production clusters, average GPU utilization is 5%. Not p10. Average. The reserved-capacity model that the entire enterprise AI stack was sold under is, on the math, mostly empty space being expensed against P&L.

If you are paying for reserved GPU and using 5% of it, you are buying a Ferrari to commute three miles, twice a week, with one passenger.

The pay-per-inference architecture isn’t a niche cost-saver — it’s the only model that survives a CFO doing the math. Workers AI on Cloudflare bills only for tokens you actually run, on hardware you don’t manage, in 330+ cities of presence. The same architecture pattern (orchestrator-plus-scout, RLM-style) that we ship in HotCopy lets one principal-led team deliver multi-agent systems that used to require a 12-person infrastructure org…

// Federal

VA ATO, VAEC, and FedRAMP: How AI Actually Ships on VA Infrastructure

How does an AI tool get authorized to run at the VA? It rides inside the VA Enterprise Cloud's existing FedRAMP High ATO, inherits the controls, and completes a thin application-layer ATO — now via a 60-day accelerated path. The vendor doesn't need its own FedRAMP authorization; it needs to be ATO-literate. Here's the mechanics.

↳ Part of: VA AI Modernization for SDVOSBs: The Procurement Ground Truth for 2026

8 min read Read →
// Federal

VA Compliance: Why FedRAMP-Aware Is Right and CMMC Doesn't Apply

For VA civilian-agency work, the correct security posture is FISMA, NIST 800-53, the VA ATO, and FedRAMP for cloud — not CMMC. CMMC is a Department of Defense program that doesn't flow to VA contracts. Here's why the absence of CMMC is the right posture, what "FedRAMP-aware" honestly means, and how to represent it without overclaiming.

↳ Part of: VA AI Modernization for SDVOSBs: The Procurement Ground Truth for 2026

8 min read Read →
// Federal

Polaris for VA AI Work: The One SDVOSB GWAC With a Door Still Open

Polaris is GSA's new, AI-forward, no-ceiling SDVOSB governmentwide contract — and unlike the closed VETS 2 pool, it's designed with on-ramps. For a brand-new SDVOSB, it's the one governmentwide vehicle where a future prime path is genuinely plausible. Here's the honest three-track play: position for the on-ramp, team in now, and watch.

↳ Part of: VA AI Modernization for SDVOSBs: The Procurement Ground Truth for 2026

7 min read Read →
// Federal

REACH VET: The Honest SDVOSB Role Near the VA's Suicide-Risk Model

REACH VET is the VA's deployed suicide-prevention predictive model — built, owned, and governed inside the VA. A new SDVOSB should never propose to build or replace it. Here's the bounded, ethical surrounding work where a firm can genuinely help, the high-impact-AI and PHI bar that work must meet, and an honest read of what the model does and doesn't do.

↳ Part of: VA AI Modernization for SDVOSBs: The Procurement Ground Truth for 2026

7 min read Read →
// Federal

How to Forecast VA AI Work Before the RFP Drops

The SDVOSB set-aside decision on most VA AI work is made 6–18 months before any RFP — at the market-research stage. Here's the free, repeatable forecasting workflow a brand-new firm can run to show up early: the VA forecast, the AI use-case inventory, Sources Sought monitoring, recompete tracking, and the policy reports that signal what's coming.

↳ Part of: VA AI Modernization for SDVOSBs: The Procurement Ground Truth for 2026

7 min read Read →
// Federal

Who Actually Buys VA AI: TAC vs. SAC for SDVOSBs

Most VA enterprise AI/IT work is bought by one office — the Technology Acquisition Center — and a real, growing slice of clinical AI runs through the Strategic Acquisition Center. If you don't know which center owns which vehicle, you can't forecast, target a capability statement, or pick a teaming partner. Here's the org map for a new SDVOSB.

↳ Part of: VA AI Modernization for SDVOSBs: The Procurement Ground Truth for 2026

7 min read Read →
// Federal

Contact-Center AI at the VA: The Honest SDVOSB Role

VA's contact centers — 1-800-MyVA411, VA Health Connect, the VA.gov chatbot — are in active AI modernization, and the work is increasingly going to SDVOSBs. Here's the honest, bounded role for a new firm: surrounding AI engineering as a subcontractor, the M-25-21 and PHI limits that shape it, and the one bright line you don't cross — the Veterans Crisis Line.

↳ Part of: VA AI Modernization for SDVOSBs: The Procurement Ground Truth for 2026

7 min read Read →
// Federal

NVSBE Is Gone: How a New SDVOSB Works VA Events in 2026

VA discontinued NVSBE, and the de facto successor is the NVSBC VETS Conference. Here's the honest, teaming-first event playbook for a brand-new SDVOSB selling AI/automation to the VA — which one or two events are worth the travel, which to attend free and virtual, and how events feed the desk-based pipeline work rather than replace it.

↳ Part of: VA AI Modernization for SDVOSBs: The Procurement Ground Truth for 2026

7 min read Read →
// Federal

VA EHRM (Oracle Health): The Honest SDVOSB Subcontracting Map

VA's Electronic Health Record Modernization is Oracle Health's program, run by Accenture, Booz Allen, and Leidos — and a brand-new SDVOSB cannot prime any of it. Here's the honest map of the surrounding AI/automation and governance work where a bounded-scope sub can actually contribute: FHIR validation, test automation, ambient-scribe integration, and M-25-21 documentation, under a prime, never the EHR itself.

↳ Part of: VA AI Modernization for SDVOSBs: The Procurement Ground Truth for 2026

7 min read Read →
// Federal

AI Leadership in 2026: Governance Is Table Stakes, Delivery Is the Job

A point of view on what AI leadership actually means for the VA and the federal SDVOSB ecosystem in 2026. Every agency now has a strategy, a Chief AI Officer, and a use-case inventory — governance is the floor, not the differentiator. The real bottleneck is delivery, data readiness, and human-in-the-loop discipline. Here's the case for leading by shipping bounded, accountable software.

↳ Part of: VA AI Modernization for SDVOSBs: The Procurement Ground Truth for 2026

6 min read Read →
// Commercial

AI for Medical Practices: Where Clinics Actually Get ROI (Ambient Scribing, Intake, Prior Auth, and Scheduling)

Where AI actually pays off in mid-market private medical practices — ambient scribing, patient-message drafting, intake and scheduling, prior authorization, and revenue cycle — with an honest read on the mixed ROI evidence, the HIPAA and safety reality, and a 90-day starting point.

↳ Part of: AI Use Cases by Industry: Where Mid-Market Companies Actually Get ROI

10 min read Read →
// Commercial

AI for Commercial Real Estate and Property Management: Where CRE Firms Actually Get ROI

Where AI actually pays off in mid-market commercial real estate and property management — lease abstraction, due-diligence document review, and portfolio intelligence over your own leases — plus the accuracy risk that makes human review non-negotiable, and a 90-day starting point.

↳ Part of: AI Use Cases by Industry: Where Mid-Market Companies Actually Get ROI

10 min read Read →
// Cloudflare-Native

The Real Cost of Cloudflare Workers vs AWS Lambda for an AI App

A real-dollars monthly billing breakdown of running an AI app on Cloudflare Workers vs AWS Lambda in 2026. Why CPU-time billing beats wall-clock billing for IO-bound AI, the egress swing factor, the AWS hidden-cost tax, and the 128MB cap that forces Lambda regardless of price.

↳ Part of: Why We Build AI on Cloudflare: The Mid-Market and Federal Case for a Cloudflare-Native AI Stack

10 min read Read →
§ Newsletter

Field notes, monthly. Not a vendor blog.

One email a month. What we shipped, what we read, what changed in the federal acquisition or Cloudflare-platform layer. Written by the principal, not by a content team. Zero tracking pixels.

// We will never share, sell, or “enrich” this address.
Cadence 1×/month, max
Length ~600 words
Unsub One click