/* =========================================================================== tool-chassis.css — the shared chassis every Coastal SD Pros tool is built on. READ THIS BLOCK. It is the whole contract. Eight tools are being built in parallel against this file; if you invent a class instead of using one below, the tools stop looking like one product and the directory stops looking like it has evidentiary discipline. Load order on a tool page: and, in , before any stylesheet, the no-flash JS flag: This file is standalone. It mirrors the ten canon palette tokens itself (see the :root block immediately below), so it does not require v4.css. Loading it next to v4.css is safe — same names, same values. --------------------------------------------------------------------------- 1. SHELL — the six regions every tool has, in this DOM order --------------------------------------------------------------------------- .tc-tool Root of one tool. Sets the corrected focus ring for everything inside. Use
. .tc-tool__head Region 1+2+3: title, purpose, method disclosure. Emitted by _partials/tool-shell.html — do not hand-write. .tc-tool__title Region 1. The tool name.

. id="ID-title". .tc-tool__purpose Region 2. ONE sentence: what the tool does. No claims. .tc-method Region 3.
method disclosure. Closed by default, fully readable with JS off. .tc-method__summary "How this works, and what it does not tell you" .tc-method__body Wrapper for the disclosure content. .tc-method__h

inside the disclosure. .tc-method__p Paragraph inside the disclosure. .tc-input Region 4. The input region. Normally a
. .tc-input__legend Optional heading for the input region. .tc-result Region 5. The result region. Holds .tc-field / .tc-held. Do NOT put aria-live on it — announce via .tc-live. .tc-result__head Optional heading row inside the result region. .tc-foot Region 6. Source + checked-date footer. REQUIRED on every tool, even a tool whose output is held. .tc-foot__label "Sources" label. .tc-foot__list
    of sources. .tc-foot__item per source. .tc-foot__item One source line — carries a .tc-chip. --------------------------------------------------------------------------- 2. PROVENANCE CHIP — source name + checked date, travelling with the value --------------------------------------------------------------------------- .tc-chip "SOURCE NAME · checked DATE". A SINGLE text node — children become extra flex items and add a phantom gap. Put one next to every fact, every blank, every source. .tc-chip--held Same chip, sand ground. For a line where the source and date are known but the value is not on hand. Compatibility: `.tc-tool .stamp--chip` is styled identically, so the existing _partials/provenance-chip.html stamps into a tool unchanged and renders the same as .tc-chip. Either is correct; the stamped partial is preferred because it cannot drift. The chip's leading dot is a DOT, deliberately not a checkmark. A checkmark reads as "verified". This site does not verify anyone. Do not change it. --------------------------------------------------------------------------- 3. FACTS + THE HONEST BLANK --------------------------------------------------------------------------- .tc-field One fact: label, value, chip. The only fact container. .tc-field__label What the fact is ("License status"). .tc-field__value The value. Only ever a real, sourced value. .tc-field__note Plain-language caveat that must travel WITH the value. Mandatory sentence for workers' comp, verbatim: "Workers' compensation is not general liability insurance. This line says nothing about whether this business carries general liability cover." .tc-field--blank THE HONEST BLANK. Same box, same padding, same type size and weight as a populated field. It is a result, not an apology. Never dim it, never italicise it, never add opacity. (.tc-field__state shares its entire declaration with .tc-field__value so the two cannot drift apart. Keep it that way.) .tc-field__state The blank's value slot: "Not published", "Not on the record". Written as a fact about the record. .tc-field__where Where the homeowner checks instead, with a real link. --------------------------------------------------------------------------- 4. HELD OUTPUT — for a tool whose method ran but whose input is missing --------------------------------------------------------------------------- .tc-held Gated result. Shows the method ran; names the missing input and who supplies it; shows NO number, no range, no estimate, no progress bar. If you are tempted to render "approximately", you are rendering an invention. .tc-held__title "The method ran. The output is held." .tc-held__ran
      of the steps that actually executed. .tc-held__missing What input is missing, in plain words. .tc-held__who Who supplies it and how it arrives. .tc-held__rule Coral marker bar. Decoration only — the words carry the meaning. Coral is capped at 2% of the page. --------------------------------------------------------------------------- 5. FORM PRIMITIVES — native controls, 44px targets, plain-language errors --------------------------------------------------------------------------- .tc-form Grid wrapper inside .tc-input. .tc-control One labelled control. Wraps label + hint + field + error. .tc-label