Systems

High-level system and capability documentation.

What Goes Here

System documentation defines: - System purpose and scope - System boundaries and interfaces - Key components and services - Integration points - Ownership and contacts

System Definition Template

Each system should have a document with frontmatter like:

---
id: "sys-example"
type: System
domain: Operations
owner: "[[role-system-owner]]"
status: active
---

Systems in this Section

• Knowledge Base System - Git-Wiki architecture and technical stack
• Cloudflare Deployment - Deploying to Cloudflare Pages with Zero Trust Access

Creating System Docs

When documenting a system: 1. Use kebab-case filenames matching the system name 2. Include a clear system definition with scope 3. Document key capabilities 4. Link to related operational docs 5. Identify dependencies on other systems