Joshua R. Barron · Lubbock, Texas
Systems that tell the truth about their own limits.
I build platforms where the guardrails are part of the architecture — policy-as-code, tamper-evident audit, fail-closed defaults for humans and AI agents alike. Twenty-eight years across enterprise SaaS and higher education, most recently coordinating around eighty developers across multiple agile teams.
-
14,219
commits
across 30 repositories in 9 months, by one engineer directing governed AI agents
-
22s → 0.4s
report resolution
by collapsing ~1,500 sequential queries into ~7 batched
-
285+
device capabilities
across 57 vendors, under a 1,279-test conformance suite
-
94%
coverage on 1,849 tests
live-verified weekly against production tenants
What I’m brought in for
-
Platform & integration architecture
Event-driven and event-sourced systems, partner integration fabrics, IoT control planes, canonical data contracts. Kafka, Debezium CDC, Kubernetes, AWS. Twenty-plus partner integrations shipped and maintained.
-
Governance & compliance engineering
SOC 2 automation, identity lifecycle, OPA/Rego policy-as-code, consent ledgering, tamper-evident hash-chain audit. The unglamorous layer that decides what is allowed, why, and who approved it.
-
AI-orchestrated delivery
Not agents writing code — the governance substrate that makes agent output safe to merge: claim leasing, adversarial review gates, provenance hashing, anti-hallucination verification, evaluations as infrastructure.
Selected work
-
2025 – 2026
A governed multi-agent delivery platform
Turned LLM coding agents into a production-grade delivery capability across a 30-repository codebase: persona-based governance manifests, a 50-skill catalog, file-claim leasing so parallel agents never collide, adversarial review agents as quality gates, and audit trails on every autonomous action. Output included a greenfield 12-service governance platform, an event-sourced IoT control plane, and shipping firmware.
-
2025 – 2026
A compliance authority layer for regulated software
Twelve bounded services deciding what is allowed, why, and who approved it — field- and object-level authorization, consent ledgering, jurisdictional rule layering with auditable conflict resolution, legal-grade receipts with policy-version metadata, and immutable decision ledgers. The same policy boundary governs humans and AI agents.
-
2026
Five radios on one microcontroller
LoRaWAN, BLE, Z-Wave, NFC and Wi-Fi in a single Zephyr RTOS image with secure boot and signed over-the-air updates — at 73% flash and 27% RAM, after disproving an “exceeds budget” assumption with measured builds rather than argument.
-
2026
A user interface that writes itself
A server-driven UI where the interface is a projection of a machine-readable capability catalogue: add a device capability and its controls appear for entitled users with no renderer changes. One contract drives a web runtime plus generated Android and iOS native code, verified by real compiler runs — and every control is gated fail-closed by the same policy engine that guards the API.
The pattern holds across industries that have very little to do with each other.
-
PropTech SaaS
Multifamily leasing, payments, IoT, identity. Head of Systems & Software.
-
Higher education
Seventeen years. Four enterprise platforms, 283 stakeholder groups, record retention outcomes.
-
Nonprofit & mission-driven
Program leadership and operations before the software career; still how I think about adoption.
-
Enterprise consulting
PricewaterhouseCoopers knowledge management; e-business consulting.
Deep practice areas
The capabilities above apply anywhere. In one sector I have enough history that it deserves its own account.
Higher education · 21 years
Student success is an operations problem before it is a technology problem.
Seventeen years inside a public research university — four enterprise success platforms, 283 stakeholder groups, a provost’s task force, record retention and graduation outcomes — then four years on the vendor side building the platforms institutions buy. Retention diagnostics, selection and implementation, and the integration plumbing nobody budgets for.
Three ways this usually works
-
Advisory
Days to weeks
A hard question answered properly. Architecture review, build-versus-buy, a second opinion on a roadmap you’ve stopped being able to see clearly.
-
Fractional leadership
Three to six months
Senior engineering capacity for a team between hires, standing up a new function, or carrying a platform through a transition that needs someone accountable.
-
Hands-on delivery
Scoped build
I still write the code. Governance layers, integration fabrics, data platforms — built to be operated by your team after I leave, not to keep me on retainer.
Tell me what you’re trying to move.
A short call costs nothing and usually clarifies whether this is a fit. I’ll tell you plainly if it isn’t — the same way I’d expect a system to report what it can’t verify.