Reference

Design system

This page is noindex: it documents the template for whoever builds with it. Every contrast ratio below was computed against the WCAG relative-luminance formula before shipping, not eyeballed.

The palette, measured

RESEARCH.md names #45762D — hue ∼100°, S ∼45%, L ∼32% — an olive/moss green, measured distinct from day 129's forest green (#42621A, hue ∼87°) and day 130's (#255F27, hue ∼122°), sitting between them but pushed toward an olive/ochre register. RESEARCH.md's own stated contrast figures — ink #2B2620 on ground #F3ECDD at 12.7:1, accent #45762D on ground at 4.6:1, accent on white at 5.4:1, white on accent (buttons) at 5.4:1 — were checked against the same WCAG relative-luminance formula used everywhere else in this library and matched exactly, to two decimal places (12.74:1, 4.60:1, 5.41:1, 5.41:1). No correction was needed on the palette figures themselves.

The 4.60:1 accent-on-ground figure is the tightest margin in this template's palette: it clears WCAG AA for normal-size text (the 4.5:1 threshold) but not AA for text below normal body size, and not AAA at any size. The accent is therefore never used for text smaller than the page's base body size (the eyebrow labels, which run smaller, use --color-text-muted instead — see src/styles/global.css's .eyebrow rule).

One figure needed adding, not correcting: the footer inverts to an ink-dark band (#2B2620), and the raw accent used directly as text there measures only 2.77:1 — not accessible. A lightened olive, #8CBB66, was derived for that one context and measures 6.72:1 on the band, comfortably AA. It is used nowhere else; every other accent reference on the page is the unmodified #45762D.

Typography

Domine for headings and pull-quotes — a transitional serif purpose-built for web headlines with real weight contrast, unused elsewhere in this batch. Karla for body, UI, nav, labels and every table cell, with tabular-figure alignment set via CSS (font-variant-numeric: tabular-nums) on figure-bearing cells, not a separate monospace face. No monospace anywhere on this page: nothing here is a live-computed or ledgered number in the way furniture-designer's board-feet or jewelry-designer's live total are — the one computed figure this page ships (the FF&E schedule's sample totals) is a static, build-time sum over committed demo data, not a running calculator.

Schema.org — what's settled, what's withheld

ProfessionalService carries a real PostalAddress (Santa Fe, NM) and areaServed Santa Fe County — residential design is tied to a service area the way day 137's architecture practice was tied to a licensing jurisdiction, and asserting that area is the honest claim here. Person is Marisol Griego as founder. Three Service blocks (full-service, room refresh, e-design) each carry no price or priceRange — a fourth, distinct reason in this batch's running ledger: the markup on FF&E exists and is disclosed, but only in the signed, project-specific written agreement ASID's own ethics code requires, not as a blanket public rate. Publishing one number here would misstate a practice the trade's own ethics code treats as necessarily individual — a different reason from day 135's unbuilt cut list or day 137's not-yet-estimated construction cost.

Withheld deliberately: aggregateRating (no reviews collected); Product/Offer anywhere on the page (FF&E is procured on the client's behalf through trade accounts, never stocked or checked out here, unlike day 129/131's current-stock Product+Offer pattern); gtin/mpn (not applicable to specified-not-sold goods).

A correction to RESEARCH.md's own citation

RESEARCH.md's axis cites “ASID Code of Ethics, Section 3.4” as the full-disclosure-of- compensation clause. Fetching the ASID Arizona South chapter's published Code of Ethics (azs.asid.org/code-of-ethics, the source RESEARCH.md itself lists) shows the disclosure requirement is actually Section 3.3: “Members shall fully disclose to a client all compensation that the member shall receive in connection with the project and shall not accept any form of undisclosed compensation from any person or firm with whom the member deals in connection with the project.” Section 3.4 in the same document is a different clause entirely — client confidentiality and permission to use project photographs. Every reference to the disclosure clause on this page and in its tests cites 3.3, not 3.4. The brief's California-specific-contract-language and named-court-case claims are not repeated here in specific form, since they could not be verified against a primary source in the time available for this build; the page instead states, generically and defensibly, that several states impose additional written-disclosure requirements and that undisclosed markups have exposed designers to liability in reported cases, without naming an unverified jurisdiction or case.

One module, read by the one computed figure on the page

src/lib/ffe.ts's ffeTotals() is the only place the FF&E schedule's trade cost, client price and markup percentage are summed. Both the home page's FF&E schedule table footer and this template's tests read the same function against the same src/data/config.ts rows, so the sum shown can never quietly drift from the rows it's computed from.

Tokens