# Wiki Layer — Standards & Templates ## Article Frontmatter (all types) ```yaml --- type: client | project | system | pattern name: display_name: last_compiled: YYYY-MM-DD compiled_by: sources: - session-logs/YYYY-MM-DD-session.md - clients//session-logs/YYYY-MM-DD-session.md backlinks: - projects/ - systems/ --- ``` `last_compiled` is used by `/wiki-compile` to find session logs newer than this date. Never edit manually. --- ## Article Template: Client File: `wiki/clients/.md` ```markdown --- [frontmatter] --- # ## Profile - **Contract type:** Managed / Break-fix / Project / Prepaid block - **Key contacts:** Name (title, email/phone) - **Billing rate:** $X/hr | notes on exceptions - **Hours remaining (if prepaid):** N hrs as of YYYY-MM-DD - **Ticket system:** Syncro ticket #XXXXX (most recent active) ## Infrastructure ### Servers & Services | Host | IP | Role | OS | Notes | |---|---|---|---|---| ### Email & Identity - **M365 tenant:** tenant.onmicrosoft.com - **MX / mail flow:** ... - **MFA status:** ... ### Network - **ISP / WAN:** ... - **Firewall:** ... - **VPN:** ... ## Access - SSH: `ssh user@IP` (key in vault: `clients//...`) - RDP: IP:port - Admin URL: ... - Vault path: `clients//` ## Patterns & Known Issues ## Active Work ## History Highlights ## Backlinks ``` --- ## Article Template: Project File: `wiki/projects/.md` ```markdown --- [frontmatter] --- # ## Summary ## Architecture ### Components | Component | Location | Tech | State | |---|---|---|---| ### Key Files & Repos - Repo: gitea link - Config: path - Logs: path ## Development ### Current Focus ### Patterns & Anti-Patterns ### Build & Deploy ## Active State ## History Highlights ## Backlinks ``` --- ## Article Template: System File: `wiki/systems/.md` ```markdown --- [frontmatter] --- # ## Identity - **Hostname:** ... - **IP:** ... - **Role:** ... - **Location:** Physical / VM on - **OS:** ... ## Specs ## Services | Service | Port | Notes | |---|---|---| ## Access - SSH: `ssh user@IP` - RDP: ... - Console: ... - Vault: `infrastructure//` ## Known Issues & Quirks ## Backlinks ``` --- ## Article Template: Pattern File: `wiki/patterns/.md` ```markdown --- [frontmatter] --- # ## Rule ## Why ## How to Apply ## Examples ## Backlinks ``` --- ## Index File: `wiki/index.md` LLM-maintained. Do not edit manually except to bootstrap. ```markdown # Wiki Index Last updated: YYYY-MM-DD ## Clients | Article | Summary | Last Compiled | |---|---|---| | [Cascades](clients/cascades.md) | Prepaid block, $175/hr, ~37.5 hrs remaining | 2026-05-24 | ## Projects | Article | Summary | Last Compiled | |---|---|---| | [GuruRMM](projects/gururmm.md) | RMM platform, Rust/Axum, active development | 2026-05-24 | ## Systems | Article | Summary | Last Compiled | |---|---|---| | [Neptune](systems/neptune.md) | Primary server, 172.16.3.30, MariaDB + API | 2026-05-24 | ## Patterns | Article | Summary | Last Compiled | |---|---|---| ## Cross-Reference ``` --- ## Naming Conventions - Slugs: lowercase, hyphens, no spaces (`az-computer-guru`, `guru-rmm`, `cascades`) - System slugs match hostname exactly (`neptune`, `jupiter`, `pluto`) - Pattern slugs describe the rule (`no-mock-db-tests`, `labor-not-taxable`) ## Linking Convention Use `[[slug]]` for cross-references within wiki. Full relative path in frontmatter `backlinks` field. ## What the LLM Should NOT Put in Wiki Articles - Credentials or passwords (vault paths only) - Full session log transcripts (summaries and highlights only) - Speculative or uncertain facts (mark with `[unverified]` if uncertain) - Real-time state (IPs are OK, but current ticket status belongs in coord API)