Glossary
The terms coentrify uses most, each described in plain words.
- The People - who does what
- The System - what a project adopts
- The Work - how a piece of work is specified, built and accepted
- Keeping It Right - how differences are found and fixed
The People
Director
The human in charge of a project. The director decides what is built and in what order, and accepts or rejects the result (How It Works).
Agent
An AI model that does the work of a project: it writes the documentation, the tests and the code.
The System
Spec-Driven Development
A way of working in which what is wanted is written down and specified before it is built, and what is built is checked against what was written (Spec-Driven Development).
Standard
A written rule, convention or template that a project adopts. Every standard is one file (Standards).
Module
A folder of standards on one subject, such as Docs or Tests.
Core Rules
The rules every task follows, in every session. An agent loads them at the start of each session (Overview).
Check
An automated test of a rule: a script, a lint rule or a hook that fails when the rule is broken.
Harness
Everything that guides and limits the work of an agent: the standards, the checks and the tools (Always Make No Mistakes).
Coentrify
The harness described on these pages. As a verb: to set a project up with it (Origin).
Pillar
One of the four principles behind the system: Specs & Checks, Layering, Harmony and Shepherding (Philosophy).
Law
A short rule about the product that holds unless there is a very good reason to break it. The design rules of a game are laws (Game Design Laws).
Why
The section of a standard that says why its rule is needed.
Part Page
A standard that holds one part of a larger standard. Its title starts with the title of the larger standard, followed by a colon.
The Work
Use Case
The smallest complete flow in a product: one thing a user does, from a start state to a result. A feature consists of several use cases.
Spec
Short for specification: what is wanted, written down, at any level. A feature doc's statements, a feature's use cases and a ticket's criteria are each a spec. The feature spec lists a feature's use cases, each written out as steps, and every use case has an id of its own, renamed everywhere at once when it changes (Feature Spec Template).
Layer
One level of description of a product. From general to specific, the layers are the docs, the specs, the tests and the code.
Proof
Evidence that the director can verify without reading code: a screenshot, a video, a test run or steps to try (The Done Part).
Go
The director's explicit approval to build ready work: by a ticket's or a story's id, or in one word for all that is ready (Work Workflow). Work in another project, or a session that outlives this one, needs a go of its own (A Go Before Work Elsewhere).
Pass
One stretch of an agent's work on a request, from taking it up to reporting it. Done in the same pass means done before the report, with no new go needed.
Maybe
An idea the director phrases with uncertainty. An agent investigates it at once and reports the outcome (A Maybe Is A Trigger To Investigate).
Veto
The director's rejection of a choice that an agent made on its own. An agent lists such choices in its report (Flag Every Addition Of Your Own). A ticket's Veto section lists those choices.
Phase
The stage of development a project is in, such as prototype or production. The phase determines which work has priority (Project Lifecycle).
Phase Gate
The test that ends a phase: a leading question together with everything it takes to answer it (Project Lifecycle).
Keeping It Right
Gap
A difference between two layers: something that one layer states and the other lacks. A use case without a test is a gap.
Gap Analysis
To compare two layers and find the differences and discrepancies between them, the delta (Regular Layered Gap Analysis).
Drift
A difference that grows over time, because one layer or rule changed and the related one was not updated.
The Loop
The self-healing feedback cycle of the system. A mistake or a gap that is caught gets fixed twice: once in the work, and once in the harness, as a standard or a check. Round after round the system stabilizes, and adapts to its director, its agents and its project (How It Works).
Sweep
To apply one rule to every existing instance in a project: find all instances, list them, then fix them (Sweeps Enumerate Into Tech-Debt First).
Focus Level
The level of detail a page is written at, such as a workspace, an application or a feature. A page summarizes the levels next to it and leaves their details to their own pages. Also called altitude or level of awareness (Docs Are Hierarchical, Explicit And Short).