derive-min-antecedents-is-prompt-only
IN premise
The minimum-2-antecedents rule for derived beliefs is enforced only by the LLM prompt instructions, not validated in code by `validate_proposals`.
Summary
The system relies on the LLM following its prompt to require at least two supporting beliefs when generating a derived belief, but there is no programmatic check that actually enforces this rule. If the LLM ignores the instruction and proposes a derivation from a single antecedent, the system will accept it without complaint.
Dependents
These beliefs depend on this one:
- complete-quality-lifecycle-spans-creation-through-egress — The complete belief quality lifecycle — automated self-correction maintaining consistency, explicit review validating derived beliefs, and governed resilient egress controlling all output — forms an unbroken chain where quality is enforced at creation, validated during maintenance, and preserved through output.
- derive-pipeline-has-end-to-end-quality-enforcement — The derive pipeline achieves end-to-end quality enforcement: defensive validation prevents invalid proposals, Jaccard retraction guards prevent re-derivation of known-bad conclusions, budget allocation is accurate, AND the minimum-antecedents rule for derived beliefs is enforced in code — not just as an LLM prompt instruction that can be ignored.
- 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.
- llm-belief-pipeline-is-fully-quality-enforced — The system's complete LLM-driven belief pipeline — both generation (derive with safety, completeness, and coverage) and classification (list_negative with defensive bounding) — achieves fully code-enforced quality constraints at every stage, provided minimum-antecedent validation moves from prompt-only to code-enforced.
- review-driven-quality-lifecycle-is-fully-code-enforced — The complete LLM-driven quality lifecycle — creation via derive with structural validation and retraction guards, classification via list-negative with defensive bounding, and evaluation via review with scoped mutation safety — achieves full code enforcement of all quality constraints, but only when the derive pipeline's minimum antecedent requirement is enforced in code rather than prompt-only.
- revision-has-code-enforced-derivation-constraints — The deterministic traceable revision system with complete dialectical semantics achieves fully code-enforced derivation quality — every constraint including minimum antecedent requirements is validated programmatically, not relying solely on LLM prompt instructions for structural invariants.
Details
| Source | entries/2026/04/29/reasons_lib-derive.md |