We don't write to a content calendar. We write when we have something specific to say — a customer's question that turned out to be everyone's question, an architectural decision worth showing our work on, a pattern from the design-partner motion that's compounding.
The grid is the navigational primitive of the resource surface. Columns are audiences; rows are buying stages. Each cell is a question-shaped headline that points at one or more blog posts that carry the answer.
The failure-mode taxonomy primer for buyers — why 95% of generative-AI pilots show no measurable P&L impact, and what an operating layer fixes that distribution alone doesn't.
A walkthrough of a day with Lucy — what she sees, how she nudges, what you build, and why the capability stays with you instead of with the tool.
An EU AI Act Article 4 framing of workforce AI literacy — what the mandate actually asks for, and how a coaching surface satisfies it without surveillance.
The routing-judgment thesis plus the V·C·C primer — why general AI tools answer prompts, training teaches out of context, and Lucy's trust architecture is structurally different.
The Signal / Context / Content boundary explained for the person doing the work — what Lucy observes, what she keeps, and the aggregate-only line manager-side data never crosses.
The trust-architecture-as-compliance essay — how aggregate-only manager data, refused capabilities, and human-oversight defaults map to Articles 4, 14, and the NIST AI RMF 1.0 functions.
The pilot deal-shape walkthrough — how design-partner engagements scope, what the measurement plane looks like, and which signals tell you the operating model is actually compounding.
A walkthrough of the Personal Coaching Plan — how Lucy sequences your first agent build, what counts as the first useful win, and how the pattern compounds across your week.
The Paid Pilot variant explainer — the deal shape designed for public-sector procurement, the deliverable structure, and how the engagement closes into an at-scale rollout.
The bottom-up scaling moat essay — why capability-formation data is structurally different from task-completion data, and why the moat compounds the further the rollout goes.
The capability-stays-with-you essay — how cohort gating, aggregate-only manager surfaces, and refused capabilities keep the trust posture intact as adoption widens.
The public-sector workforce-literacy-at-scale essay — what a multi-agency rollout looks like, how the trust architecture lands with works councils and regulators, and how the cadence holds.
Reverse-chronological. Audience and stage tags reference the grid so you can read across or read down.
The five-stage framework for actually changing behavior with AI. Why every other order fails — and why "rollouts" that skip Trust never make it past Adoption.
Business buyer · DiscoveryWhy "privacy by design" can't be a marketing line. The eight subsystems of trust, how they stack, and what breaks when you miss one.
Business buyer · EvaluationThe 70% of AI value lives in the muscle, not the model — the universal skills that turn AI from a curiosity into a working partner. And almost every rollout skips past it.
Individual / employee · DiscoveryPeople are bad at exponentials. Not a little bad. Really bad. The paper-folding problem, applied to your AI roadmap.
Business buyer · ScaleAI quietly renamed our core framework. Here's the document alignment system we built to catch drift before it compounds.
Business buyer · Implementation