Concepts
Signal
Section titled “Signal”A clue that something may have changed or degraded. Signals can come from alerts, metrics, logs, traces, errors, deploys, pull requests, configuration changes, or webhooks.
Operational Context
Section titled “Operational Context”The surrounding context needed to investigate a signal. This can include affected services, environments, ownership, dependencies, recent changes, telemetry, and related past events.
Evidence
Section titled “Evidence”A traceable fact used to support or challenge a hypothesis. Evidence should keep its source, source URL, capture time, confidence, and raw reference when available.
Hypothesis
Section titled “Hypothesis”A candidate explanation for what is happening. A hypothesis is useful only when it is connected to supporting evidence, disconfirming evidence, and next checks.
Handoff
Section titled “Handoff”A reviewable investigation artifact that transfers the current state of understanding to a responder or AI coding agent. A Handoff should include symptoms, affected scope, leading hypotheses, evidence, uncertainty, next checks, relevant action candidates, and any created branch / PR / validation context.
Action Candidate
Section titled “Action Candidate”A possible next action, such as rollback, configuration change, feature flag adjustment, code repair, or PR creation. In the first release, Daran can autonomously create branches and GitHub PRs inside scoped application repositories. Production-impacting actions require explicit approval with evidence, blast radius, validation, and rollback guidance.