Layer 4 — Method

How a room is tested

The console is a situation-aware evaluation instrument. It is not a ranking, a booking tool, or a substitute for a site visit. Pretty is invited. Operationally right gets the seat.

The five layers

  1. 01

    Decision

    What should I do with this room, against this evening?

  2. 02

    Reason

    Which inputs and rules produced that standing?

  3. 03

    Evidence

    What is actually on the record, and of what class?

  4. 04

    Method

    How the model fails closed, and what it refuses to invent.

  5. 05

    Technical

    Schemas, source versions, snapshot dates, edge cases.

Fail closed

If a capability you marked as required is not established on the record, the room is held back. Absence is never read as a pass. A posted capacity figure is treated as marketing until a usable figure exists. Headcount inside the last eight percent of a usable figure is flagged as tight, not as a hard block.

Evidence classes

  • Documented — a first-party document. Strongest class in this instrument, still not a guarantee of the day.
  • Stated — someone at the venue said it. It survives staff turnover only as memory until it is in writing.
  • Pattern — typology behaviour or outside observation. Useful signal, not authority.
  • Absent — nothing of any class addresses the point. Recorded as absence.
  • Known
  • Watch
  • Blocking
  • Unknown

What the numbers are not

“Answered” is the share of situation-weighted findings the record can currently speak to. “Still to confirm” is confirmation work, rising with unresolved weight and build level. Neither is a quality score. A room with fewer blockers may simply be a room with less evidence in it.

Snapshot

Catalog snapshot 2026-08-27 · 1110 snapshot venues · 9048 findings · 7763 unknowns carried rather than filled.

Read next

Return to the console →