LogForge

// software.repair.verification

AI can write the patch.
Cirdan proves it repairs the incident.

Cirdan turns a production alert into a controlled repair trial: reproduce the failure, contain the change, challenge the regression, and release only what the evidence supports.

Request early access Follow the repair
target bound failure proven repair gated
incident / checkout-api live
An alert activates Cirdan and moves through the repair pipeline A pulsing alert light enters Cirdan, activates the repair agent, then continues through reproduce, repair, and verify stages before reaching a verified pull request. ALERT checkout-api CIRDAN ACTIVATED REPRODUCE REPAIR VERIFY VERIFIED PR ALERT RECEIVED REPAIR VERIFIED

// immutable.evidence.chain

A repair has to earn the next step.

The model proposes. The repair contract decides. Missing evidence never becomes model confidence, and a failed gate becomes a clear manual handoff.

  1. 01
    Bindexplicit service + repository target
  2. 02
    Baselinesame pinned probe must fail first
  3. 03
    Containauthorized change surface only
  4. 04
    Challengeregression proof + specialist review
  5. 05
    Gateverified PR or manual required

// category.delta

The difference is not the AI.
It is what must be true before Cirdan trusts it.

Investigation, root-cause analysis, remediation suggestions, and generated pull requests are becoming table stakes. Cirdan is built around the harder part: proving that a proposed code change repairs this incident without creating the next one.

COMMON AI SRE LOOP investigate → explain → suggest → act

The model's conclusion remains the center of trust.

CIRDAN REPAIR CONTRACT bind → reproduce → contain → challenge → verify

Deterministic evidence gates—not model confidence—decide whether a repair advances.

  1. 01 / TARGET Bound before touched

    An explicit service registry fixes the repository, runtime, probes, and permissions in scope.

  2. 02 / FAILURE Proven before patched

    The pinned incident probe must fail in an isolated Compose or Kubernetes runner.

  3. 03 / CHANGE Contained before tested

    The patch is checked against its authorized change surface and integrity rules.

  4. 04 / REGRESSION Challenged, not admired

    Counterfactual proof, patch-bound suites, and conditional specialists try to disprove the fix.

  5. 05 / DELIVERY Evidence before privilege

    The same probe must pass after the patch. Failed gates stop at manual_required.

NO DISCOVERY GUESSWORK→ NO UNPROVEN BASELINE→ NO UNBOUNDED PATCH→ NO CONFIDENCE-BASED SHIP

// from.signal.to.change

Keep your stack.
Add a repair contract.

Keep the signals, coding agents, and delivery controls your team already trusts. Cirdan supplies the evidence chain between generated code and production recovery.

// signal.in Grafana
Alertmanager
Slack
// repair.engine CIRDAN
bind baseline challenge gate
// proof.out Verified change pull request + recovery evidence
EARLY ACCESS Put verified repair into your on-call loop.
Request early access