okhp3-mermaid-architecture

原文涵盖的主题

• okhp3-mermaid-architecture
• C4 Layering
• Architecture-beta Diagrams
• Solution Patterns
• Execution contract
• Block & Packet Diagrams
• Cross-diagram zoom coherence
• Scope

OverKill Hill P³ · overkillhill.com · github.com/OKHP3 System/solution architecture vocabulary, loaded after okhp3-mermaid-core. Context → Container → Component → Code. Each layer is typically a separate diagram (per core's splitting guidance), cross-referenced in DIAGRAMS.md. The same system at multiple zoom levels is a feature, not duplication - see references/c4-patterns.md for layer-by-layer guidance and what belongs at each zoom level. The newer Mermaid architecture syntax (architecture-beta) for cloud/infrastructure: groups, services, edges with directional sides (L/R/T/B), junctions for layout control. See references/architecture-beta.md for syntax and the known layout limitations (siblings sharing logical position, fcose layout tuning via idealEdgeLengthMultiplier). Declare the audience and zoom level before selecting Context, Container, Component, Code, block, or packet notation. Separate confirmed systems from proposed systems and label assumptions. Keep names stable across views, validate every cross-view relationship, and do not invent services, boundaries, protocols, or deployment details. Integration flows, service topology, data flow diagrams. See references/solution

这里只展示节选，请以完整原文和当前要求为准。