Software Architecture Metapatterns Knowledge Base
software-architecture-metapatterns namespace covers software architecture metapatterns: system topologies, layers, services, pipelines, proxies, orchestrators, plugins, hexagonal architecture, service-oriented architecture, polyglot persistence, pattern aliases, architectural forces, dependencies, performance tradeoffs, and architecture evolution paths.The software-architecture-metapatterns namespace covers software architecture metapatterns: system topologies, layers, services, pipelines, proxies, orchestrators, plugins, hexagonal architecture, service-oriented architecture, polyglot persistence, pattern aliases, architectural forces, dependenc
Structure
raw/— raw Markdown provenance mirror for agents and source inspection.wiki/— synthesized knowledge pages: concepts, entities, summaries, and syntheses.- Schema and maintenance rules: see
CLAUDE.md.
Usage
- Add new sources: update canonical source notes in
pixi-vault, then compile into this namespace. - Ask questions: agents read this wiki and cite raw/source paths.
- Publish: regenerate
pixi-wiki, run tests, then live-verify raw and HTML routes.
Software Architecture Metapatterns¶
Software-architecture pattern-language reference for agents, compiled from Denys Poltorak's Architectural Metapatterns: The Pattern Language of Software Architecture GitHub wiki.
Canonical Source Roots¶
- Source repository:
https://github.com/denyspoltorak/metapatterns - Source wiki:
https://github.com/denyspoltorak/metapatterns/wiki - Source website:
https://metapatterns.io/ - Latest release inspected:
https://github.com/denyspoltorak/metapatterns/releases/tag/v1.2
Provenance and License Guardrail¶
The repository root license is Creative Commons Attribution-NonCommercial-ShareAlike 4.0. The book/source directory and wiki copyright page indicate Creative Commons Attribution 4.0. This namespace keeps the ambiguity visible and follows a conservative public-use stance: preserve attribution, source links, license notes, and no-endorsement boundaries.
Use this corpus for reference, critique, education, architecture review, and non-misleading agent retrieval. Do not present it as unrestricted commercial training data or as Jamie/Pixi-authored source material.
Agent Use Contract¶
- Start with For Agents — Software Architecture Retrieval.
- Retrieve a bounded set of 3–8 relevant metapattern/source pages before recommending an architecture.
- Compare patterns by structure, dependency direction, communication style, performance, team ownership, and likely evolution path.
- Cite metapattern names and source pages in the recommendation so a human can inspect the reasoning.
- Prefer "what forces are present?" over "what architecture is trendy?" Tiny systems do not need distributed cosplay.
Public Output Contract¶
When published to pixi-wiki, this namespace should expose:
/raw/software-architecture-metapatterns/README.md
/raw/software-architecture-metapatterns/wiki/index.md
/wiki/software-architecture-metapatterns/README.md.html
/wiki/software-architecture-metapatterns/wiki/index.md.html
/wiki/software-architecture-metapatterns/llms.txt