V · MemoryEmerging★

Unstructured Human Capture Layer

also known as Human Dump Layer, Read-Only Raw Notes Layer, Two-Layer Capture (Dump / Knowledge)

Keep a human-authored raw dump layer that the agent may read but never edit, and confine all structuring to a separate derived layer, so half-formed human thought survives as durable context.

Context

A person works alongside an agent over weeks and keeps notes — half-formed ideas, contradictions, dead ends, observations recorded before they have hardened into a position. The agent has memory tools and is eager to help: it tags, reformats, deduplicates, and reorganises whatever it can write to. The notes are valuable to the agent as context, so the temptation is to fold them into the agent's tidy knowledge store. The moment the agent normalises a half-formed note, the raw material the person was still thinking through is gone.

Problem

Unstructured human thought and a structured knowledge base have opposite requirements, and a single shared store cannot satisfy both. Tagging, choosing headings, and aligning format all force a premature commitment that discards the loose, contradictory, still-forming material that gave the note its value. Yet the agent does need structure to retrieve and reason over the corpus. If the agent is allowed to rewrite the human's raw notes, it strips them down to whatever it could already articulate; if the agent is forbidden to structure anything, the corpus stays unsearchable. The capture surface and the retrieval surface pull in incompatible directions over the same data.

Forces

  • Structuring a note — tags, headings, a fixed format — is exactly what makes it retrievable, and exactly what kills the half-formed material the human was still working out.
  • The agent is more capable at organising than the human and will, given write access, normalise the raw layer toward what it can already express.
  • The corpus is useless to the agent as one undifferentiated pile, yet equally useless if every entry has been flattened into the agent's own categories.
  • Contradictions, dead ends, and unresolved hypotheses carry signal, but only survive if no consistency pass is run over the layer that holds them.

Example

A researcher keeps a daily/ folder of rough, dated notes — stray observations, contradictory takes, ideas not yet worth defending. The agent is mounted with read-only access to daily/ and read-write access to a separate knowledge/ folder. Each day it reads the new dumps and grows knowledge/: an index and a few theme clusters that cite the raw entries. When it spots a likely typo in a dump note, it proposes the fix to the researcher rather than editing it, leaving the rough material exactly as written.

Diagram

Solution

Therefore:

Maintain two distinct layers over the same body of notes. The dump layer is human-authored and deliberately unstructured: dated free-form entries, kept rough on purpose, holding contradictions and unfinished thoughts. The agent has read access to this layer and nothing more — it may quote, cite, and reason over a dump entry, and it may propose changes for the human to apply, but it cannot write, tag, reformat, or reorganise it. The knowledge layer is separate and derived: an index, theme clusters, and structured notes that the agent reads the dump to build and maintain. When the agent learns something from the raw layer, it writes the structured form into the knowledge layer and leaves the source untouched, linking back to the dump entry rather than absorbing it. The enforcement is at the tool boundary, not the prompt: the agent is granted read-only access to the dump path and read-write access only to the derived path, so the rough material is structurally safe from the agent's own tidiness.

What this pattern forbids. The agent may read but must never edit, tag, reformat, or restructure the human dump layer; any change to the raw layer is proposal-only and applied by the human, and all structuring the agent performs is written to a separate derived layer.

And the patterns that stand alongside it, or against it —

  • complementsAppend-Only Thought Stream★— Make the agent's thought log append-only so the agent cannot rewrite its own history.
  • alternative-toScratchpad★★— Give the agent a writable scratch space for intermediate notes that informs later turns but does not pollute the response.
  • complementsFilesystem as Context★— Use the filesystem as the agent's externalized working memory, writing plans, notes, and large tool outputs to files, dropping them out of the live window, and re-reading on demand.
  • alternative-toTacit-Knowledge Elicitation Agent★— Run a front-loaded phase in which an agent interviews domain experts and converts their undocumented know-how into a structured, queryable knowledge base before downstream task agents read from it.

Neighbourhood

Click any neighbour to follow the language. Scroll to zoom, drag to pan.

References

Provenance