Skip to content

refactor: rename backoff to cooldown and make guardrail thresholds configurable#112

Merged
tosh2230 merged 4 commits intomainfrom
refactor/cooldown-terminology
May 1, 2026
Merged

refactor: rename backoff to cooldown and make guardrail thresholds configurable#112
tosh2230 merged 4 commits intomainfrom
refactor/cooldown-terminology

Conversation

@tosh2230
Copy link
Copy Markdown
Collaborator

@tosh2230 tosh2230 commented May 1, 2026

  • Rename backoff to cooldown in guardrail module
  • Make guardrail thresholds configurable via nagi.yaml: maxConsecutiveSyncFailures, cooldownInitialSecs, cooldownMaxSecs
  • Add validation rejecting zero values
  • Restructure Guardrails docs with state/transition tables for Cooldown, Suspend, Halt
  • Fix notification event names to match code

…nfigurable

Rename backoff terminology to cooldown throughout the guardrail module
to align with the design principle that the reconciliation loop is a
convergence mechanism, not a retry mechanism.

Make the three previously hardcoded guardrail thresholds configurable
via nagi.yaml:
- maxConsecutiveSyncFailures (default: 3)
- cooldownInitialSecs (default: 30)
- cooldownMaxSecs (default: 1800)

Add validation to reject zero values for these fields.
Restructure the Guardrails section in concepts with state/transition
tables from the cooldown design proposal. Add Cooldown to the glossary
as an Asset state, move Halt and Resume to the Operations section.

Fix notification event names to match code: EvalFailed -> EvaluateFailed,
remove Halted (no corresponding NotifyEvent in code).
@tosh2230 tosh2230 merged commit edd273e into main May 1, 2026
18 checks passed
@tosh2230 tosh2230 deleted the refactor/cooldown-terminology branch May 1, 2026 10:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant