# The algo records whose domain is quality-engine

This index as JSON: https://banes-lab.com/json/api/facets/algo/domain/quality-engine

## Entries

- [Quality Governance Loop](https://banes-lab.com/records/algo/quality-governance-loop.md): On each update (an apply), normalize the proposal, resolve a CheckPlan, verify it, and on failure fix-then-reverify the downstream set until the verdict is clean or the pass bound is reached, then escalate.
- [Canonical Config Resolution](https://banes-lab.com/records/algo/canonical-config-resolution.md): Expand one canonical config across selected profiles and native rules into per-tool config, resolve exactly one owner per contested surface, detect the four conflict kinds fail-closed, route loosening or self-certification to the developer's gate, and emit a resolved plan.
- [Stage Ordering](https://banes-lab.com/records/algo/stage-ordering.md): Build the runnability DAG from dependsOn, topologically order the cascade by the invalidates relation so fixes point forward, partition into normalization prefix, structural band, and semantic suffix, and permit back-edges only inside the suffix.
- [Comment Normalization Remediation](https://banes-lab.com/records/algo/comment-normalization-remediation.md): Express the comment-strip rule once as canonical behavior, bind it per language from a comment-grammar descriptor, run the toolchain-free token-scan backing on the in-memory proposal and the real-AST backing in the sandbox, preserve directive comments, and trust a backing only after calibration and adversarial testing.
- [Custom-Rule Derivation](https://banes-lab.com/records/algo/custom-rule-derivation.md): Derive a candidate rule from repeated evidence through anti-pattern classification, boundary-principle evaluation, and candidate selection, migrate with rollback, verify elimination, and admit a tightening rule while routing a self-certifying or loosening rule through the developer's gate.
- [Machine Verdict Derivation](https://banes-lab.com/records/algo/machine-verdict-derivation.md): Derive the verify-stage verdict from the toolchain's machine output — exit codes and parsed findings — never from the model's reading, so a clean verdict is an observed machine fact.
- [Bounded Cascade Termination](https://banes-lab.com/records/algo/bounded-cascade-termination.md): Terminate the verify-remediate cascade on the completion AND-gate — a clean verdict, or bounded progress where findings strictly decrease within the pass bound — escalating when neither holds.
- [Quality-Engine Kernel](https://banes-lab.com/records/algo/quality-engine-concern.md): Resolve a canonical policy into a per-ecosystem CheckPlan, order its stages by the invalidates relation, normalize the proposal, run generation checks on the server and project tools via the relay, derive a machine verdict, and drive a bounded downstream cascade to clean — holding no runtime execution in the engine itself.