Context
Select, retrieve, compress, and isolate the information a model needs without treating a huge prompt as architecture.
FG / 03 / Field guide
Learn through useful work: bounded authority, visible failures, repeatable evaluations, and a real quality bar.
Current briefing
Get your bearings
Separate models, products, workflows, agents, and the harness that makes them dependable. A model demo is not a production system, and an agent is not merely a longer prompt. Reliability lives in the surrounding constraints and feedback loops.
Start here / Three moves
Define inputs, output artifact, quality bar, privacy class, unacceptable failures, time saved, and the human decision that remains.
Use explicit instructions, structured output, minimal tools, permission boundaries, logs, and a clear stop condition.
Save representative examples, known traps, latency, cost, tool failures, and review outcomes; rerun them after changes.
Build capability
Select, retrieve, compress, and isolate the information a model needs without treating a huge prompt as architecture.
Control tools, permissions, state, retries, handoffs, tracing, budgets, and durable work products.
Measure actual workflow quality with examples, graders, failure taxonomies, human review, and regression checks.
Choose gear / Decision rule
Choose models and platforms by the actual workflow: data sensitivity, quality, tool use, modalities, latency, cost, maintenance, auditability, retention, access control, and portability. Benchmark the work—not the launch demo.
Your source map
Also followed as a newsletter.
Idea source; verify independently.
Idea source; verify independently.
Idea source; verify independently.
Idea source; verify independently.
Idea source; verify independently.
Idea source; verify independently.
Reference layer
Original editorial work
Replacing monthly subscriptions with local and self-hosted open-source software can restore privacy and eliminate recurring fees, but only if you are willing to pay the maintenance tax.
Read the working note →When software can record your keystrokes and study your habits, the real problem is no longer what AI can do—it is deciding what you should never let it touch.
Read the working note →Bridging an AMD Strix Halo mini-PC to a high-end NVIDIA card over OCuLink proves cross-vendor local inference works, but the practical friction and cost are steep.
Read the working note →Stacking four NVIDIA DGX Spark boxes unlocks half a terabyte of unified memory, but near-linear scaling cannot hide the brutal cost-per-token reality of desktop clusters.
Read the working note →Large language models default to a recognizable brand of breathless, smug prose. Fixing it requires persistent negative constraints rather than reactive prompting.
Read the working note →Most people locked in their AI habits two years ago. Cutting through the feature bloat reveals which newer techniques actually improve your work, protect your privacy, or waste your time.
Read the working note →As frontier AI benchmarks plateau, enterprise value is shifting from raw parameter reasoning to the messy reality of multi-step agent execution, security boundaries, and platform distribution.
Read the working note →Applied AI
How to deploy always-on background agents that aggregate competitor moves and policy shifts across tools without constant re-prompting.
Open use case →How to intercept agentic tool calls with fast, non-generative judgment models to slash latency, prevent runaway API spend, and block malformed actions before execution.
Open use case →