Register

Type: definition · Status: current · Tags: document-system

One of three content modes that classifies what a knowledge artifact says — its orientation toward knowledge. Each register has a distinct quality goal and writing conventions:

Register Orientation Quality goal Title style
Theoretical Claims about what is true Reach Claim
Descriptive Accounts for what exists Fidelity + economy Topical
Prescriptive Directs what to do Executability + precision Imperative

In this KB, registers map to collections: kb/notes/ (theoretical), kb/reference/ (descriptive), kb/instructions/ (prescriptive). This is a design choice — registers could also be encoded in types, metadata, or convention. Directories work because they make conventions enforceable by path and visible to tooling.

The three registers are exhaustive because they correspond to the three fundamental orientations toward knowledge: understanding why, representing what exists, and directing action. Every question a consumer asks reduces to "Why is X a good idea?", "How does X work here?", or "How do I do X?"

Registers are orthogonal to operational roles (what an artifact does in the system — evidence, executable instruction, generated report, routing surface). A note type in kb/notes/ is theoretical; the same type in kb/reference/ is descriptive. Register × type gives the full picture.

Two properties make the distinction real: the formulation constraint (theories must be statable in general terms, without referencing a particular system) and maintenance asymmetry (changes flow downstream from theory through prescriptions into descriptions).


Relevant Notes: