Skip to content

Configurable Features ​

edikt's governance core — rules, compiled directives, drift detection, review-governance — is always on. That's the product.

Five optional behaviors run on top, each an on/off flag. Each can be turned off in .edikt/config.yaml for teams that want a lighter touch or have their own tooling for that concern.

The features ​

yaml
# .edikt/config.yaml
features:
  auto-format: true        # format files after every edit
  session-summary: true    # git-aware "since your last session" on start
  signal-detection: true   # detect ADR/invariant candidates on stop
  plan-injection: true     # inject active plan phase on every prompt
  quality-gates: true      # block on critical findings from gate agents

All five default to true. Set one to false to disable it.

auto-format ​

Runs the appropriate formatter (gofmt, prettier, black, rubocop, rustfmt) after every file edit. Disable if your CI handles formatting or your team uses a different formatter setup.

yaml
features:
  auto-format: false

Environment variable override: EDIKT_FORMAT_SKIP=1

session-summary ​

Shows what changed since your last session when you open the project — modified files, relevant agents, active plan phase. Disable if you prefer a clean start with no preamble.

yaml
features:
  session-summary: false

signal-detection ​

After every response, scans for uncaptured architectural decisions and suggests /edikt:adr:new or /edikt:invariant:new. Disable if the suggestions feel noisy or your team captures decisions through a different process.

yaml
features:
  signal-detection: false

plan-injection ​

Injects the active plan's current phase into every prompt so the model always knows where it is in the execution plan. Disable if you're not using plans or prefer to load context manually.

yaml
features:
  plan-injection: false

quality-gates ​

When a specialist agent configured as a gate (e.g., security) finds a critical issue, it blocks progression until the finding is resolved or explicitly overridden. Disable if you want agents to advise without blocking.

yaml
features:
  quality-gates: false

Setting quality-gates: false also disables the stop-hook completion-claim detector (v0.6.0). When enabled (the default), the stop hook scans each assistant message for completion phrases (✓, Done!, All tests pass, Phase N complete, …) and — if there's an in-progress plan phase — emits a non-blocking systemMessage suggesting bin/edikt verify <plan-id> --phase <N>. With the flag off, the detector stays silent. See Gates for details.

evidence-gate — removed in v0.9.0 ​

features.evidence-gate was the posture dial (block | warn | educate | disabled) for the verify-gate PreToolUse hook, which watched for completion-claim edits — flipping a sidecar to passes: true, marking a plan row done, ticking an AC-NNN checkbox — and acted on them before they landed (ADR-062).

The hook is retired and the key is removed (ADR-083). verify-gate.sh is no longer shipped, features.evidence-gate is no longer read, and /edikt:config no longer lists it. Leaving it in an upgraded config changes nothing; edikt doctor will tell you if .claude/settings.json still registers the hook itself.

INV-009 — no completion claim without fresh verification evidence in the same turn — is unchanged and reaches the model through the ambient core on every edit. The non-blocking completion-claim detector under quality-gates above still fires at Stop, bin/edikt verify <plan-id> --phase <N> still produces the evidence a claim is meant to rest on, and edikt doctor now names any behavioral verify still missing its human_approved_at approval instead of letting it read as approved.

See Gates → The retired pre-edit gate and Falsifiable verification → The retired pre-edit gate for the full history.

Evaluator ​

The evaluator validates acceptance criteria at two points: pre-flight (before a phase starts, checking the criteria are testable) and phase-end (after completion, verifying the work meets them). Both points, plus the execution mode, retry ceiling, and model, are configured under evaluator: in .edikt/config.yaml. Setting both preflight and phase-end to false disables it — the criteria sidecar is still emitted.

See Evaluator for the config keys, their defaults, and the headless-vs-subagent comparison.

What's always on ​

These are not configurable — they're the governance core:

FeatureWhy it's always on
Rule loadingRules in .claude/rules/ load automatically — this is Claude Code's behavior, not edikt's
Compiled directives/edikt:gov:compile output loads as a rule file — same mechanism
Drift detection/edikt:sdlc:drift is a command you run explicitly, not a background behavior
Review-governance/edikt:gov:review is a command you run explicitly
PreToolUse guardRefuses an edit that would change an edikt-managed region (INV-005), and warns if docs/project-context.md is missing
Context recoveryPreCompact saves plan state, and SessionStart re-injects it after compaction. Turning this off would lose that state.

Event logging ​

edikt writes a structured event log to ~/.edikt/events.jsonl. This is always on and not configurable — it's the audit trail.

Events logged:

  • Quality gate firings and overrides (with git identity of the approver)
  • Invariant violations detected by the pre-push hook
  • Status changes on governance artifacts (PRD accepted, spec created, etc.)

Each entry is a JSON line with an ISO 8601 timestamp, event type, and relevant context. The file lives at the machine level (not committed to git) and is used by /edikt:status to show gate and agent activity for the current session.

Checking feature status ​

bash
/edikt:doctor

Doctor reports which features are enabled and which are disabled.

For teams ​

Feature settings are in .edikt/config.yaml which is committed to git. The whole team shares the same configuration. If your team disables signal-detection, everyone gets a quiet stop hook.

Released under the Elastic License 2.0. Free to use, not for resale.