Version 1 of 2 · · razie · in person · Current version

template-target
Design
template-levels
pro, master
template-note
the design of a pro or master project, made when the project is created (P-530)
description
The design of {{project}}: the mechanisms that realise its specification
tags
#ai #design
status
draft

{{project}}: design

This is the design for {{project}}: the mechanisms that realise the specification, independent of any one code base. Its companions: Spec (the specification), UiSpec (the UI specification), Design (the design) and Implementation (the implementation).

Goals

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 or language features (those go in Implementation), or if it restates behaviour (that goes in Spec or UiSpec).

Domain

Components

Decisions