- description
- The components of d2conf: its functional areas, what each is for and what it uses
- tags
- #ai #spec
- status
- draft
d2conf: components¶
The functional areas d2conf is made of, kept in one place: what each is for and which others it uses. A component is a functional area, not a file, class or package. No technology here; how a code base provides them is its own business. The /components page reads this list as written.
Goals¶
- Role: the one list of d2conf's areas. Spec features, Design's sections and the code's folders each belong to one of them.
- A line belongs here if it names an area, what it's for, or what it uses.
- Design follows it: when Design grows past what an agent reads at once, it is split into one part per component,
Design<Component>(DesignAccounts), with Design kept as the index.
1. The components¶
Keep one bullet per component, - **Name**: what it is. Uses A, B., so the page can read it:
- Name: what it is for. Uses nothing.