Tutorials · Lesson 1 of 9

Doctrine

Doctrine is how your code is built: the standing rules every agent follows on every item. You declare a rule once, and it holds across every session, every agent and every model until you change it.

By doctrine, we mean:

Your house style, written down: naming, comments, commit format, tests.
Rules that outlive the chat: a new session reads them first.
Enforced where it can be: hooks check it, review holds the rest.
A standard to start from: add to Pullboard’s, override or decline.

Doctrine and spec, on one item

Doctrine sets how it's built. The spec sets what it must do.

Item #2Checkout page pays by card

Doctrinehow it's built: We keep only the data we need.
Specwhat it must do: A shopper can pay by card in one step.

Every item is held to both: this one takes a card in one step, and never stores the number.

Layered

Pullboard's standard, then your repo's changes, enforced at every commit.

StandardPullboard's doctrineEvery repo starts with it: tests must be able to fail, questions go up the chain.

Your repoPRACTICE.mdAdd to it, override it, or decline any part. Only you approve a row.

Every commitGit hooks enforce itLanes, commit format and the gate, checked before anything lands.

Try it

In any git repo.

~/your-repo

$ pullboard init         # writes PRACTICE.md with the standard doctrine
$ pullboard spec check   # lints SPEC.md and PRACTICE.md
$ pullboard view         # the Doctrine tab shows every rule and its source