repo-architecture

To organize brain pages by primary subject, apply a decision tree that routes content into canonical paths like people, companies, or concepts. This enforces consistent information architecture and cross-linking across the knowledge base.

The best way to file meeting notes and media content is using a standardized taxonomy that routes pages to meetings/{slug}.md or media/{type}/{slug}.md. This ensures consistent filing, cross-linking, and standardized output for downstream tooling.

A decision tree enforces information architecture by walking through page content to identify the primary subject and assign it a canonical path. This content governance mechanism prevents misfiling and ensures notability checks are applied consistently.

Yes, you can cross-link related entries when filing new concepts and companies. The routing process enforces cross-linking between canonical paths like concepts/{slug}.md and companies/{slug}.md to maintain a connected and navigable knowledge base architecture.

You need notability checks for filing brain pages whenever new content is routed into canonical paths like people, companies, or sources. These checks are enforced during the decision tree routing to maintain quality and consistency in your taxonomy.