- description
- The design of d2conf: the mechanisms that realise its specification, for any code base
- tags
- #ai #design
- status
- draft
d2conf: design¶✎ edit
This is Design, the design for d2conf, kept by the designer: the mechanisms that realise the specification, independent of any one code base. Its companions: Spec (what it does), SpecUi (how the UI behaves), Design (the mechanisms), DesignRoutes (the API) and SpecTest (the black-box tests); each code base that builds d2conf keeps its own topics, named after it (e.g. Proto1Impl, Proto1Code, Proto1Routes, Proto1Test).
Goals¶✎ edit
What this topic is for, and how to tell a line belongs here:
- Role: the mechanisms that realise Spec, in terms any build could follow.
- A line belongs here if it would be wrong only if another architecture were picked for the same behaviour.
- It fails if a second build can't follow it without reading the first one's code, if it names files, classes, commits or anything one code base did (those go in that code base's topics), or if it restates behaviour (that goes in Spec or SpecUi).