Skip to main content

Module provenance

Module provenance 

Source
Expand description

Where content came from.

agentplane’s gates — what may go to which model, which arguments may drive a mutating tool — decide on labels. So every value speccoder hands the runtime says where it came from: speccoder’s own instructions and the person’s committed spec and decisions are trusted; a check’s output, the worktree’s content, an MCP server’s words and the model’s answers are not.

Labels are given where content enters — a skill input is assembled from labelled parts — and read back with label_at, never inferred from what the content looks like: agentplane journals the field labels a run was admitted with (0.50), live and in replay.

Constants§

GITHUB_ISSUE
A GitHub issue’s title and body, fetched for a bug (--issue N): anyone who can open an issue wrote them — outside content, not the worktree’s.
PERSON
A person’s answer to a question: their input, not speccoder’s; who they were is on the decision’s record, not in the label.
VERIFIER
Check output quoted in a retry digest: the verifier’s facts.
WORKTREE
Worktree content speccoder inlines into a prompt (a patch, files, a manifest).

Functions§

from
An untrusted label from source.
labelled_prompt
A prompt whose /system is speccoder’s constant instruction (trusted) and whose every other part carries label.
tool
The source of a tool’s results and of an MCP tool’s description.