review-pipeline-is-scoped-and-mutation-safe
IN derived (depth 1)
The belief review pipeline restricts evaluation to derived beliefs only (premises excluded) and gates auto-retraction behind the dry-run flag, ensuring review operations are scope-limited and mutation-safe by default.
Summary
The automated review process only examines beliefs that were derived from other beliefs, leaving human-entered premises untouched. Additionally, any automatic retraction of flagged beliefs requires an explicit opt-in and defaults to a safe preview mode that shows what would change without actually modifying the database. Together, these constraints mean that running a review cycle cannot accidentally damage foundational knowledge or make unintended changes.
Justifications
SL — Scope restriction and mutation gating combine to make review a safe batch operation that cannot accidentally modify premises or retract beliefs without explicit opt-in
Antecedents (all must be IN):
- review-only-evaluates-derived-beliefs — `review_beliefs` filters out premises (nodes without justifications); only derived beliefs with at least one justification are sent for LLM review.
- auto-retract-respects-dry-run — The `--auto-retract` flag in the `review-beliefs` CLI is gated by `--dry-run`: when dry-run is active, findings are displayed but no database mutation occurs, even for beliefs flagged as invalid.
Dependents
These beliefs depend on this one:
- derived-belief-pipeline-achieves-code-enforced-quality — The derived belief pipeline — creation via defensive derivation with structural validation, Jaccard retraction guards, and environment isolation, followed by independent review with scope restricted to derived beliefs and mutation gated behind dry-run — achieves completely code-enforced quality assurance including logical soundness validation, only when inference soundness checking is implemented in code rather than relying solely on LLM prompt instructions.
- dual-quality-gates-are-complementary-and-non-mutating — The system enforces belief quality through dual non-mutating gates targeting complementary validity dimensions: review validates logical soundness of derived beliefs (scoped to justified nodes, dry-run gated auto-retraction), while staleness checking validates source currency of all IN beliefs (conservative CI gate with nonzero exit on drift) — neither gate can corrupt network state.
- review-achieves-verified-fault-tolerance — The review pipeline's scoped mutation-safe operation combined with uniform fail-safe output achieves verified fault tolerance across all failure modes — batch failures, missing antecedent references, and malformed LLM responses.
- review-completes-llm-quality-lifecycle — The LLM-driven belief quality lifecycle is complete across all phases: creation via derive (safe, complete, efficient), classification via list-negative (bounded, batch-scalable), and quality evaluation via review (scoped to derived beliefs, mutation-safe, fault-tolerant) — covering belief genesis, categorization, and ongoing quality assessment with no unmonitored phase.
- 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.