defaults.yml

# defaults.yml
# Org-default universal gates. Every consuming repo inherits these unless its profile
# overrides a specific one with a reason. Gates marked (stubbed) have their contract
# specified but no working logic this sprint; they are Phase 1+.

# Adoption-Ramp-1: every gate's tier (see profiles/_schema.yml's `gates[].tier` /
# `polarity.tier` / `claude_contract.tier`) defaults to "advisory" when a profile
# doesn't declare one -- consuming `resolve_tier` in
# packages/konjo-gates-py/src/konjo_gates_py/cli.py. A gate earns "blocking" only after
# meeting BOTH promotion criteria: a passing `rejects_test` kill-test, and a measured
# false-positive rate under a stated ceiling over at least N runs (lib/gate_stats.py).
# This mirrors gate_polarity's own pre-existing default and generalizes it org-wide --
# quality tooling that blocks merge before it has demonstrated it deserves to block
# merge is exactly the failure mode Gate-Tiering-1 (konjoai/lopi) found and fixed.
default_tier: advisory

universal_gates:

  secrets_redact:
    enabled: true
    description: >
      Three-tier secret scan (lib/redact.py) on every Ledger write and on the
      cross-machine state sync before push. HIGH blocks, MEDIUM flags for confirm,
      LOW surfaces. No MEDIUM-to-HIGH promotion.

  supply_chain:
    enabled: true
    stubbed: true
    description: >
      Dependency and provenance checks (lockfile integrity, advisory scan). TODO(phase-3):
      wire the per-stack runners in packages/.

  decision_logging:
    enabled: true
    description: >
      Durable decisions go to the Konjo Ledger (ledger/engine.py) via konjo-decision.
      Append-only, event-sourced, redact-scanned.

  one_way_door:
    enabled: true
    description: >
      Classify hard-to-reverse changes (schema/migration, public-API removal, data
      delete, key rotation, release actions) and require an explicit acknowledgement.
      Implemented in Phase 3: lib/oneway.py + bin/konjo-oneway classify the change; the
      interactive confirm (lib/confirm.py) requires a typed token and logs to the Ledger;
      the CI one_way_door gate in konjo-gates checks for the commit-trailer acknowledgement
      and never prompts.

  net_new_only:
    enabled: true
    description: >
      Strict gates report only net-new findings versus the base ref (bin/konjo-newonly),
      so gates stay on against an existing codebase without blocking on legacy findings.

  prose_lint:
    enabled: true
    description: >
      Editorial gate (lib/prose_lint.py): no em dashes, no AI-tell vocabulary. Blocking
      on article branches, --warn on general docs.

  self_test:
    enabled: true
    description: >
      The gates test themselves against the eval corpus (the meta-gate). Implemented in
      Phase 1 (konjo-eval + evals/runner.py) and wired into the CI plane in Phase 2 via
      the deterministic replay backend (konjo-eval run --replay), so it runs in CI with no
      model and no network. The 30-run paired Wilcoxon prove baseline remains Phase 3.

  prove:
    enabled: true
    description: >
      The perf prove gate (Phase 4). A 30-run paired Wilcoxon signed-rank test renders a
      MERGE / NOISE / REGRESSION verdict; MERGE requires p<0.05 AND a median improvement at
      or above the minimum effect size, so significance alone never merges. konjo-prove
      runs locally on the bench hardware and records the verdict (BENCHMARKS.md, prove.jsonl,
      a Ledger ack, and a MERGE commit trailer). The CI prove gate checks for the MERGE
      trailer on a perf-labeled change and never runs the benchmark.

  specialist_stats:
    enabled: true
    description: >
      Tag a review specialist by its record: ACTIVE, GATE_CANDIDATE (zero findings over
      the sample floor), NEVER_GATE (insurance set), or INSUFFICIENT_DATA below the floor.
      Implemented in Phase 1: lib/specialist_stats.py, fed by lib/review_log.py.