Core holds what every company shares, and a pack what only some kinds of company need. Your own words go into kinds and sections.
Robert Blust · Software Engineer & Architect
A vocabulary too small leaves facts out. One too large makes every company carry types it leaves empty.
What fits every business. Core defines a type; it does not oblige you to fill it.
Vocabulary only some kinds of company need at all. For any other company its types are absent, not optional.
A pack names core; core never names a pack. Taking one asks nothing new of a page you already have.
A kind is a page in your own words that sorts the pages of a type: product kind, decision kind, group kind, system kind. It adds no type.
A section is open and a field is closed: a page may carry prose its schema does not declare.
init --pack when you start, upgrade --pack later: vendored beside core, listed in the manifest, checked and moved with it.
Take a pack when your company is that kind of company, and only then.
Ask with a feature request. New vocabulary starts from a pattern a real company shows, not from a wish list.
One talk follows for each pack, for people who already work in the method it draws from.
Core for every company and a pack for your kind. Your own words go into kinds and sections before any new type.