The vault’s container rules are vault-kit’s upkeep skill, and what a note says about the code is Craft Kit’s doc-rules skill. This note holds only what Datler adds to them or does differently, and it wins where they differ. vault.config.json names it as the vault’s rulesNote, and craft.config.json gives it to every craft pass slice as docs.rules.
What publishes
- The public notes, by the
visibilitypolicy invault.config.json(concept, system, pattern and devlog), are published at docs.datler.ca (Public Site). Every other kind stays in the repo. - Datler Vault and Page Specs are the reference maps, and carry
visibility: public. Delivery Plan is the working index, and stays private; open work, deferred work at P4 among it, is on the board, as issues on jeliroco-multimedia/datler. - A public note uses the app’s words for any term the app also shows, as Writing in Datler sets them.
- The glossary is a separate vault,
docs-vault/, outside these rules.
Where things go
- Concept, system, pattern and decision notes live in the folder their
domainnames; tasks intasks/, audits inaudits/and devlogs indevlog/. A task that graduates by retype moves to its domain’s folder. - Problems in the code are issues on
jeliroco-multimedia/datler, filed with Craft Kit’sfile-issueskill. - A lesson about how agents should work goes in the repo’s
CLAUDE.md, or in the note it concerns. - A fact measured on a device says how it was measured and on which device, as Steps does.
Decisions reach the docs as design
A decision note is private: the record of a choice, the options weighed and the ruling. What it settled is stated in the public note for the part it shaped, as how that part works, with the reason in a clause where it is not obvious (“X rather than Y, because …”). A public note carries no decision record and no link to one, and design that only a decision note states moves into the reference note it belongs to.
A decision note of the wrong kind is retyped. One that lists open questions becomes a task. One that describes how something works becomes a concept or system, its record of the choice left behind. One that only records how questions were resolved has its design folded into the notes it shaped, and is proposed for deletion.
A craft pass’s structure changes
A craft pass’s slices propose renames, folds, splits and deletes rather than carrying them out, since each reaches into other slices’ links. After the pass, the main session carries out the proposals with vault-kit rename, moves graduated tasks to their domain folders, and runs pnpm run vault:refresh. A note is deleted by a person, never by a pass.
Related
- Datler Vault — how the vault is organized.