Research — Auto Demo · Precomputed (draft, unvalidated)

Service entrance: the compliance walk — auto

No controls here: seven short stories play on their own over one service entrance. The first starts from a bare survey where every card reads incomplete, then builds the service up. Then a water heater creeps into the panel's working space, a bigger transformer outgrows its protective device, a bigger breaker meets the small-conductor cap, a ground wire is pulled too small, a trench is dug too shallow and the disconnect arrangement is bent. Use Pause, or the story and step buttons, to stop on any frame.

About this data · draft, unvalidated harness · screening illustration, not a compliance determination

  • DRAFT, UNVALIDATED. ubm-agent-harness has had no human NEC subject-matter-expert sign-off (its VALIDATION.md).
  • Its NEC table values come from secondary sources, not a licensed NFPA 70 copy.
  • Open questions recorded there include: whether Table 310.16 is the correct 2023 citation, which 110.26(A)(1) exceptions apply (none are modeled), and whether the interrupting-rating check needs an X/R gate (it does not have one).
  • This file is a screening illustration, not a compliance determination.
  • SCENE: a generic three-phase 208Y/120 V building service; every dimension, the source strength (MVA, X/R), the zero path impedance, the device interrupting ratings and the obstruction position are ILLUSTRATIVE (step geometry:'illustrative').
  • The available fault current is computed by circuit-calc-harness calculate_available_fault_current (three-phase bolted only).
  • NEC DATA RULE: no NEC table is shipped; required values appear only as the per-case results of the functions.
File format notes (units, sentinels, grid layout, verdict mapping)
  • UNITS AND SENTINELS: dimensions in inches, currents in amps (kA where named).
  • In `snap`, -1 (numbers) and "" (strings) mean not set / not measured.
  • GRID: top-level axes src_mva x dev_kaic (row-major, last axis fastest); cols verdict, faultKa (computed available fault current at that source strength, kA), reasonStr (string index of the harness violation, -1 if none). `tables`: workspace (condition x voltage_to_ground x depth_in), ampacity (material x size x ocpd_a), egc (material x ocpd_a x egc_size), cover (location x method x cover_in), disc_rating (category x disconnect_a), disc_count (disconnects x enclosure); each {id,title,axes,cols,cells}, same row-major rule, cols verdict + reasonStr.
  • Axes may be strings.
  • VERDICTS: compliant=False -> fail; a 'skipped' or 'incomplete' note -> incomplete; a rule-level 'not applicable' or 'not evaluated' note -> not_applicable (for example a grounding-conductor OCPD rating that is not one of the function's rows); otherwise pass, or tight (workspace and cover: margin under 3 in; interrupting rating: device within 10% of the available current; display bands, not rules).
  • CHECKS per step, in walk order: lateral, disconnect, workspace, aic, svc_ampacity, br_ampacity, egc. `workspace` carries parts [depth,width,height] and failDims; `disconnect` carries parts (five rule groups) and failRules. `reasoning` entries are indexes into `strings`: the function's violations then notes, verbatim (aic and others may be prefixed by one composed line stating the fault-current provenance). `reqNum` is the required value as a number (-1 when none).

Reproduced verbatim from the data file's own note.

Story

Section through the panel wall · to scale in inches, utility side cut with a break mark

passtight (a display band, not a rule)failincomplete, not applicable or not seta required value stated by the datadashed = unmeasured or illustrative

Seven checks at once · click a card to point at what it measures

No whole-service verdict is shown on purpose.

Plan · the panel room seen from above

Device board · rating, breaker, conductor, ground

How the checks read it · the harness's own text, verbatim

Every check · before, after the change, after the fix

Required values are read from the data file. Tight is a display band only, never a rule. Incomplete and not applicable are not passes. There is no whole-service verdict.

Precomputed results:every verdict, required value and margin on this page was computed by the real Python harness at export time and is played back from a data file. The page runs no harness logic and holds no standards tables, and it never interpolates between exported values. Not a live API call. Precomputed by the real functions check_service_disconnect_requirements, check_panel_working_clearance, check_breaker_conductor_ampacity_match, check_equipment_grounding_conductor_size, check_equipment_interrupting_rating, check_underground_installation_cover in ubm-agent-harness (commit 1a920a2), with the available fault current from calculate_available_fault_current in circuit-calc-harness (commit 2589b99). The harness is a draft with no human subject-matter-expert sign-off; its code values rest on secondary sources, not a licensed copy of the code book. Every dimension, the source strength, the X/R, the device ratings and the heater position are illustrative. The fault current is a three-phase bolted value only, for a 208Y/120 V service. The meter and the utility transformer are scenery. Domain maturity: starting inventory, not a completed review.Real functions this maps to:check_service_disconnect_requirements, check_panel_working_clearance, check_breaker_conductor_ampacity_match, check_equipment_grounding_conductor_size, check_equipment_interrupting_rating, check_underground_installation_cover, calculate_available_fault_current, source_impedance_from_fault_mva.Not modeled: the utility lateral, clear space and storage around the panel, exceptions to the working-space rule, an X/R gate on the interrupting rating, other fault types, load calculations, catalog ratings of real devices, and any real building. The drawing is schematic.See also:Service entrance, interactive with free play · Breaker against conductor, hands-off