repo-architecture

File wiki pages by primary subject using a structured decision tree that evaluates content across people, companies, concepts, and other directories. This enforces a consistent placement protocol to reduce misclassification and maintain repository organization.

Handling ambiguous knowledge base pages requires following structured decision phases to resolve unclear cases before creation. The protocol guides you through checking existing pages and applying notability gates to determine the correct target path for cross-linking.

Cross-linking in a wiki directory structure works by connecting a newly filed page to related directories after its primary subject placement is finalized. This ensures consistent navigation and reduces broken organization across the knowledge base repository.

Apply notability rules during brain-writing and wiki authoring when deciding the correct target path for a new page. This quality gate prevents low-quality placements by verifying the content meets standards before finalizing its directory location.

Yes, a subject-based filing contract applies to meetings, media, originals, and source imports. It standardizes how new knowledge-base pages are filed by evaluating the primary subject rather than the format to determine the correct directory target.

Wiki organization breaks down because filing by format or source ignores the primary subject, leading to misfiled pages and broken directory structures. Enforcing a subject-based decision protocol ensures consistent placement across the knowledge base.