Electrical Code Filing Guide

Use this folder for verbatim code-book excerpts and implementation-facing filing notes.

Filing Rules

Create one markdown file per closely related section set, grouped by code book, edition, article, and topic.
Keep verbatim code language separate from implementation notes. Exact text goes in the section file; interpretation belongs in sizing docs or code comments.
Use a path structure like docs/electrical-code/<code-book>-<edition>/article-<article>/<sections>-<topic>.md.
Start each filing with the source metadata:
code book and edition
article and section numbers covered
why the excerpt matters to the product
any image or scan identifiers supplied with the source material
Preserve the user-supplied wording exactly when asked to file exact language. Do not silently normalize punctuation or rewrite prose.
If a formula image is supplied separately, note the image identifier and describe where it belongs in the section.
When implementation depends on the excerpt, add a short "Implementation impact" section at the end that points to the relevant code paths, but do not mix that commentary into the verbatim text.

Link sizing docs to the filed excerpt rather than duplicating long verbatim code blocks.
Add concise reminders in repo-level AGENTS.md when a code rule is easy to misapply.