Unstructured Human Capture Layer

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.

Solution

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.

When to use

• A human accumulates loose, half-formed notes over time that lose their value once tagged, reformatted, or reorganised.
• The agent needs structure to retrieve and reason over the corpus, but that structure can live in a layer separate from the raw notes.
• The capture boundary can be enforced at the tool layer — read-only on the dump path, read-write on a derived path — rather than relying on the agent to behave.