Skip to content

#250 child: Define Atlas edge-routing and congestion budget #268

Description

@Joncallim

Parent: #250. Visual/layout orthogonal pass; fold into #257/#253 implementation.

A deterministic layout can still be unreadable if connectors cross labels/groups or if one dense dependency lens paints hundreds of lines. Freeze a deterministic congestion policy.

Required: connectors may not traverse interactive subject interiors except at endpoints; group-boundary crossing is explicit; relation routing order is canonical; parallel/bundled routing is deterministic; selected/local context gets priority; edge labels are avoided by default unless necessary; dense relation sets aggregate/focus instead of unlimited drawing.

Define measurable budgets for visible connectors, crossings per viewport/region, and maximum routed segments at 25/100/250-object fixtures. If the budget is exceeded, the deterministic policy must reduce/aggregate secondary relations rather than let the renderer choose an aesthetic solution.

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