Skip to main content

Folder Ownership Map

Who owns a method — the folder that teaches it or the skill that runs it?

Both, through one contract. A playbook folder owns the know-how for a capability; a skill packages one repeatable method that serves it. The chain is the pattern: business function → capability → unit of work → skill → tool → evidence. The machine SSOT for the skill side is the skill namespace manifest; this page is its playbook-side mirror. When the two disagree, fix the manifest through its generator — never fork the truth here.

The Map​

  • /playbook/ai — directed cognition: models, agents, instruments, work maps. Skill domain: agt.
  • /playbook/business — business functions, flows, and operating patterns. Skill domain: bus.
  • /playbook/software — engineering practice and software products. Skill domain: eng.
  • /playbook/systems — feedback loops, thinking methods, process systems. Skill domains: ops, wf, 5p.
  • /playbook/productivity — workspace tooling and personal throughput. Skill domain: gws.
  • /playbook/scoreboard — metrics, proof, validation, ledger logic. Skill domain: val.
  • /playbook/crypto — chains, tokens, on-chain commerce. Skill domain: sui.
  • /playbook (root and remaining hubs) — documentation and knowledge-shaping methods themselves. Skill domain: doc.

How To Use It​

  • Naming a new skill — find the owning folder first, then apply the slug rules in Naming Standards. The folder names the capability; the skill names the method.
  • Placing new know-how — when a method repeats inside a territory, it earns a skill, and the skill's manifest row points back at the owning folder.
  • Reading a gap — folders without a skill domain yet (community, games, navigation, agency, mental-models) own capability know-how whose methods are not packaged. The gap is a signal, not an error.

Checks​

  • Verify the manifest and this page name the same folders and domains; a mismatch is a manifest fix, made through its generator.
  • Verify every new skill row carries an owning folder before the skill ships.

Failure Modes​

  • Forked truth — editing this page to "correct" an ownership row instead of fixing the manifest. The mirror must never lead the source.
  • Slug packing — forcing lifecycle, provider, or audience into a skill name when the manifest row already carries those dimensions.
  • Orphan skills — a skill with no owning folder serves no named capability and resists discovery and review.

Context​

Questions​

If a competitor copied your folder tree but not your skills, what would they actually have?

  • Which folder owns the method you repeated most this month — and is it packaged yet?
  • When a skill and a folder disagree about ownership, where is the tie broken, and who fixes the source?