Rodin 91b62be330 docs: add Temporal architectural analysis
8,958 commits, 290 contributors, heavyweight Go infrastructure.

Key findings:
- HSM framework: type-safe state transitions, source validation
- CHASM: mutable vs immutable contexts enforced at type level
- goro.Handle: predates CockroachDB's Handle by 3.5 years (same solution)
- softassert: production assertions that log, don't crash
- 566 dynamic config settings with namespace-scoped resolution
- uber/fx for DI (justified by genuine service graph complexity)
- Domain error types → gRPC mapping (not generic wrapping)

PR discussions show:
- HSM (#5494): 'not final, step in the right direction' — explicit iteration
- CHASM (#6987): separate contexts to make mutation impossible in read paths
- goro.Handle (#1892): born from double-close panic, reviewer rule: 'if expert asks, code needs comment'
2026-04-30 11:38:51 -07:00

Patterns vs Official Guidelines

Divergence analyses comparing our extracted-from-source patterns against official coding guidelines.

Reports

Ecosystem Our Patterns Official Guidelines Report
Go rodin/go-patterns Effective Go, Code Review Comments, Google Style go/
Elixir rodin/elixir-patterns CONTRIBUTING.md, Style Guide, HexDocs elixir/

Philosophy

Official guides tell you what to do. Source patterns show what mature code actually does. When they diverge, neither is wrong — they serve different audiences and optimize for different things.

This repo documents where they agree, where they differ, and why.

S
Description
Divergence analysis: extracted source patterns vs official coding guidelines
Readme 93 KiB
Languages
Markdown 100%