Templates

A template is a pre-authored mini-graph: collection skeleton, edge vocabulary, day-one question list, starter design.md files. Pick one during Level 2 if the scenario fits; adapt collection names to your vocabulary; react rather than design from scratch.

Tier-1 templates

Full content. These cover the primary audiences (SaaS founder, consulting practice, code repo, personal KB, cross-functional product).

• saas-startup — founder wiki that grows into sales and product surfaces as the team scales
• consulting-agency — boutique practice with clients, engagements, deliverables, frameworks
• code-repo — documenting a codebase; pairs with the code path
• personal-repo — single-user knowledge base, intentionally modest
• product-strategy — strategy → roadmap → marketing claims, cross-functional visibility

Tier-2 templates (skeleton only)

Skeleton + edge vocabulary + day-one questions. Fewer examples, no prose expansion. Useful as starting points; expect to fill in the rest.

• business-strategy — company-level: vision, bets, priorities, org units, metrics
• sales-memory — accounts, contacts, deals, commitments, features, competitors
• regulated-audit — regulations, policies, controls, procedures, evidence, systems, incidents

How to use

The rubric each template follows lives in this collection's design.md companion file. During Level 2 of onboarding, the agent shows the menu; the user picks one, rejects all (custom), or combines two (rare, usually harmful — prefer one).

Extending

Adding a new template: follow the rubric in design.md, match the voice of existing Tier-1 templates, and link from this index. Templates are standalone — don't reference each other except where one is a clear evolution path from another (e.g., saas-startup grows into product-strategy).