julien/meadows
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs: align design docs and README with the editor

Browse Source
This commit is contained in:
Julien Calixte
2026-06-20 09:37:50 +02:00
parent d3119e8a20
commit 37017c1175
5 changed files with 113 additions and 90 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
docs/adr/0001-detected-feedback-loops.md
View File

@@ -6,7 +6,7 @@ A **Feedback Loop** in a **Model** is a cycle in the wiring (Stock → Informati
Link(s)/Flow → same Stock). We chose to **derive** loops by detecting cycles and
classifying each as **Reinforcing** (even number of `−` polarities) or
**Balancing** (odd), rather than storing them as first-class objects the user
hand-labels. This makes loops *discovered insight* that can never disagree with
hand-labels. This makes loops _discovered insight_ that can never disagree with
the actual structure — the point of a systems-thinking tool.
## Considered Options

4
docs/adr/0003-flow-as-node-materialised-clouds.md
View File

@@ -2,8 +2,8 @@
_Part of [meadows](../../README.md) · see [DESIGN.md](../../DESIGN.md)._
In the domain `Model`, a **Flow** is a *node* carrying `source` and `target`
references (each to a Stock or Cloud), not an edge. The pipe you see is *rendered*
In the domain `Model`, a **Flow** is a _node_ carrying `source` and `target`
references (each to a Stock or Cloud), not an edge. The pipe you see is _rendered_
from those references. The **Source/Sink** boundary is a **materialised Cloud
node**, so every Flow connects node→node uniformly — no `null` ends.