Project

General

Profile

Actions
Copy link

csAdr #4 | YANK-0001 · ADR-0001

closed
AM

Record architecture decisions

csAdr #4 | YANK-0001 · ADR-0001: Record architecture decisions

Added by Ana Manager about 4 hours ago. Updated about 4 hours ago.

Status:
Accepted
Priority:
Normal
Number:
ADR-0001
Format:
MADR
Date:
10/15/2026
Decision makers:
tech lead
Consulted:
backend team
Supersedes:
-
Content:
Locked
Status:
Accepted
Informed:
everyone
Superseded by:
-

Description

Context and Problem Statement

How do we keep track of the decisions that shape Yank? We follow Meta › ADR-0001 Record architecture decisions Accepted.

Considered Options

  • ADRs in cosmoSys
  • Wiki pages
  • Nothing

Decision Outcome

Chosen option: "ADRs in cosmoSys", because they live next to the issues that implement them.

Consequences

  • Good, because decisions get an owner, a status and a history.
  • Bad, because writing them takes discipline.

Hierarchy

Loading diagram...

Dependencies

Loading diagram...

Combined

Loading diagram...

Document catalog

Document references

No data to display

Your roles cannot decide on this ADR. In this project the decision belongs to: Manager, Developer.

Linked issues

ProjectItemStatusOrigin
Yank Feature #YANK-0008: Move sync state to PostgreSQL New Mention

AM Updated by Ana Manager about 4 hours ago Actions
Copy link
 #1

  • Status changed from Proposed to Accepted
Actions
Copy link

Also available in: PDF Atom