Skip to content

#250 child: Replace stale Service Map design documentation as part of Atlas cutover #265

Description

@Joncallim

Parent: #250. Documentation-control review finding.

docs/design/DESIGN.md and DESIGN_LANGUAGE.md still describe the current force/service map, including older 'state dominates', edge-health and impact-radius language. The Atlas intentionally changes some of those presentation rules while preserving truthfulness/accessibility.

Do not edit the as-built design docs ahead of implementation and make them aspirational. During #256 cutover, update them atomically to the accepted Atlas: identity/hierarchy-first healthy view; attention escalation; evidence-backed relation grammar; cross-screen continuity; deterministic layout; lightweight graphics; and current screenshots. Clearly retain product-wide Hearth/state rules outside the Atlas where they still apply.

Documentation tests/links/screenshots must refer to the shipped default, not /map-v2 experiments.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions