Fire Code Matrix Grades 20 Questions Empty; the Summary Says 18

The fire and life-safety question matrix grades its own twenty-six rows, and reading that grade column returns 20 with no obtained input and 6 at the next grade up [TARGET]. Two paragraphs later the same chapter's summary writes 18 empty and 8 upgraded [TARGET]. A later compartment conclusion repeats the 18 while arguing that six compartment constraints can be frozen anyway. The two-row difference is left unidentified in the file. The article does not invent the two. The register's priority logic still runs off which rows are empty.

Only Six of Twenty-Six Questions Carry Any Obtained Input

Six questions carry the next grade up, and they are the only rows a reviewer can act on today [TARGET]:

• the electrical code edition and local amendments, where a clearance envelope is already built and held conditional;
• whether automatic suppression may be traded for compartment area or fire resistance;
• whether the single-storey premise holds;
• the fire access road, graded upward only because the site model refused to assign values to it;
• whether on-site water storage is required;
• the fire pump drive.

The remaining twenty carry no obtained input, and none of the twenty-six reaches the grade at which a written third-party answer exists. Zero items sit at the next grade or above [TARGET]. The delivered code and occupancy matrix agrees from the machine side: eight criteria rows, every one marked not evaluable pending its hold, each hold naming its own owner among the authority, the record engineer and an equipment supplier [TARGET]. Nothing in that file is a compliance judgement either, which is the correct output when no code edition has been adopted.

Eight Blockers; Later Answers Would Void Downstream Work

The same chapter is exact where it can be. Eight items are listed as true blockers, separated from items that are merely incomplete by a stated test: a blocker is an item whose later answer voids downstream work that was done in the meantime. Of those eight, one is recorded open on a different ground from the rest. Its state is not-asked, because the autonomy hours that drive fuel quantity have never been put to the owner as a question, and the chapter says this is the only one of the eight whose delay is caused entirely inside the project.

A second is flagged for the opposite reason. Neither the fire pump drive question nor the question of whether generators stop on a fire alarm looks like a blocker on its own, since each has an answer available. Taken together they can produce a system in which the fire pump loses its supply at the moment it is needed, and because they would normally be answered by different parties at different times, that combination is invisible to a process that treats them separately. The chapter requires them to be submitted as one joint question and closed at one gate, and it is the only place in the register where two answers are forbidden to be given apart.

The eight blockers and the twenty-six questions also barely overlap. Four of the eight are code or authority questions: the adopted code edition, the separation requirement, the water supply measurement, and the joint ruling above, which occupies two question rows at once. The other four are a battery chemistry decision, the unasked autonomy figure, an undefined building form and a missing safety data sheet, and no authority can supply any of them.

The hydrant flow test is the one input whose clock is third-party scheduling. Starting it in parallel is the only close that does not wait on design.

Ninety-three requests, none of them sendable

A separate register of 93 external requests would carry these questions outward [TARGET]. Ninety sit in a draft-not-sent state; three sit as existing evidence still unverified [TARGET]. None has been sent. Its send gate is a conjunction whose every term currently evaluates false, so the count of sendable batches and of sendable requests is zero. Two of the false terms are internal: all 93 entries still name a placeholder recipient, and no sender has been designated for correspondence with the authority, which blocks all twenty entries of that class under a no-sender code. Its external gate table holds 14 entries, all open, and it records its own contribution to closing them as zero [TARGET]. Eighteen quality-gate rows in the same register are marked not evaluable, because the validator script does not exist [TARGET]. Not evaluable is not a pass.

The 20-versus-18 Gap Is Left Unidentified

The recount reads a grade column, so it inherits whatever judgement assigned those grades, and two of the six upgraded rows were upgraded because another discipline refused to assign values rather than because an answer arrived. Two rows carrying a written reply that the table did not print would restore the chapter's figure and shorten the priority list by two, and nothing in the file points to such a reply. The summary figure is left standing beside the table. It is not corrected here.

Whoever holds the owner interface must put the autonomy question, because the register records it as the only one of the eight whose state the project can change without waiting on anybody.

© 2026 K&K Data Service Inc. All rights reserved. Reproduction or republication is permitted only with clear attribution to K&K Data Service Inc. and a working hyperlink to the canonical URL of this article. Excerpts must preserve the technical context, maturity labels, assumptions, and limitations. No excerpt may imply project approval, field validation, certification, or endorsement that the original article does not state.

Source: K&K Data Service Inc., “Fire Code Matrix Grades 20 Questions Empty; the Summary Says 18,” https://www.kkdatasvc.com/lab/fire-structure-site-and-compliance/fires-26-questions-the-table-grades-20-empty-the-summary-says-18/.