The software reports what it found. The authenticated engineer records the professional response. The reviewing authority records its determination. No step silently erases another.
The desk is the forest
Two or more granted submissions open the existing review desk: every real granted job is one row, the pending Accept / Return / Deny board, and the firm-wide open-waiver list from record.waivers[]. The regulator sees Massena Stephens Media 16.002-3-66.1 / 2155 SH 420 as one row when that design is granted. Opening that row is the tree. If Massena is not granted, the regulator sees an empty desk — not the baked sample, and not a queue of test dirt. Owner/engineer empty-set sample preview is software testing, not Joe's queue. Opening a desk row is the tree: wells and separations, then the four east-line requests show when that row opens, then Accept / Return / Deny. Precheck findings may still show five property-line FAILs — those are not a fifth request. The 73-check wall is the collapsed technical audit, not the first view. The AHJ sees only the live granted design: Massena Stephens Media 16.002-3-66.1 / 2155 SH 420. That is one job. The desk does not invent a second Massena. Synthetic QA, new-msq* placeholders, and other pre-2026-08-18 records stay off this desk. Today's request jobs are requests, not designs, and are not purged here. All real grants matches the visible table. The desk does not recompute packages. Deny is first-class on the job with the same weight as Accept and Return. Reject remains the stored package id when Deny is recorded. The desk does not invent jobs, fees, or a posted stage.
The three-part record
- Engine finding: a reproducible observation from the submitted record, governing design pack, and calculations. It is retained unchanged.
- Professional disposition: an authenticated engineer selects a defined response, documents the engineering basis, and cites supporting evidence. The record identifies the actor and role; it does not itself prove licensure or replace a seal.
- Authority action: the assigned regulator may request information or record whether a professional disposition is accepted. This account role does not itself establish statutory waiver authority.
Revision binding
Each disposition is accepted only for a finding key independently recomputed on the server from the exact saved design revision. A changed design, stale tab, missing index, or invented key fails closed and requires the current package to be recomputed.
What screening means
Mapped parcels, hydrography, wetlands, terrain, wells, and similar sources can identify concerns and guide design. Screening information is never silently promoted to field, survey, professional, or regulatory truth. The needed evidence is fitness-for-purpose—not automatically the highest possible survey precision.
Professional judgment
The engine is an independent check, not the engineer of record. The authenticated engineer may identify a correction, document why a finding is not applicable, establish compliance from better evidence, request field verification, identify a platform limitation, or document a specific-waiver request. The original finding, actor role, and engineering basis remain visible together.
Specific-waiver lifecycle
An engineer may document and reference a waiver request. A request does not clear a failed separation and does not make the package look compliant. Denied is a recorded AHJ outcome — not a failure of this screen, and not an assumption that a grant will follow. Well-separation findings stay visible through request, grant, and deny. This review screen does not issue or activate a waiver: the written application, eligibility, designated authority, written decision, and applicant advice must be established outside this role label and incorporated into the design record through the controlled waiver workflow. For the current New York design pack, see 10 NYCRR §75.6(b) and Appendix 75-A.11.
An AHJ may request information at any time. Acceptance or non-acceptance is available only after an engineer has recorded a professional disposition for the same finding revision.
Final determination
The automated package precheck is not a permit decision. The regulator's Accept, Return for revision, or Deny determination remains separate and attributed. Reject remains if it already exists as the stored package id. Readiness changes only after corrected evidence is incorporated and the deterministic audit is rerun, except where a valid written waiver expressly covers the identified deviation.
Audit trail
Every superseded disposition is retained with actor, date, basis, and reference. Findings that disappear after correction remain visible in prior-finding history. AI may explain this record but cannot clear a finding, invent evidence, issue a waiver, or make the regulatory determination.