…
template-target: Spec
template-levels: pro, master
-template-note: the specification of a pro or master project, made when the project is created (hero and creator get Template:makerSpec instead); replaces Template:ProjectSpecification (P-530)
+template-note: the specification of a pro or master project, made when the project is created
description: The specification of {{project}}: what it does, as its users and AIs meet it
tags: ai, spec
…
# {{project}}: specification
-This is the specification for {{project}}, driving all other items: what it does, as its users and AIs meet it. It says what's true now; how it got here is in [[Log:PROJECT]] (the people's changes and decisions) and [[AiLog:PROJECT]] (what the AI changed); what's still open is in [[ToDo:PROJECT]]. Its companions: [[Spec]] (the specification), [[UiSpec]] (the UI specification), [[Design]] (the design) and [[Implementation]] (the implementation).
+<<<<<<< yours
+A project is specified in [[Spec]] and [[UiSpec]], designed in [[Design]], implemented and tested via an [[Impl]] and [[Testing]]. You create these and keep them up to date and in sync prefereably through your AI - the d2 skills teach it how to keep all these documents in-sync, index them with feature tags that correlate a feature end-to-end, visible in [system view](/system).
+
+**This is the specification** for {{project}}, a detailed, exact description and set of requirements that explain what it does and how, driving all other steps in this project. The entire creation pipeline is driven from this specification, so be brief but not too terse. Avoid lots of text, use indentation and best keep feature descriptions per section and behaviours per line.
+
+
+It says what's true now; how it got here is in [[Log:PROJECT]] (the people's changes and decisions) and [[AiLog:PROJECT]] (what the AI changed); what's still open is in [[ToDo:PROJECT]]. Its companions: [[Spec]] (the specification), [[UiSpec]] (the UI specification), [[Design]] (the design) and [[Implementation]] (the implementation).
+=======
+A project is specified in [[Spec]] and [[SpecUi]], designed in [[Design]] and [[DesignRoutes]], tested in [[SpecTest]], and implemented in each code base's own topics (e.g. `Proto1Impl`). You create these and keep them up to date and in sync preferably through your AI - the d2 skills teach it how to keep all these documents in-sync, index them with feature tags that correlate a feature end-to-end, visible in [system view](/system).
+
+
+**This is the specification** for {{project}}, a detailed, exact description and set of requirements that explain what it does and how, driving all other steps in this project. The entire creation pipeline is driven from this specification, so be brief but not too terse. Avoid lots of text, use indentation and best keep feature descriptions per section and behaviours per line.
+
+
+It says what's true now; how it got here is in [[Log:PROJECT]]; what's still open is in [[ToDo:PROJECT]]. 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 {{project}} keeps its own topics, named after it (e.g. `Proto1Impl`, `Proto1Code`, `Proto1Routes`, `Proto1Test`).
+>>>>>>> theirs
+
## Goals
…
- **Role:** what {{project}} does, as a user or an AI meets it, the same however it is built.
- **A line belongs here if** it would be wrong only when a user or an AI would notice.
-- **It fails if** two builds that both follow it behave noticeably differently, or if it holds a mechanism, a file or a host (those go in [[Design]] and [[Implementation]]).
+- **It fails if** two builds that both follow it behave noticeably differently, or if it holds a mechanism, a file or a host (those go in [[Design]] and the code base's topics).
## Purpose
…