Field notesand journal articles.
Twenty articles on cloud computing, AI, agentic AI, and the practical work of building systems that create real value.
Write the vision, and make it plain upon tables, that he may run that readeth it.
Twenty editorial articles.
Conveyor of small black tiles being polished one by one, soft warm light, paper-bag colored background
Modernization is a pipeline, not a rewrite.
We killed a $400K rewrite in week two and replaced it with a three-tier modernization pipeline. Eleven modules extracted, 19,000 lines of dead code retired, drift down 62% — without a single big-bang cutover.
Two stacks of paper on a worn wooden desk — one tall, one a single sheet — late afternoon light
Audit before you automate.
An association almost spent $180K automating a workflow that ate twenty-four hours per year, while an 8,680-hour problem sat untouched. The fifteen-minute audit that caught it is the cheapest piece of work in any AI engagement.
Schematic of three small rectangles connected by clean lines, ink on cream, draftsman style
MCP servers are the orchestration layer, not the demo.
Most AI tooling lives one paste away from the systems it could help with. Model Context Protocol servers close that gap without giving up the security posture an enterprise can defend.
Three slim arrows leaving a single point, meeting again further out, drafted in dark green ink
Subagents are a team-management pattern.
One prompt refactored a payments service in twenty-two minutes by dispatching three subagents in parallel. The interesting part is not the speed. It is that the pattern matches how strong engineering leads have always worked.
How an engagement with us actually works.
Discovery sprint, pod, managed platform, or staff augmentation. The model depends on what you need; the discipline does not change.
What we build for the public sector.
Modernization without a re-platform death march. Phased work that respects procurement and the fact the service has to work tomorrow morning.
What we build in web3 and blockchain.
Smart contracts, audited. Protocol engineering, contract systems, and supporting infrastructure where mistakes are public and hard to roll back.
What we build for algorithmic trading desks.
Execution systems, research tooling, and controls for low-latency desks. The control plane around fast strategies.
What we build for retail and commerce teams.
Inventory ledgers, ops consoles, automation that pays back in months. We fix the expensive seams between storefronts, warehouses, ERP, and the people cleaning up the mismatches.
What we build for logistics operators.
Routing engines, fleet platforms, document agents. For operators who cannot afford slow decisions or brittle integrations at the edge of the business.
What we build for healthcare teams.
HIPAA-grade data flows. Internal platforms that ship safely. Clinical and operational systems modernized without breaking privacy or cadence.
What we build for finance and tax teams.
Compliance-first systems. AI agents that read regulations. Ledgers, filing pipelines, decisioning tools that survive auditors and quarter-end at the same time.
Observability and SRE, with real SLOs.
SLOs, error budgets, dashboards a CFO can read. Incidents that end in postmortems, not blame.
Automation and workflows, built around the humans.
Temporal, n8n, Airflow, hand-rolled. Humans removed from loops that don't need them, kept in loops that do.
Platform engineering that earns its keep.
Internal developer platforms with golden paths and paved roads — self-service that ships features instead of tickets.
React frontends built like furniture.
Next.js, Remix, React Native. Frontends built like furniture — square, joinery visible, tested.
Enterprise-grade Angular, welded together.
Design systems, NgRx state, micro-frontends, accessibility welded in.
AI agents and LLM-Ops, made boring.
Production agents wired to your real systems — eval harnesses, guardrails, observability, cost ceilings.
DevOps and CI/CD, the way we set it up.
Pipelines that ship daily. Trunk-based, signed artifacts, ephemeral previews, rollback in seconds.
What we mean when we say cloud architecture.
AWS, GCP, Azure, hybrid. Reference architectures, migrations, and cost programs that survive the second budget cycle.
The boring cloud stack still wins.
Queues, Postgres, object storage, plain HTTP, and explicit idempotency are still a moat. Spectacle ages quickly; maintainable systems age into leverage.
Decision records are value preservation.
A written architecture decision can outlast a roadmap deck, a staffing plan, and half the code it first described. That durability is why it creates value.
Shipping on Friday is a value question.
The real question is not whether teams deploy on Friday. It is whether the system, controls, and rollback path have earned enough trust to do it safely.
AI still needs boring operations.
Shipping AI does not remove the need for observability, deployment discipline, and incident response. It amplifies the cost of skipping them.
The quiet economics of cloud delivery.
Delivery pipelines rarely get applause, but they compound into lower coordination cost, faster recovery, and fewer meetings about avoidable pain across cloud teams.
Agentic systems need control planes, not vibes.
As AI systems start taking chained actions, the control plane stops being optional. Guardrails, approvals, kill switches, and replay paths are part of the product.
Modernization only creates value if service quality improves.
Transformation fails when it produces architecture slides but not better delivery. Real value shows up when citizens, operators, or customers feel the system getting calmer.
A good cloud architecture is often smaller than expected.
Many teams do not need more services. They need fewer boxes, clearer ownership, and cloud infrastructure that can still be understood before lunch.
Dashboards should explain value, not just activity.
Observability earns its keep when it explains risk, spend, throughput, and service health in terms leaders can act on. Dense charts with no decision attached are wall art.
Evaluate AI systems against business failure, not benchmark theater.
AI evaluation gets serious when it measures escalation quality, retrieval coverage, operator intervention, and the cost of being wrong in production.
Cloud portals matter less than the contract behind them.
Catalogs, portals, and dashboards only help when the underlying platform is credible. Self-service is a service-level promise, not a navigation pattern.
Humans stay in the loop on purpose.
Good agentic AI removes people from repetitive work and places them exactly where judgment matters. Neither total automation nor permanent hesitation is useful.
Price reliability like it is revenue protection.
Reliability looks expensive until you compare it to delayed launches, recurring incidents, and the cost of forcing operators to stop trusting the system.
A cloud platform is broken if every team needs a ticket.
Internal cloud platforms fail when they centralize pain instead of removing it. A paved road has to be easier than the workaround on a bad Tuesday afternoon.
AI systems need replay, not mystery.
The fastest way to lose confidence in an AI system is to make it impossible to explain. Replayable reasoning and grounded outputs matter more than polished demos.
Architecture is only valuable when operators feel the difference.
Ledgers, workflows, and data models matter when they reduce pain in reconciliation, planning, and service delivery. Design patterns are not a product strategy by themselves.
Document agents are only useful when operators trust them.
Agentic AI earns its place when it shortens slow loops without inventing facts. The test is not whether a model can parse a document, but whether an operator will sign off on the result.
Forty-seven services later, where is the value?
Complexity does not become strategic just because it took years to build. Value appears when a platform helps teams ship better decisions, not more moving parts.
Cloud architecture should survive the second budget cycle.
Cloud computing is easy to approve once and hard to justify forever. Good architecture still makes sense after finance has looked at a year of invoices.
Audit logs before agent rollouts.
Agentic AI becomes enterprise software the moment someone has to explain its actions to risk, legal, or operations. The audit trail is not cleanup work; it is part of the product.
What this journal is for.
Write from shipped work, not conference vibes.
Bias toward systems, controls, and operating realities over trend-chasing.
Use the journal to explain how Kleio thinks about cloud, AI, and building value.