g-105 & g-110: context maps & architecture = the strategic blueprint. these sheets define the problem space and the structural solution.
Logical Breakdown (From First-Principles)
- Axes as Organizers: Using axes to sort info spatially is pragmatic and aligns with DDD's focus on managing complexity. In OOP/DDD, we often use grids or diagrams to delimit bounded contexts (e.g., internal vs. external as horizontal axis, human vs. AI labor as vertical). This avoids chaos by enforcing clear boundaries—think of it as coordinate geometry for domains, preventing overlap sprawl.
- Gravity as Layering: Referring to "gravity" as stacked trace layers in one isometric view is a solid metaphor for shared contexts. It mirrors DDD's layered architecture (domain layer at core, with UI/infra around it) and OOP's composition (objects layered via inheritance/composition). Static form (entities like sovereign structure) and dynamic process (event loops like 4-quadrant flow) coexist without separate diagrams, reducing redundancy.
- Heart as Overlap Density: The heart—where A/F/O-series (bounded contexts) intersect—creates intentional ambiguity. In DDD, this is like a core domain with aggregates from multiple subdomains; the density sparks insight (e.g., refactoring invariants). Ambiguity isn't a flaw; it's fuel for distillation (separating essence from noise).
- Fit in G-Series/ATLAS: As governance (strategic oversight), this unifies the blueprint set. It holarchically nests parts (domains) into a whole (sovereign entity), per your docs.
Critique: Logically tight—no contradictions with DDD patterns like context mapping or supple design. But if overused, ambiguity could blur ubiquitous language (shared terms), leading to misaligned code.
Intuitive Feel
It feels right—like viewing a 3D model where you see the building's skeleton (static) and plumbing flow (dynamic) at once. The overlap "heart" intuitively captures emergence: dense info breeds new ideas, like how neural networks find patterns in data layers. For neurodivergent users (per your docs), this spatial layering cuts cognitive overhead by collapsing views into one.