Skip to content

0.0.4 ​

Every standard has a Why now, kept to its essence: 35 got the one they lacked. Nothing in it is stable yet.

  • 196 standards in 21 modules: 117 changed and six came in
  • A sweep over every Why, each a goal or a principle that is written actively: thirteen of the 21 modules are done
  • Harmony speaks of fine-tuning a balance, where it said to decide for the case at hand
  • A standard on filing a change with coentrify, for a project that is a contributor
  • Always Make No Mistakes as a self-healing feedback loop, in the readme and on every page that names it
  • A gate is the whole test of a phase: its leading question and everything it takes to answer it
  • A glossary of the terms coentrify uses most, and a standard for the glossary of a project
  • Two generic standards: a name describes its unit, and things of one kind are consistent
  • A standard on the system behind a mock: a spec test of its own, or a spec and recorded manual tests where no test can run
  • The maturity levels of a workspace stand in a standard of their own
  • A summary of a linked page stays at the focus level of the page it stands on
  • The template asks for the goal or the principle behind a rule as its Why, in a line or two
  • The Why of a part page stands on its parent, and the check leaves the part out
  • Five docs standards speak of a reader, where a PM, QA or a new joiner stood
  • The English variant is a choice, and the recommendations say so
  • The commit check passes a standard that is back at its released text
  • The changelog has a page per version, and an overview that lists them

AI ​

Angular ​

Architecture ​

Behavior ​

Code ​

Commits ​

Docs ​

E2E ​

Electron ​

Gamedev ​

Records ​

Reporting ​

Scripts ​

Simple Workflow ​

Tests ​

Tickets Workflow ​

Tooling ​

UI ​