Private knowledge archive structure

The knowledge base was intentionally not kept as a public route. That was a deliberate architectural decision rather than an omission.

Why it stays private

Knowledge-base material is often half-formed by design: drafts, outlines, internal indexes, references, and still-evolving decisions. Publishing that raw layer usually lowers clarity rather than increasing value.

Why it still deserves a proper structure

Private does not mean unstructured.

If the archive is going to keep growing, it still needs:

• one folder per entry
• room for images, files, and related artifacts
• a path to later become public writing or project material

Current model

The archive now lives under content/knowledge/, following the same folder-first convention as public content, but it is deliberately excluded from the public content registry.

That keeps something important true: public publishing and internal storage share one organizational model without sharing one public contract.