An HN headline ('Why 1M context windows won't solve agent memory (and a protocol that does)') plus reconstructed GitHub 'echo' testimony are the only evidence for a docs-first, model-agnostic continuity protocol promoted by community user zackemannen81, who claims it lets agents externalize state and resume across long-running sessions without ever-larger context windows. Roughly five weeks and ~41 attached items later, nothing in the record identifies, inspects, or tests the protocol itself — no repo review, independent implementation, adoption signal, or demonstrated continuity result. What the record does show is the surrounding ecosystem converging on the general pattern: field reports of handoff docs, SESSION_STATE files, and Markdown vaults (with recurring staleness and retrieval-at-scale complaints), the live HN debate 'Agents don't need memory, they need documentation,' and — per the supplied snippets — a mainstream vendor now stating the same thesis, Google's ADK long-running-agent architecture ('the fix isn't a bigger context window... the agent's state is explicit, durable, and decoupled from raw chat history'). The web search surfaces only this pattern-level debate (ADK, persistent-agent market pieces, MCP's statelessness, model-agnostic stack guides); it does not surface zackemannen81's protocol at all, so the specific claim remains unvalidated rather than disproved.
2026-10-04T19:56:23Z
The one live signal — HN 'Agents don't need memory, they need documentation' — went 14→313 pts/191 comments, a genuine front-page arrival of the docs-over-memory thesis, but the growth adds volume, not substance: its tensions (doc-maintenance token cost, staleness at scale, Naur, session-grep) were already on record at the 14-pt look, and still nothing touches zackemannen81's protocol. The case closes absorbed: the thesis it carried is now established at ecosystem scale and already codified in Scott's canon, while the protocol that seeded the case ends five weeks and 41 items on as unvalidated, unadopted and unreferenced — moot rather than proved.
2026-10-03T22:52:12Z
grounded: known/low — Scott's own wikis already carry this position in published form — Long-Running Agents' 'stateless workers + stateful external kernel' and Markdown OS state the
2026-10-03T22:45:17Z
The docs-over-memory HN thread keeps growing (8→14 pts) and now draws substantive trade-off debate — token cost of maintaining docs at scale, staleness, Naur's theory-building objection, session-grep as a rival — meaning the concept conversation is maturing while zackemannen81's protocol remains untouched by any of it; five weeks and 41 items in, the multi-platform spread the magnitude valve reads is the pattern's footprint, not the protocol's, so heat stays low and no quiet clock reset is earned.
2026-10-03T22:25:31Z
evidence attached: hn.story.49945933 — Independent HN articulation of the exact docs-over-memory thesis the docs-first continuity case is testing, with real discussion.
2026-09-21T14:19:28Z
The new debugging handoff template further normalizes durable files as a session-transfer primitive, but provides no outcome data or connection to this maintainer’s protocol. Despite loud ecosystem-wide spread, the case-specific implementation and validation footprint has not expanded.
2026-09-21T13:22:10Z
evidence attached: reddit.post.1wmb9ev — The concrete handoff template provides adoption evidence for externalizing failed attempts and uncertainty across long-running agent sessions.
2026-09-20T16:23:17Z
The newest excerpt describes fresh conversations reading a persistent file, but its agent-voiced narrative supplies neither demonstrated recovery results nor a connection to this maintainer’s protocol. The loud cross-platform spread concerns the broader external-memory pattern, not an expanding implementation or adoption footprint for this case, so attention remains low.
2026-09-20T16:22:20Z
evidence attached: reddit.post.1wll9mx — This firsthand workflow is practical evidence that externalized files can preserve continuity across fresh conversations without a dedicated orchestration framework.
2026-09-19T14:22:15Z
The latest firsthand account reinforces familiar failures of conversation-based project state, but its truncated text establishes neither the proposed remedy nor recovery across crashes or model swaps. The loud spread reading concerns the broader memory-tool landscape, not adoption or testing of this maintainer’s protocol, so this case remains low-attention.
2026-09-19T14:21:58Z
evidence attached: reddit.post.1wkme7i — Independent hands-on evidence supports externalizing plans, dependencies, and validation onto durable files for continuity across compaction, crashes, and model swaps.
2026-09-18T04:30:55Z
Continuity adds another adjacent project headline, not evidence of a verified plugin release, contradiction prevention, or use of the subject protocol. The growing memory-tool landscape still does not independently validate this maintainer’s claim or change its value to Scott.
2026-09-18T04:21:53Z
evidence attached: hn.story.49750016 — The released Continuity plugin directly bears on whether externalized project state can prevent contradictions across agent sessions.
2026-09-17T19:24:02Z
The latest harness request repeats the known demand for software-project continuity, but its truncated account supplies neither a demonstrated compaction failure nor evidence about this protocol. It does not turn broad demand for external state into validation of the maintainer’s solution.
2026-09-17T19:21:49Z
evidence attached: reddit.post.1wj2ru2 — The firsthand report materially supports the open hypothesis that coding agents need externalized state and better continuity than built-in compaction provides.
2026-09-17T17:51:32Z
MemPalace adds only an adjacent OpenCode plugin headline, not inspected code, verified release details or continuity results. It does not corroborate the subject protocol; accumulating neighboring memory projects still leaves this case unvalidated and low-priority for Scott.
2026-09-17T17:26:01Z
evidence attached: hn.story.49742226 — A released OpenCode persistence plugin is a concrete artifact bearing directly on preserving agent memory across sessions.
2026-09-16T10:26:40Z
Kival adds a builder-described organizational knowledge system with a concrete stack and interfaces, but no demonstrated session recovery or connection to the subject protocol. This broadens the adjacent implementation landscape without corroborating the maintainer’s claim or changing its consequence for Scott.
2026-09-16T10:22:12Z
evidence attached: hn.story.49724109 — This self-hosted organizational knowledge system is a concrete implementation relevant to externalized shared state and continuity across agent sessions.
2026-09-16T04:22:20Z
Context Freshness Ledger adds only an adjacent Show HN headline: no schema, implementation or results are supplied to establish that it addresses stale memory. It neither validates the subject protocol nor changes its low consequence for Scott.
2026-09-16T04:21:49Z
evidence attached: hn.story.49721941 — The released freshness-ledger schema materially contextualizes the open case about reviewable externalized agent state and continuity.
2026-09-15T18:01:07Z
DaiDocs adds a builder-described portable memory format, but a serialization proposal does not demonstrate session recovery or validate this maintainer’s protocol. The new attachment reinforces the familiar external-state pattern without changing this case’s assessment or consequence for Scott.
2026-09-15T17:26:08Z
evidence attached: hn.story.49715672 — A plain-text memory format is a concrete alternative implementation for externalizing agent state across sessions.
2026-09-15T11:22:42Z
The new report describes a more concrete adjacent workflow—transcript extraction into Markdown and immutable JSON events, paired with a SessionStart hook—but supplies neither inspected code nor demonstrated recovery results. It supports the familiar external-state pattern without validating this maintainer’s protocol or changing its consequence for Scott.
2026-09-15T11:22:22Z
evidence attached: reddit.post.1wgwl1c — A concrete session-end extraction and session-start briefing implementation provides practical supporting evidence for externalized agent continuity.
2026-09-15T09:22:45Z
The new Markdown-canonicality headline adds no implementation detail or protocol-specific validation; a shared-link attachment is not independent corroboration. The broader external-memory pattern remains active, but this maintainer’s claim has not gained substance or new consequence for Scott.
2026-09-15T09:22:16Z
evidence attached: hn.story.49709612 — shared external link with case evidence
2026-09-15T03:21:40Z
PowerContext adds only a headline about an adjacent handoff tool, not a verified implementation or independent validation of this maintainer’s protocol. The attachment does not change the case’s meaning: external-state workflows remain active, but this specific claim is still unsubstantiated.
2026-09-15T03:21:30Z
evidence attached: hn.story.49707246 — PowerContext is an independent artifact directly bearing on externalized context handoff and continuity across human and agent sessions.
2026-09-14T18:45:20Z
The latest discussion repeats Markdown, checkpoint-file and Obsidian workflow anecdotes; it does not establish adoption or successful recovery using this maintainer’s protocol. The broader external-memory pattern remains active, but this case has gained no protocol-specific validation or new consequence for Scott.
2026-09-14T18:22:33Z
evidence attached: reddit.post.1wgb6d6 — This independent user workflow provides adoption evidence that externalized Markdown and Obsidian state can preserve continuity across recurring Claude sessions.
2026-09-12T23:21:36Z
The new session-transfer item is headline-only evidence, not the concrete implementation established by its attachment rationale; transferring Claude Code sessions also need not demonstrate docs-first or model-agnostic continuity. It adds no validation of this maintainer’s protocol and leaves the case low-priority.
2026-09-12T23:21:23Z
evidence attached: hn.story.49678247 — A concrete implementation for transferring Claude Code sessions bears directly on the open hypothesis that externalized state can preserve continuity across agent runs.
2026-09-12T02:24:20Z
The Obsidian post adds another self-reported external-memory workflow, not evidence that this maintainer’s protocol works. Its truncated account supplies no measured continuity or cross-model recovery result, leaving the case unvalidated and low-priority.
2026-09-12T02:21:29Z
evidence attached: reddit.post.1wdzdtr — This concrete Claude Code and Obsidian workflow supports the case that externalized documents can preserve useful agent continuity across sessions.
2026-09-11T13:25:41Z
SOS adds an adjacent implementation claim and a report that simple file-based governance was insufficient; Kiro Crew adds only a persistent-workspace headline. Neither validates this maintainer’s protocol or establishes reliable continuity, so the broader pattern’s activity should not promote this case.
2026-09-11T13:22:04Z
evidence attached: hn.story.49657363 — Kiro Crew independently supports the episode that persistent workspaces and cross-session state are becoming core coding-agent harness features.
2026-09-11T13:22:04Z
evidence attached: hn.story.49657908 — The released MCP-backed repository state system is a concrete implementation of explicit, versioned continuity across coding-agent sessions.
2026-09-11T02:24:39Z
Refreshed discussion adds no distinct continuity result: instruction-following anecdotes, handoff practices, and provenance advice remain background to the already-known external-state pattern. The named protocol remains unvalidated; adjacent activity should not substitute for protocol-specific evidence or sustain frequent review.
2026-09-10T10:28:02Z
Refreshed comments mix anecdotal instruction-following failures with reports of consistency, without distinguishing lost state from ignored instructions or demonstrating recovery. They add no validation of the named protocol and do not change Scott’s established external-state approach.
2026-09-10T08:28:33Z
The new continuity survey reiterates familiar symptoms of state loss, rather than demonstrating recovery or identifying a new failure mode. It adds no validation of the named protocol; accumulating adjacent discussion should not advance this case’s maturity or keep it on a frequent review cycle.
2026-09-10T08:22:23Z
evidence attached: reddit.post.1wccz9t — The reported continuity failures provide user-level evidence for the problem that externalized, recoverable agent state is meant to solve.
2026-09-10T03:27:47Z
Ambient Context’s maker-announced signed macOS release adds a concrete upstream capture mechanism—screen text organized into app, website, and message Markdown files—not evidence of reliable agent-state restoration. It is an adjacent implementation worth retaining for routine research, while refreshed discussion adds no validation of the named protocol or resolution of its freshness and retrieval limits.
2026-09-10T00:22:37Z
evidence attached: hn.story.49636194 — The released macOS artifact provides concrete evidence for externalizing ambient context into durable files and knowledge bases for assistant continuity.
2026-09-09T19:41:29Z
The new persistence-project submission is a title-only discovery lead, not evidence of a working continuity mechanism or validation of the named protocol. Adjacent projects continue to accumulate without changing this case’s meaning or Scott’s existing external-state approach.
2026-09-09T19:23:23Z
evidence attached: hn.story.49631429 — A concrete persistence project bears directly on the open question of externalizing and preserving agent state across sessions.
2026-09-09T10:25:13Z
The refreshed blackboard comments add speculative claims about multi-agent superiority and familiar shared-state examples, not tested continuity results. This remains an unvalidated protocol claim surrounded by adjacent architectural discussion; that discussion should not keep triggering frequent review.
2026-09-09T07:25:15Z
The refreshed blackboard discussion adds a builder's pointer to an existing coordination library, not a demonstrated continuity result or a new release. Adjacent implementations remain research leads; they do not establish this protocol's adoption, model independence, or reliability.
2026-09-09T06:24:49Z
Refreshed blackboard comments add an adjacent append-only Git-log implementation lead, but no tested continuity result beyond the already-recorded coordination-versus-durable-state distinction. This remains architectural discussion around an unvalidated protocol, not evidence of its adoption or reliability.
2026-09-09T05:28:51Z
The blackboard comments add a concrete architectural distinction worth checking: keeping transient coordination outside source control while committing distilled plans and implementation records. This remains commenter testimony about an adjacent workflow, not validation of the named protocol or evidence of reliable continuity at scale.
2026-09-09T02:27:14Z
The martinfowler.com link adds a credible architectural research lead, but the supplied title-only evidence establishes no concrete finding or connection to the named protocol. Broader external-state discussion continues to accumulate without advancing protocol-specific validation or changing Scott’s existing approach.
2026-09-09T02:22:38Z
evidence attached: hn.story.49579482 — Fowler's discussion of a shared blackboard as agent state materially contextualizes docs-first continuity and coordination workflows.
2026-09-09T01:23:30Z
Refreshed handoff comments add anecdotal use of existing skills and repository-backed state, not a new continuity mechanism or tested result. They reinforce the familiar architecture without validating the named protocol or resolving its retrieval and freshness limits.
2026-09-08T18:24:58Z
The four-month Markdown workflow account adds longitudinal testimony for the broader architecture, while the cross-tool handoff checklist adds guidance rather than a demonstrated result. Neither tests the named protocol or resolves its freshness and retrieval limits, so accumulating adjacent examples does not advance this case’s maturity.
2026-09-08T17:23:23Z
evidence attached: reddit.post.1wats4y — This practical handoff workflow independently supports externalized, docs-first state for continuity across coding-agent sessions.
2026-09-08T15:23:05Z
evidence attached: reddit.post.1waqsrz — This independent four-month field report supports plain Markdown files and shared instruction conventions as a practical cross-agent continuity mechanism.
2026-09-08T13:38:57Z
The refreshed cross-project discussion adds familiar folder-level instructions and repository indexes, not evidence that this protocol preserves continuity. Architectural discussion continues to accumulate around an unchanged, unvalidated protocol claim; it does not justify promotion or frequent review.
2026-09-08T10:28:07Z
Refreshed comments reiterate familiar cross-project routing and maintained handoff-file practices, without adding a demonstrated continuity result or a new failure mode. They do not validate the named protocol, and adjacent architectural discussion should not advance its maturity.
2026-09-08T09:30:12Z
The new reports sharpen a practical boundary: durable state must be discoverable across projects and captured outside tool-local plan storage, not merely written to files. Operating Memory adds an adjacent query-layer announcement, but neither it nor the handoff testimony validates the named protocol or demonstrates reliable freshness and state restoration.
2026-09-08T09:23:10Z
evidence attached: hn.story.49607580 — A local Markdown-backed queryable store is a concrete implementation of externalized, portable agent state and materially informs the continuity hypothesis.
2026-09-08T08:22:36Z
evidence attached: reddit.post.1wahp5q — The report independently reinforces repository-backed plans and session state as a practical, portable continuity mechanism for coding agents.
2026-09-08T08:22:36Z
evidence attached: reddit.post.1wahpgp — Independent user experience supports the case that externalized handoff documents can preserve continuity across long coding-agent sessions and projects.
2026-09-08T06:32:28Z
Portable Resume adds a concrete builder-announced implementation of cross-tool handoffs from local session histories, distinct from maintaining durable docs-first state. It offers an adjacent test candidate but neither validates the named protocol nor demonstrates reliable state restoration, freshness handling, or model independence.
2026-09-08T06:22:14Z
evidence attached: reddit.post.1wag3ut — Portable Resume is an independent released implementation of cross-agent session continuity and materially bears on the existing continuity hypothesis.
2026-09-07T13:23:54Z
Refreshed comments frame Git-as-cache as familiar incremental indexing rather than adding evidence of reliable state restoration or measured token savings. The named protocol remains unvalidated; adjacent discussion does not advance its maturity.
2026-09-07T12:35:49Z
The Git-as-cache report adds an adjacent incremental-indexing idea, not demonstrated cross-session continuity; its claimed 90% token savings lack supporting measurements in the supplied evidence. It does not validate the named protocol or resolve the distinction between avoiding repeated reads and reliably restoring agent state after context loss.
2026-09-07T12:23:40Z
evidence attached: reddit.post.1w9pk21 — The Git-as-cache pattern is a concrete implementation of externalizing agent state to reduce repeated context loading and preserve continuity.
2026-09-06T13:24:47Z
The latest Rune item repeats an adjacent project's discovery lead, while refreshed comments reinforce the existing need for explicit freshness checks and authoritative sources in external memory. Neither adds validation of the named protocol, demonstrated continuity gains, or a solution to its unresolved retrieval and staleness limits.
2026-09-06T13:22:32Z
evidence attached: hn.story.49586035 — A released project addressing coding-agent memory between sessions materially bears on the open hypothesis that externalized state can preserve long-running agent continuity.
2026-09-05T23:26:00Z
The new persistent-codebase-understanding item adds a discovery lead, not implementation evidence or a demonstrated continuity result. Adjacent projects continue to illustrate the broader external-state pattern without validating this protocol’s reliability, model independence, or adoption.
2026-09-05T23:22:21Z
evidence attached: hn.story.49581382 — The hunted GitHub project is directly relevant to persistent codebase understanding and continuity across coding-agent sessions.
2026-09-05T21:25:01Z
Crbro’s announcement adds a separate implementation claim with explicit supersede/retract operations, addressing the previously identified stale-state problem rather than merely persisting more documents. It neither validates this protocol nor demonstrates that retraction reliably prevents stale-state retrieval, so protocol-specific maturity remains unchanged.
2026-09-05T21:22:22Z
evidence attached: hn.story.49580477 — This concrete file-backed MCP memory artifact independently supports the case that externalized, retractable state is becoming a practical pattern for agent continuity.
2026-09-05T17:28:41Z
The refreshed handoff discussion repeats known practices rather than adding a tested continuity result. Correcting the maturity assessment: independent reports corroborate the broader external-state pattern, not this protocol, whose release is represented only by echo testimony and whose reliability remains unvalidated.
2026-09-04T16:33:07Z
The refreshed comment adds no substantive implementation detail, validation, or new failure mode; it is repetitive discussion around already-known staleness risks. The broader external-state pattern remains corroborated, while the named protocol’s reliability and adoption remain unverified.
2026-09-04T14:34:34Z
The new reports strengthen the boundary condition rather than the protocol claim: externalized state can itself become a source of failure when stale repository artifacts are treated as authoritative. They add no protocol-specific use, measured reliability, or adoption, so the case remains corroborated only as a broader architecture pattern.
2026-09-04T14:22:56Z
evidence attached: reddit.post.1w74zup — Stale repository artifacts are direct contextual evidence for the open case's challenge of maintaining reliable external agent state.
2026-09-04T14:22:56Z
evidence attached: reddit.post.1w75fgh — This concrete continuity failure reinforces the open case's question of whether externalized, auditable state can prevent stale facts from dominating long-running multi-model workflows.
2026-09-04T09:29:35Z
The refreshed discussion remains repetitive support for distilling plans into durable artifacts before clearing context. It adds no measured outcome, adoption, or validation of the named protocol, leaving the case corroborated only at the broader architectural-pattern level.
2026-09-04T00:28:16Z
Refreshed comments repeat the established practice of starting implementation from a distilled plan or project-state file after clearing chat context. They add no measured outcome, named-protocol validation, or answer to the known retrieval and staleness limits of docs-first memory.
2026-09-03T23:34:19Z
The planning-thread report reinforces the broader practice of distilling approved state into durable artifacts before resetting context, but adds no measured result or validation of the named protocol. The case remains corroborated only at the architectural-pattern level, with docs-first scaling and retrieval limits unresolved.
2026-09-03T23:22:25Z
evidence attached: reddit.post.1w6m6d5 — The report that discarded planning history degrades implementation accuracy materially contextualizes the case for externalized, distilled agent state.
2026-09-03T20:35:46Z
Refreshed comments sharpen the handoff pattern—committed plans, provenance-bearing manifests, and separation of evidence from executable actions—but largely repeat architecture already captured. They add no validation of the named protocol or evidence that docs-first continuity remains reliable at scale.
2026-09-03T18:53:12Z
Independent reports now corroborate the broader pattern that durable project artifacts and explicit handoffs can preserve continuity across sessions and agents. They still neither use nor validate the named protocol, and the known retrieval, staleness, and scaling limits of docs-first memory remain unresolved.
2026-09-03T18:23:49Z
evidence attached: reddit.post.1w6eyje — A concrete agent-to-agent handoff workflow bears on whether externalized state can preserve continuity across long-running coding sessions.
2026-09-03T17:24:35Z
evidence attached: reddit.post.1w6d0sa — The report provides firsthand context on persistent project state and knowledge-base workflows addressing cross-session continuity.
2026-09-03T09:28:59Z
Refreshed comments merely reinforce the already-recorded failure mode: growing Markdown stores suffer inconsistent retrieval and stale facts, while deterministic databases, indexes, and executable rules can help. No new evidence validates the named protocol or materially changes the architecture assessment.
2026-09-03T05:25:55Z
The new field report adds an important boundary condition: durable Markdown can preserve continuity yet become unreliable as document volume, retrieval ambiguity, and staleness grow, pushing mature systems toward deterministic indexes, databases, or executable rules. This informs the architecture but still does not validate the named protocol’s implementation or robustness.
2026-09-03T01:21:56Z
evidence attached: reddit.post.1w5s8dx — Long-running Claude Code use exposes failures from scaling Markdown-based project context, materially informing the case about externalized agent state and retrieval.
2026-09-02T23:35:31Z
An independent field report upgrades this from a bare maintainer claim to a concrete example of the same docs-as-memory architecture working across sessions. It does not use or evaluate the named protocol, so protocol-specific continuity, robustness, and adoption remain unvalidated.
2026-09-02T23:22:24Z
evidence attached: reddit.post.1w5qhff — Independent real-world use supports the case that living repository documents can preserve coding-agent continuity across sessions.
2026-09-01T01:28:39Z
The reobservation adds no validation, implementation detail, or adoption; this remains an untested implementation claim closely overlapping Scott’s established external-state approach.
2026-09-01T01:26:55Z
grounded: known/low — Scott’s “Long-Running Agents” and “Markdown OS” pages already state the same core position: stateless workers resume from durable, inspectable external artifact
2026-09-01T01:24:02Z
case created — The linked first-party repository is a usable continuity artifact with a distinct implementation claim, though it has not yet attracted validation or discussion.