repo-architecture

To determine the correct directory path for filing markdown pages, apply a primary-subject decision protocol that routes files into directories like people, companies, or concepts. This prevents misfiling by format, ensuring consistent repository architecture.

The best way to organize a knowledge management repository without misfiling by format is using a decision-tree protocol. It categorizes content by primary subject rather than source, routing pages into folders like media or sources to maintain clean markdown organization.

Your repository architecture strategy fails when filing content based on source because it leads to misfiling. A primary-subject decision protocol avoids routing by attributes like "came from email," using a decision tree to map content to concept or company directories.

Yes, you can use a decision tree to prevent duplicate brain pages when adding raw data imports. The repository architecture protocol checks for existing pages before finalizing, outputting an advisory filename to ensure consistent knowledge organization.

You need a notability gate check for new markdown files in a content filing system before finalizing a page. This quality check is applied after determining the correct directory path, ensuring only notable content is committed to the repository architecture.

Yes, the repo-architecture skill supports cross-linking between directories like people and companies. It encourages linking from related directories after selecting the correct path and passing the notability gate, enhancing overall knowledge management and content discovery.