Eye / camera validation coverage¶

Generated from validation-slots.json (schema version 1). Do not hand-edit this file: edit the registry and run uv run python scripts/gen-eye-validation-dashboard.py.

How to read this page¶

• It reports the committed registry, not GitHub. Every value below is a function of the registry file. Live issue readiness, labels and claims are read from the issues under #102, never from here — see the note in README.md about why this directory carries no status snapshot.
• PLANNED and READY are lifecycle states, not results. VALIDATION_OPERATIONS.md defines them: PLANNED means the runtime or harness is not available yet, READY means a contributor could run the cell today.
• A FAIL or BLOCKED report is evidence, not missing evidence. Such a cell counts as reported, is a valid completed contribution, and never appears in awaiting a first report.
• Independent hosts and repeat sessions are different units. Three separated sessions by one person on one computer are three repeat sessions and one host; they are never added together or shown as three people.
• Beginner-safety is intrinsic difficulty, not a live label. It records whether a cell would carry good first issue once READY. Readiness labels are deliberately withheld while a cell is PLANNED (GOVERNANCE.md).
• A combination with no registered cell is not an overdue test. The programme opens a cell when the capability is reachable on that platform, so a gap below means no cell has been committed yet.

Summary¶

Registered cells by test pack and environment¶

Rows are the test packs and columns the environments in the registry's own vocabulary, so a pack or environment added to the registry appears here without editing this table. — means no cell is registered for that combination.

Every registered cell¶

One row per registered cell, in pack then environment then slot order. The issue link is derived from the registry, so it cannot disagree with the cell it represents.

Unmet blockers¶

Conditions beyond a prerequisite issue¶

Combinations with no registered cell¶

These are pack/environment combinations the registry vocabulary allows and for which no cell has been committed. They are gaps in the plan, not overdue work: VALIDATION_MATRIX.md is explicit that a row must not be asked of a contributor before that capability is reachable on their platform.