Skip to content

#250 child: Define measurable Atlas usefulness and visual-quality acceptance rubric #260

Description

@Joncallim

Parent: #250. Must be frozen before #254.

The flagship map cannot pass merely because it is deterministic and unclipped. Define a repeatable usefulness + visual-quality rubric over fixtures and real-host captures.

Mechanically/observer-test the ability to locate: a named subject; attention subjects; host-published ports; network/storage membership; a recorded dependency; unresolved/ambiguous evidence; and the boundary of what is not known. Measure task completion/click depth and prevent critical facts from requiring hover.

Visual-quality rubric must score hierarchy, alignment, whitespace/rhythm, label legibility, connector crossings/congestion, simultaneous color count, group distinguishability, selected/focus clarity, attention salience, and continuity with adjacent screens. Define failure thresholds rather than relying on 'looks nicer'.

AI screenshot critique may supplement this rubric but cannot be the authority. Final acceptance requires deterministic fixture assertions plus human/maintainer visual approval on the certified screenshots.

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