ExzenTCG Internal Documentation Repository Direction¶

Intent¶

ExzenHQ/wiki is the canonical internal documentation repository for ExzenTCG.

Use this local Obsidian vault to edit, sync, commit, and push docs to GitHub.

Do not preserve every old plan, phase note, screenshot, or implementation log. Maintain accurate docs for how the business and technical systems operate now.

Working principle¶

Prefer current-state docs over historical planning docs.

Keep:

• Current architecture
• Current source-of-truth maps
• Current service ownership
• Current deployment topology
• Current migration state
• Current tcg-platform capabilities and gaps
• Current operational risks

Archive or remove:

• Old phase plans
• Superseded implementation plans
• Stale screenshots
• Completed/abandoned design notes
• tcg-platform planning-phase documents that no longer describe the current system
• Homelab setup logs that are no longer useful for understanding current infrastructure

Clean structure¶

ExzenTCG/
  Home.md
  Business/
    Operating Model.md
    Finance and Accounting.md
    Inventory and Stock.md
    Fulfillment.md
  Systems/
    Google Sheets and Apps Script.md
    exzen-core.md
    Otto.md
    n8n.md
    Cloudflare and Edge.md
    Proxmox and Tailscale.md
    tcg-platform.md
  Migration/
    tcg-platform Current Gap Analysis.md
    Decommissioning Legacy Systems.md

GitHub repository¶

Canonical repo:

https://github.com/ExzenHQ/wiki

Former repo names/locations may redirect for now, but new links and remotes should use ExzenHQ/wiki.

tcg-platform documentation rule¶

For tcg-platform, keep docs that cover:

• Current implementation.
• Current deployment state.
• Current data model and architecture.
• Production migration blockers.
• Dual-write risks during cutover.

Remove or archive phase docs that only describe earlier implementation plans.