Templetry organization architecture

Templetry organization architecture An architecture diagram generated by Archify. desktop · Wails: Go backend + React/TS · Architecture component desktop Wails: Go backend + React/TS Developers & AI agents · CLI · Desktop · MCP · Architecture component Developers & AI agents CLI · Desktop · MCP homebrew-tap · brew install (macOS/Linux) · Architecture component homebrew-tap brew install (macOS/Linux) engine · Go library + CLI + MCP server · Architecture component · Apache-2.0 engine Go library + CLI + MCP server Apache-2.0 catalog · registry.json · schema v2 · Architecture component catalog registry.json · schema v2 pieces · common, decoupled units · Architecture component pieces common, decoupled units scoop-bucket · scoop install (Windows) · Architecture component scoop-bucket scoop install (Windows) 11 parent repos · android · web · python · go … · Architecture component 11 parent repos android · web · python · go … .github · org profile + setup-templetry action · Architecture component .github org profile + setup-templetry action Git forges · GitHub · GitLab · Gitea · self-hosted · Architecture component Git forges GitHub · GitLab · Gitea · self-hosted renovate-config · shared preset · Renovate bot · Architecture component renovate-config shared preset · Renovate bot alternate entry CLI render/verify/update · MCP tools imports engine library (no IPC) push generated/updated repos reads registry.json release + SHA256SUMS release + SHA256SUMS piece pointers (repo+ref) form pointers (repo+ref) installs pinned CLI (setup-templetry) proposes engine-version bump Legend Frontend Backend Database Cloud Security External

Usage

  • • Developers drive the `templetry` CLI directly or through the desktop app; AI agents drive it over `templetry-mcp`
  • • The desktop app imports the engine as a Go library — no IPC, no sidecar
  • • Every path ends the same way: a repo created or updated on GitHub, GitLab, Gitea/Forgejo, or any self-hosted forge (BYOR)

Content pipeline

  • • `catalog`'s registry.json is the single source of truth for where every form and piece actually lives
  • • 11 parent repos hold the forms themselves; `pieces` holds units adopted after creation, independent of any one form's lifecycle

Governance & distribution

  • • Renovate proposes an engine-version bump; once merged into `.github`'s setup-templetry action, every parent's CI re-verifies all its forms against it
  • • Homebrew tap and Scoop bucket regenerate their install manifests from the engine's own GitHub Release artifacts — packaging trails the engine automatically
  • • `renovate-config`'s preset is extended by every repository in the org, not drawn as an edge to every node to keep the diagram readable

Documentation

  • • The `wiki` repo (ADRs, specs, studies) isn't a runtime dependency — every other repo's README links back into it, and this diagram is generated from its content