derive-parse-supports-two-formats

IN premise

`parse_proposals` tries the new format first (v0.10+: `### DERIVE id`), falls back to old format (v0.9: `### DERIVE: \`id\``) only when no new-format matches are found

Summary

The proposal parser is backward-compatible: it prioritizes the current heading style but still accepts the older format, so previously generated derivation proposals won't silently break after the format change. This means both old and new LLM outputs will be handled correctly, but mixing formats in a single response is implicitly discouraged since the fallback only activates when the new format finds zero matches.

Dependents

These beliefs depend on this one:

system-tolerates-evolution-at-all-boundaries — The system handles format and schema evolution gracefully at every external boundary: derive output parsers support two format versions with automatic fallback, belief import silently skips unknown metadata fields, and storage tolerates missing tables from older database schemas via exception handling

Details

Source

entries/2026/04/24/tests-test_derive.md