📖 [Docs]: Document architecture and memory boundaries

[Marius Storhaug (MariusStorhaug)]

Documentation now has an explicit, discoverable architecture for humans and agents: topic-first navigation, reader-need artifact tiers, minimal OKF-style metadata, and a separate durable-memory repository.

Changed: Documentation architecture

Contributors can now choose a page home by subject and artifact tier without duplicating a Diataxis taxonomy. The decision makes clear that reviewed knowledge stays in MSXOrg/docs, while durable working knowledge belongs in private MSXOrg/memory.

Changed: Navigation coverage

Every content directory now has an index. Deployment designs and Agentic Development decisions are visible in site navigation and generated indexes.

---

Technical details

• Adds the immutable decision record for the documentation architecture, OKF-style metadata boundary, and memory boundary.
• Extends the Documentation Model and contributor guidance with the chosen placement rule.
• Adds the missing Capabilities/deployment/designs/index.md and wires nested navigation for deployment designs and agentic-development decisions.
• Validation: regenerated and checked indexes; same-repository and cross-repository link checks; clean Zensical build; Update-DocumentationIndex.Tests.ps1 (6 passing tests).
• Implementation plan progress: architecture decision, contributor guidance, navigation gap, and validation are complete.

Changed surface	Standards checked	Framework docs checked	Result
src/docs/**	Markdown, Documentation	Documentation Model, Agentic Development	Aligned
src/zensical.toml	Documentation navigation	Documentation Model	Aligned
CONTRIBUTING.md	Markdown	Contribution Workflow, Documentation Model	Aligned

• Issue convergence sweep: Adopt Diataxis + Open Knowledge Format as the docs architecture (small human+agent pages, self-updating remote brain) #10 is fully addressed by the recorded decision; its previously referenced PowerShell standards issues (Add tools vs. controllers and raw-data output to the PowerShell standard #2–Add PowerShell code-sample conventions to the Markdown standard #8) are already closed.

Relevant issues (or links)

• Resolves Adopt Diataxis + Open Knowledge Format as the docs architecture (small human+agent pages, self-updating remote brain) #10

Related work

• References 📖 [Docs]: Add Open Knowledge Format to the Dictionary #34
• References 📖 [Docs]: Agentic development framework documented #51
• References 📖 [Docs]: Canonical memory repository template added #70