Tag: Claude Context Window

What Is the claude_delta Standard?

The claude_delta standard is a lightweight JSON metadata block injected at the top of every page in a Notion workspace. It gives an AI agent — specifically Claude — a machine-readable summary of that page’s current state, status, key data, and the first action to take when resuming work. Instead of fetching and reading a full page to understand what it contains, Claude reads the delta and often knows everything it needs in under 100 tokens.

Think of it as a git commit message for your knowledge base — a structured, always-current summary that lives at the top of every page and tells any AI agent exactly where things stand.

Why We Built It: The Context Engineering Problem

Running an AI-native content operation across 27+ WordPress sites means Claude needs to orient quickly at the start of every session. Without any memory scaffolding, the opening minutes of every session are spent on reconnaissance: fetch the project page, fetch the sub-pages, fetch the task log, cross-reference against other sites. Each Notion fetch adds 2–5 seconds and consumes a meaningful slice of the context window — the working memory that Claude has available for actual work.

This is the core problem that context engineering exists to solve. Over 70% of errors in modern LLM applications stem not from insufficient model capability but from incomplete, irrelevant, or poorly structured context, according to a 2024 RAG survey cited by Meta Intelligence. The bottleneck in 2026 isn’t the model — it’s the quality of what you feed it.

We were hitting this ceiling. Important project state was buried in long session logs. Status questions required 4–6 sequential fetches. Automated agents — the toggle scanner, the triage agent, the weekly synthesizer — were spending most of their token budget just finding their footing before doing any real work.

The claude_delta standard was the solution we built to fix this from the ground up.

How It Works

Every Notion page in the workspace gets a JSON block injected at the very top — before any human content. The format looks like this:

{
  "claude_delta": {
    "page_id": "uuid",
    "page_type": "task | knowledge | sop | briefing",
    "status": "not_started | in_progress | blocked | complete | evergreen",
    "summary": "One sentence describing current state",
    "entities": ["site or project names"],
    "resume_instruction": "First thing Claude should do",
    "key_data": {},
    "last_updated": "ISO timestamp"
  }
}

The standard pairs with a master registry — the Claude Context Index — a single Notion page that aggregates delta summaries from every page in the workspace. When Claude starts a session, fetching the Context Index (one API call) gives it orientation across the entire operation. Individual page fetches only happen when Claude needs to act on something, not just understand it.

What We Did: The Rollout

We executed the full rollout across the Notion workspace in a single extended session on April 8, 2026. The scope:

• 70+ pages processed in one session, starting from a base of 79 and reaching 167 out of approximately 300 total workspace pages
• All 22 website Focus Rooms received deltas with site-specific status and resume instructions
• All 7 entity Focus Rooms received deltas linking to relevant strategy and blocker context
• Session logs, build logs, desk logs, and content batch pages all injected with structured state
• The Context Index updated three times during the session to reflect the running total

The injection process for each page follows a read-then-write pattern: fetch the page content, synthesize a delta from what’s actually there (not from memory), inject at the top via Notion’s update_content API, and move on. Pages with active state get full deltas. Completed or evergreen pages get lightweight markers. Archived operational logs (stale work detector runs, etc.) get skipped entirely.

The Validation Test

After the rollout, we ran a structured A/B test to measure the real impact. Five questions that mimic real session-opening patterns — the kinds of things you’d actually say at the start of a workday.

The results were clear:

• 4 out of 5 questions answered correctly from deltas alone, with zero additional Notion fetches required
• Each correct answer saved 2–4 fetches, or roughly 10–25 seconds of tool call time
• One failure: a client checklist showed 0/6 complete in the delta when the live page showed 6/6 — a staleness issue, not a structural one
• Exact numerical data (word counts, post IDs, link counts) matched the live pages to the digit on all verified tests

The failure mode is worth understanding: a delta becomes stale when a page gets updated after its delta was written. The fix is simple — check last_updated before trusting a delta on any in_progress page older than 3 days. If it’s stale, a single verification fetch is cheaper than the 4–6 fetches that would have been needed without the delta at all.

Why This Matters Beyond Our Operation

2025 was the year of “retention without understanding.” Vendors rushed to add retention features — from persistent chat threads and long context windows to AI memory spaces and company knowledge base integrations. AI systems could recall facts, but still lacked understanding. They knew what happened, but not why it mattered, for whom, or how those facts relate to each other in context.

The claude_delta standard is a lightweight answer to this problem at the individual operator level. It’s not a vector database. It’s not a RAG pipeline. Long-term memory lives outside the model, usually in vector databases for quick retrieval. Because it’s external, this memory can grow, update, and persist beyond the model’s context window. But vector databases are infrastructure — they require embedding pipelines, similarity search, and significant engineering overhead.

What we built is something a single operator can deploy in an afternoon: a structured metadata convention that lives inside the tool you’re already using (Notion), updated by the AI itself, readable by any agent with Notion API access. No new infrastructure. No embeddings. No vector index to maintain.

Context Engineering is a systematic methodology that focuses not just on the prompt itself, but on ensuring the model has all the context needed to complete a task at the moment of LLM inference — including the right knowledge, relevant history, appropriate tool descriptions, and structured instructions. If Prompt Engineering is “writing a good letter,” then Context Engineering is “building the entire postal system.”

The claude_delta standard is a small piece of that postal system — the address label that tells the carrier exactly what’s in the package before they open it.

The Staleness Problem and How We’re Solving It

The one structural weakness in any delta-based system is staleness. A delta that was accurate yesterday may be wrong today if the underlying page was updated. We identified three mitigation strategies:

1. Age check rule: For any in_progress page with a last_updated more than 3 days old, always verify with a live fetch before acting on the delta
2. Agent-maintained freshness: The automated agents that update pages (toggle scanner, triage agent, content guardian) should also update the delta on the same API call
3. Context Index timestamp: The master registry shows its own last-updated time, so you know how fresh the index itself is

None of these require external tooling. They’re behavioral rules baked into how Claude operates on this workspace.

What’s Next

The rollout is at 167 of approximately 300 pages. The remaining ~130 pages include older session logs from March, a new client project sub-pages, the Technical Reference domain sub-pages, and a tail of Second Brain auto-entries. These will be processed in subsequent sessions using the same read-then-inject pattern.

The longer-term evolution of this system points toward what the field is calling Agentic RAG — an architecture that upgrades the traditional “retrieve-generate” single-pass pipeline into an intelligent agent architecture with planning, reflection, and self-correction capabilities. The BigQuery operations_ledger on GCP is already designed for this: 925 knowledge chunks with embeddings via text-embedding-005, ready for semantic retrieval when the delta system alone isn’t enough to answer a complex cross-workspace query.

For now, the delta standard is the right tool for the job — low overhead, human-readable, self-maintaining, and already demonstrably cutting session startup time by 60–80% on the questions we tested.

Frequently Asked Questions