<?xml version="1.0" encoding="UTF-8"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>3ngram writing</title><description>Notes from the round-six build — how we think about the difference between a notes app and a context layer, and why we keep deleting features.</description><link>https://3ngram.ai/</link><language>en-us</language><item><title>Curation Is Infrastructure, Judgment Is the Job</title><link>https://3ngram.ai/blog/curation-is-infrastructure-judgment-is-the-job/</link><guid isPermaLink="true">https://3ngram.ai/blog/curation-is-infrastructure-judgment-is-the-job/</guid><description>Everyone now agrees that agents need a human who cares. But caring is two jobs: deciding what context matters, and judging whether the output is right. Only one of them should stay manual.</description><pubDate>Wed, 27 May 2026 00:00:00 GMT</pubDate><author>Sebastian Eusebio Bedmar Gade</author></item><item><title>Transcript Mining Is the New Retrospective</title><link>https://3ngram.ai/blog/transcript-mining-is-the-new-retrospective/</link><guid isPermaLink="true">https://3ngram.ai/blog/transcript-mining-is-the-new-retrospective/</guid><description>AI session transcripts show where work actually breaks: repeated corrections, missing context, stale instructions, failed checks, and unclear permissions. Teams should mine them before the same mistake repeats.</description><pubDate>Wed, 20 May 2026 00:00:00 GMT</pubDate><author>Sebastian Eusebio Bedmar Gade</author></item><item><title>The Agent-Readable Company</title><link>https://3ngram.ai/blog/the-agent-readable-company/</link><guid isPermaLink="true">https://3ngram.ai/blog/the-agent-readable-company/</guid><description>The next operating advantage is not just writing better docs for people. It is making decisions, commitments, incidents, PRs, and transcripts readable by the agents that now help run the work.</description><pubDate>Fri, 15 May 2026 00:00:00 GMT</pubDate><author>Sebastian Eusebio Bedmar Gade</author></item><item><title>Context Is the New CI</title><link>https://3ngram.ai/blog/context-is-the-new-ci/</link><guid isPermaLink="true">https://3ngram.ai/blog/context-is-the-new-ci/</guid><description>Agents are getting faster, but work still depends on state. AI-native teams need a context pipeline that captures, verifies, retrieves, and prunes the facts agents act on.</description><pubDate>Wed, 13 May 2026 00:00:00 GMT</pubDate><author>Sebastian Eusebio Bedmar Gade</author></item><item><title>AI Memory Is Not Enough</title><link>https://3ngram.ai/blog/ai-memory-is-not-enough/</link><guid isPermaLink="true">https://3ngram.ai/blog/ai-memory-is-not-enough/</guid><description>Memory helps an AI recall facts. Serious work needs more than recall: typed context, current state, provenance, permissions, and follow-through across every tool and agent.</description><pubDate>Fri, 08 May 2026 00:00:00 GMT</pubDate><author>Sebastian Eusebio Bedmar Gade</author></item><item><title>The chief-of-staff metaphor, and why it matters in a single-prompt world.</title><link>https://3ngram.ai/blog/chief-of-staff-metaphor/</link><guid isPermaLink="true">https://3ngram.ai/blog/chief-of-staff-metaphor/</guid><description>A chief of staff used to be reserved for executives. With the right AI tools, everyone can have one: a context layer that keeps receipts, briefs the next room, and makes sure nothing falls between two conversations.</description><pubDate>Thu, 30 Apr 2026 00:00:00 GMT</pubDate><author>Sebastian Eusebio Bedmar Gade</author></item><item><title>Follow-through is the product.</title><link>https://3ngram.ai/blog/follow-through-is-the-product/</link><guid isPermaLink="true">https://3ngram.ai/blog/follow-through-is-the-product/</guid><description>AI memory is becoming table stakes. The harder product is keeping decisions, commitments, blockers, and source context alive after the chat window closes.</description><pubDate>Thu, 30 Apr 2026 00:00:00 GMT</pubDate><author>Sebastian Eusebio Bedmar Gade</author></item><item><title>A small evaluation: portable context vs. a fresh model.</title><link>https://3ngram.ai/blog/portable-context-vs-fresh-model/</link><guid isPermaLink="true">https://3ngram.ai/blog/portable-context-vs-fresh-model/</guid><description>The claim is simple: the same model should do better follow-through work when it starts with the right work state. Here is the evaluation design we need before saying that with confidence.</description><pubDate>Thu, 30 Apr 2026 00:00:00 GMT</pubDate><author>Sebastian Eusebio Bedmar Gade</author></item><item><title>The prompt-compression metric we need before we make compression claims.</title><link>https://3ngram.ai/blog/prompt-compression-metric/</link><guid isPermaLink="true">https://3ngram.ai/blog/prompt-compression-metric/</guid><description>Shorter prompts are only useful if they preserve the work state. Here is how we should measure compression, recall, latency, and false carryover before making numeric claims.</description><pubDate>Thu, 30 Apr 2026 00:00:00 GMT</pubDate><author>Sebastian Eusebio Bedmar Gade</author></item></channel></rss>