derive-prompt-roundtrips-through-parser
IN premise
The `### DERIVE` / `### GATE` format is a shared contract between `DERIVE_PROMPT` LLM output, `parse_proposals()` input, and `write_proposals_file()` output, forming a closed serialization loop
Summary
The derive prompt, the proposal parser, and the proposal file writer all use the same markdown format with DERIVE and GATE headers, which means LLM output can be parsed and re-serialized without loss. This matters because any change to that format has to be coordinated across all three sites or the pipeline breaks silently.
Dependents
These beliefs depend on this one:
- derive-budget-allocation-is-accurate — The derive pipeline's proportional belief-budget allocation produces correct per-agent token counts
- derive-pipeline-is-production-ready — The derive pipeline correctly allocates budgets, validates proposals defensively, and produces well-formed beliefs through a round-trippable prompt contract.
- derive-quality-is-comprehensively-code-enforced — All derive pipeline quality constraints — structural validation, retraction guards, environment isolation, format contracts, AND minimum-antecedent requirements — are enforced through code-level validation, ensuring no invalid proposals can reach the database regardless of LLM prompt compliance.
Details
| Source | entries/2026/04/23/reasons_lib-derive.md |