Coding OS
Sign in
Browse docs▾

Risk Register

Purpose: Canonical list of active project, architecture, and workflow risks that still require mitigation or follow-up. Read when: Planning work, reviewing blind spots, or deciding whether a task can proceed safely. Skip when: The task is tightly scoped and all relevant risks are already captured in the task file. Read next: Relevant ADR in ../architecture/adr/ or the domain architecture doc.

Nav: Docs Index | ADR Index

Active Risks

(empty — populate as risks are identified)

Usage Rules

  • Risks stay here while active.
  • Once resolved, move the resolution into the relevant ADR, architecture doc, or change log entry and remove or downgrade the risk.
  • Historical risk analysis belongs in archive docs, not active architecture indexes.
  • Each risk needs an ID (RISK-NNN), a one-line description, and ideally an owner and mitigation plan.
  • Each risk MUST carry a review-by: YYYY-MM-DD date and a tracking: ref (task or issue); make docs-lint flags a missing field or a past-due review-by so a stale risk is re-triaged, not silently accumulated.