- *.archify-decision files: id (unique, words), title, status, date, elements, diagrams, supersedes, and prose; parsed, merged and link-checked in the model index; diagnostics on the file - diagrams point at decisions with decisions: [...] on the diagram, nodes and edges; stripped before Archify, unknown ids reported, completion, hover and go-to-definition for the ids and for elements/diagrams/ supersedes in decision files - Decisions panel on the main.archify page; Decisions rail panel under a diagram (hover lights up the node or connection); decisions on element cards and in the element dialog; decision view for the file, with a lost-model note outside a model - Archify | New Decision… command and template; editor schemas; the three New Model examples carry decisions; docs, changelog, 0.8.0
21 lines
778 B
Plaintext
21 lines
778 B
Plaintext
schema_version: 1
|
|
decision:
|
|
id: postgres-as-source-of-truth
|
|
title: PostgreSQL as the single source of truth
|
|
status: accepted
|
|
date: 2026-09-02
|
|
elements: [db, api, worker]
|
|
diagrams: [0200-containers/online-shop.archify]
|
|
context: >
|
|
Orders, customers and the catalogue were spread over the
|
|
shop database and two spreadsheets kept by support.
|
|
Refunds were reconciled by hand every Monday.
|
|
decision: >
|
|
One PostgreSQL database owns orders, customers and the
|
|
catalogue. The API is the only writer. Everything else
|
|
(cache, search, reports) is derived and may be rebuilt.
|
|
consequences: >
|
|
Support loses the spreadsheets and gets the admin console.
|
|
Any new store must be declared derived or get its own
|
|
decision. Backups and migrations are the API team's job.
|