Chapter · Company Admin Edition

Template families

Company settings holds a family of template surfaces - structure templates (Part 1), log templates (Part 4), note types, flag types, spark categories, and asset categories & types (Part 2). Six lists, one philosophy, stated once here so the individual pages don't repeat it:

Templates are scaffolding, not answers. Every family exists to make the right habit the lazy habit - the create dialog that already offers the right categories, the project that starts with the right sketch. The moment a template starts deciding things the work hasn't decided yet, it has crossed from scaffolding into cage. The work drives the shape; templates just make the shape cheap to adopt.

Three operating rules that apply across the family:

Rule: short lists get chosen; long lists get defaulted. Every vocabulary (note types, flag types, spark categories, asset types) should be short enough that the right choice takes no thought. Past roughly seven options, people stop choosing and start defaulting to the first entry - and your structured data becomes noise wearing structure's clothes.

Rule: adopted copies don't follow the template. Projects copy templates at adoption (structure at creation, log configs at setup). Editing a company template improves future adoptions, never running projects - so template investment compounds forward and can't break anything mid-flight. Corollary: fix a running project in the project; fix the pattern in the template; usually you should do both.

Rule: retire by deactivating, never deleting. Deactivation removes an option from new adoptions while everything already built on it keeps working. Deletion is for things that never shipped.

Each family's specific judgment lives with its tool: structure templates in the Organizer chapter, log templates in the Logs chapter, spark and asset vocabulary in Sandboxes and Rallies, note and flag types in Everything Else. This chapter's job is only the shared doctrine - and the reminder that manage templates is a per-member capability (chapter 06), so template stewardship can live with your best organizers rather than with whoever happens to be admin.

Mechanics - each family's settings page: Field Guide → Company settings.