Field notes

What we keep seeing.

Short technical positions drawn from prior operating experience, current research, reference architecture, and explicitly identified lab work.

Published

Positions we will defend on a call.

TrafficReference architecture and lab observation

The invoice is not the problem. The routing table is.

Spend spikes are frequently caused not by price changes but by mechanical work — extraction, classification, formatting — being sent down the route reserved for high-consequence work, because no route was ever chosen deliberately.

KnowledgePrior delivery experience

A chatbot cannot outrun three sources of truth.

When policy exists in a wiki, a PDF and someone's inbox, retrieval will faithfully surface whichever one it finds. Governance is not paperwork; it is the mechanism that makes an answer defensible.

EvaluationReference architecture

If quality is not scored, every model change becomes politics.

A fixed question set with a scoring method turns upgrade decisions into measurements. Without one, the loudest stakeholder's anecdote tends to become the evaluation suite.

OperationsPrior delivery experience

Degradation is more common than outage.

Providers more often get slower, terser, or subtly worse than they go dark. Monitoring built only for availability can report green through most of an incident.

InfrastructureCurrent lab program

Local inference is cheap per token and expensive per person.

Owned hardware may reduce marginal cost for evaluated mechanical workloads, subject to quality, latency, capacity, hardware and energy requirements. It also introduces capacity planning, patching, lifecycle and on-call. Both belong in the same decision record.

CostPrior delivery experience

Seats are not usage.

Seat licenses are provisioned by procurement and often abandoned by humans. Before negotiating a rate, measure who touched the tool last month — utilization is usually the number with leverage in it.

These notes are general engineering commentary, not advice about a specific environment. Anything that touches money, safety or compliance should be evaluated against your own architecture and constraints.

Planned

Queued, not written.

These are titles with a thesis behind them and no article yet. They are listed so the publication order is visible, not to pad the page.

  • Planned field note · Traffic

    AI Looks New Until You Diagram the Traffic

  • Planned field note · Traffic

    Class of Service for AI Workloads

  • Planned field note · Knowledge

    From Salesforce, Slack, Jira, Confluence, Zendesk, and Git to OKF

  • Planned field note · Cost

    Price per Token Is the Wrong Denominator

  • Planned field note · Knowledge

    An OKF Bundle Is a Knowledge Contract, Not an Agent Runtime

  • Planned field note · Traffic

    Why Model Handoffs Need a Continuity Contract

Disagree with one of these?

Good. Those are the most useful calls we take.