Module derived 

Arguments copied from repository content: a call needing a person whose arguments occur verbatim in content the attempt received from a source other than the model, the person and speccoder’s own instructions (file reads, search results, command and check output, MCP results, inlined worktree text) names that source and offers no remembered option — the mechanism by which planted content becomes a standing rule is broken at the prompt.

Pure over journaled data: the parts are the attempt’s tool results and prompt parts as the journal holds them, never the live worktree, so strict replay rebuilds the same sources byte for byte.

Structs

Part

One piece of untrusted content the attempt received.

Constants

KEPT

Sources kept on a request; more counts the rest.

MIN_CHARS

The shortest argv element (after the program) or MCP argument string that is matched; shorter ones (-p, test, build) occur everywhere.

Functions

candidates

What of a call’s arguments is matched: the whole command line (any length), a write’s full path (any length), each argv element after the program and each MCP argument string of at least MIN_CHARS.

part_of

The part a tool result is, if it counts: a read of one of the person’s committed intent files (the spec, the plan, the tasks, the constitution — intent says which) does not, nor does an empty result. tool is the source (tool://fs/read_file); a read is named by its path.

sources

Where the arguments of tool called with arguments were copied from: for each part that holds one verbatim, the longest such argument — in order of turn, then of arrival — at most KEPT, with the count of the rest.

text_of

Every string in v, joined by newlines: what a tool result says, without JSON’s escaping (a quote in a README is a quote here).