/* ===================================================================== OUR ORIGINS — page sheet for src/pages/our-origins.html No colour value appears here. Everything refers to css/tokens.css. SCOPE IS BY SELECTOR THROUGHOUT. Every rule is reached through `.a-hero`, `.a-cta`, `.jcol-lead`, or the memorial's own `.mango*` and `#mango`. Nothing here is keyed to a position in the document or to a count of anything, and no rule reaches an element it does not name. THE FOUR PAGE-CHROME RULES ARE COPIED FROM css/pages/our-team.css AS AUTHORED, not re-derived. `.a-hero .kick` and `.a-hero .body` are reached through the hero wrapper; `.a-cta` styles the hero's call-to-action paragraph; `.jcol-lead` styles the copy column of the join band. THE MEMORIAL'S RULES AT THE FOOT OF THIS FILE ARRIVED BYTE-IDENTICAL and are governed by the block that precedes them. Read it before touching any `.mango*` or `#mango` selector. `.jcol-lead` IS AUTHORED HERE RATHER THAN IN components/join-form.css BECAUSE THE ELEMENT IT STYLES IS NOT IN THAT PARTIAL. join-form.html carries no copy column. The paragraph lives in this page's own join wrapper, so the rule lives exactly as wide as the element does. A page whose sheet omits this rule inherits nothing for that paragraph — the shared sheet has never carried it. ===================================================================== */ /* ---- PAGE-LOCAL DEVIATION REGISTER ---------------------------------- Prefix OO-. Numbered from 1 and never renumbered. OO-1 · THE JOIN BAND'S COPY IS BORROWED, NOT WRITTEN FOR THIS PAGE. partials/components/join-our-origins.html carries the heading and lead paragraph of partials/components/join-about.html, character for character, on instruction and as a placeholder. It is NOT copy chosen for this page and no part of it was authored here. When the client supplies per-page join copy, that wrapper is rewritten and this entry is closed. Until then the two files say the same thing by borrowing, not by design — changing one does not change the other. OO-2 · THE FOUR HERO STRINGS ARE DIRECTOR-DRAFTED, NOT CLIENT-SUPPLIED. Eyebrow, h1, body and CTA in src/pages/our-origins.html were drafted and approved 2026-08-14 and are set exactly as given — no typographic correction, no re-wrapping, no smart quotes. Same status as OO-1: they stand until the client supplies copy written for this page, and replacing them is a copy change. Verified at authoring by codepoint: the CTA's arrow is U+2192 preceded by one U+0020. The body contains no dash. OO-3 · THE META DESCRIPTION IS BESPOKE AND DIRECTOR-DRAFTED. It was drafted and approved 2026-08-14 and is set exactly as given. It no longer duplicates the hero body — an earlier draft of this page repeated that string verbatim, which is the wrong shape for a description. Same status as OO-1 and OO-2: director-drafted, not client-supplied. AUTHORING WAS THE ONLY PATH, AND THAT WAS ESTABLISHED BY MEASUREMENT RATHER THAN ASSUMED. A mechanical derivation was looked for first. Across the seven pages that predate this one, NONE opens with its title's subject, NONE contains its own h1, and no two share an opening construction; lengths run 119 to 181 characters and sentence counts run one to three, and even the em dash appears in only some of them. Each is a bespoke editorial summary of its own page's argument. There is no pattern to follow, so no derivation was available and none was invented. A CLIENT-SUPPLIED DESCRIPTION REMAINS OPEN. Replacing this one changes a single attribute in src/pages/our-origins.html and this entry with it. OO-4 · THE PAUL MANGO MEMORIAL ARRIVED HERE BYTE-IDENTICAL, 2026-08-14. It was moved from the about page by director ruling and NOTHING about it was rewritten, merged or re-scoped in transit. Verified by sha taken FROM THIS FILE AND FROM src/pages/our-origins.html AFTER PLACEMENT, never carried forward from the cut: the
markup 2,290 B sha 7debe0aa… the thirteen rules at the foot 1,537 B sha 40dd2375… THE PORTRAIT WAS NEVER OPENED. assets/mango-paul-1024x544.jpeg is untouched at sha 1d47a059f0b8f0202d… — the same value before the move, after the move, and when fetched from the built page over localhost. The src string moved character-identical. The portrait rule is absolute here: no AI generation, upscaling, enhancement or processing, ever. THE ORNAMENT RULE IS NOW A DIRECT REQUIREMENT OF THIS SECTION AND CARRIES NO CROSS-PAGE REFERENT. It previously justified itself by contrast with a section on the about page — "the opposite of §4, on the same page" — and that reasoning became uncheckable the moment the two sections stopped sharing a document. A rule that can only be verified by opening a second file is not a rule anyone will verify. It is restated in the block above the memorial's own rules, on its own terms: the typed U+0022 pairs ARE the quotation signal, an unornamented blockquote here is the ruling rather than a defect, and marks and ornament may never both be present. THE MEMORIAL IS CLIENT COPY AND IS NOT COVERED BY OO-2. Its heading, four paragraphs, two quotations and two attributions came from the client copy source and are FROZEN. OO-2 covers the hero strings only, which are director-drafted. The two provenances sit on one page and must not be collapsed into one — replacing the hero copy does not license touching a word of the memorial. OO-5 · THE MEMORIAL'S GROUND WENT TO SAND, 2026-08-16, unit G3. Director change. The
ground moves --paper -> --cream and the two .mango-card boxes invert --ground-alt -> --white. NOT ONE CHARACTER OF COPY AND NOT ONE LAYOUT PROPERTY MOVED — the memorial's content and layout stay out of scope and every measurement below came back metric-free. THE CARD CHANGE IS LOAD-BEARING, NOT COSMETIC, AND THE REASON IS NOT THE ONE THE DISPATCH GAVE. `--ground-alt` AND `--cream` ARE ONE VALUE — rgb(246,240,230), resolved by paint, luminance 0.87626. The cards were ALREADY sand before this unit; they read as cards only because the section behind them was paper. Move the section to sand and leave the cards alone and the boundary is 1.0000: BOTH TRIBUTES ERASE INTO THE GROUND. The dispatch reached the right ruling from "white is stronger than paper", which describes a choice between two viable fills; measured, there is no second viable fill. A border is the only alternative and it is a new declaration on a section whose absences are deliberate — see the ornament ruling below. White, ruled 2026-08-16. THE 1.0694 ON RECORD IS THE EDGE THIS UNIT REMOVES, NOT AN AFTER-STATE. It is the sand card sitting on the paper section TODAY. The after-state is --white on --cream at 1.1336. Do not read the two as candidates. RE-DERIVED, ALL FOUR WIDTHS 1440/1028/768/390, all measured on the built page after transitions settled: h2.mango-h2 --accent 3.9310 -> 3.6759 LARGE 3.0 PASS p.mango-lead --on-page-body 8.0825 -> 7.5580 SMALL 4.5 PASS p (body x2) --on-page-body 8.0825 -> 7.5580 SMALL 4.5 PASS p.mango-close --on-page-body 8.0825 -> 7.5580 SMALL 4.5 PASS blockquote --on-page 13.0839 -> 14.8318 SMALL 4.5 PASS figcaption --on-page-body 7.5580 -> 8.5676 SMALL 4.5 PASS card boundary --white/--cream 1.0694 -> 1.1336 non-text, no border THE h2 IS LARGE BY SIZE ALONE AND DOES NOT REST ON THE 18.66/700 BOUNDARY. Measured 46 / 34.952 / 28 / 28 px at weight 700 — the floor clears the 24px any-weight boundary by 4px. That is a different guarantee from .vm-label on our-approach, which does rest on 18.66/700, and the two must not be reasoned about together. THE SECTION IS NOW A SAND ISLAND BETWEEN TWO PAPER SECTIONS and both its seams are 1.0694 — hero -> #mango at y=516.266 and #mango -> #join at y=1492.641, gap 0.000 at each. ACCEPTED, director-ruled 2026-08-16, as the intended separation. 9an resolved a paper->cream soft step by routing it paper->plum->cream; THAT PRECEDENT DOES NOT BIND HERE. It governed a seam between two argued sections carrying continuous prose. This is a memorial set apart from the page around it, where a soft edge is the point rather than a defect, and our-team.html has shipped two live 1.0694 seams around .band-cream since before this unit. --------------------------------------------------------------------- */ .a-cta{margin-top:32px} .a-hero .body{max-width:60ch} .jcol-lead{ margin-top:22px; font-size:17.5px;line-height:1.6; color:var(--on-page-body); max-width:46ch; } .a-hero .kick{font-size:14px} /* ===================================================================== THE PAUL MANGO MEMORIAL. READ THIS BEFORE CHANGING ANYTHING BELOW. Paul Mango died in early 2025. This section is a memorial and it is NOT A DESIGN OPPORTUNITY. Every property below is chosen for restraint and the absences are as deliberate as the declarations. Each is stated as a requirement of these rules on their own terms, checkable here. NO ORNAMENT. `.mango-quote` gets no ::before, no gold mark, no rule, no border, no drop cap and no pull-quote type. ITS TWO QUOTATIONS CARRY THE LITERAL U+0022 PAIR THAT THE COPY SOURCE PRINTS, and that typed pair IS the quotation signal — which is precisely why no ornament is needed. AN UNORNAMENTED BLOCKQUOTE IS NORMALLY A DEFECT AND HERE IT IS THE RULING. A future reader will see a blockquote with no ornament and be tempted to add one. DO NOT. If an ornament is ever added, the typed marks must come out in the SAME edit, or the quotation renders twice. NO PORTRAIT-READY CONTAINER BEYOND THE ONE PORTRAIT ALREADY PLACED. These rules are deliberately not built to accept a further picture. NO ENTRY ANIMATION. The section carries no .rv and is simply present at load. That is not an omission. NO ADDED DATES, NO ADDED EPITAPH, NO ADDED HEADING. The client's own header stands. His name appears exactly where the copy source puts it. THE PORTRAIT RULE IS ABSOLUTE. The image is never AI-generated, upscaled, enhanced or processed; mechanical crop and resize only, from a client original. Its only structural marker is id="mango", for deep linking. ===================================================================== */ /* ---- TWO-COLUMN TREATMENT ------------------------------------------- THE h2 IS --accent AND THE TRIBUTE CARDS SIT ON --ground-alt. Those two are the whole of the decorative treatment and both were director decisions. No band ground, no texture, no gold, no band class on the
itself, and no .rv. THE CARD GROUND IS --ground-alt AND IT IS A TOKEN, NOT A LITERAL. Cream is the tinted light token and is marginally the more distinct against the page ground (1.0694 against paper; --ground-field is 1.0600 and LIGHTER than the page). --ink-on-dark would have been more separated at 1.6093 but it is a foreground token for dark grounds and using it as a ground would misname it. THE CREAM TRAP APPLIES TO THIS CARD. On --ground-alt, --slate measures 4.3009 and --on-page-soft 4.6361. The attribution therefore takes --on-page-body (7.5580). Moving a colour onto cream without re-measuring is exactly how that trap bites. TWO COLUMNS AT >=1000px. Below it the grid is one column and the reading order is the DOM order: heading, prose, closing, portrait, then the two tributes. THE PORTRAIT IS LANDSCAPE — 1024x544, 1.882:1. The display box is given the SOURCE ASPECT via aspect-ratio:1024/544, so `cover` crops NOTHING on either axis; a square-ish box would have cut roughly half the frame. max-width:420px caps it so the DPR-2 need never exceeds the 544px short side: at 420 wide the box is 223.14 tall, needs 446.28, and holds 1.219x. WITHOUT THAT CAP a full-width stacked portrait at 599 would be 531 wide / 282 tall, need 564, and fall to 0.965x — below native. The cap is a headroom guarantee, not a layout preference. --------------------------------------------------------------------- */ /* THE GROUND IS A NEW DECLARATION, NOT A CHANGED ONE. This section painted nothing before G3 and inherited the page ground from ; the rule below is the first background it has ever carried. See OO-5. */ #mango{background:var(--cream)} .mango{display:grid;gap:40px} @media(min-width:1000px){ .mango{ grid-template-columns:minmax(0,1fr) minmax(0,420px); column-gap:56px;row-gap:40px; align-items:start; } } .mango-main{min-width:0} .mango-side{min-width:0;display:grid;gap:28px;align-content:start} #mango .mango-h2{color:var(--accent);margin:0} #mango .mango-main p{margin-top:20px;font-size:16.5px;color:var(--on-page-body);max-width:62ch} /* SPECIFICITY, NOT SOURCE ORDER. `#mango .mango-main p` above is (1,1,1) and sets 16.5px; a rule written as `#mango .mango-lead` is (1,1,0) and LOSES to it, so the lead silently rendered at body size. Measured 16.5 where 20 was authored. The element selector is restated here to match at (1,1,2). Same failure shape as §18 — a rule that looks authoritative and is simply outranked. */ #mango .mango-main p.mango-lead{ margin-top:26px; font-size:20px;line-height:1.6; color:var(--on-page-body); } #mango .mango-main p.mango-close{margin-top:26px} .mango-portrait{margin:0;max-width:420px} .mango-portrait img{ display:block;width:100%;height:auto; aspect-ratio:1024 / 544; object-fit:cover; } /* --white, AND IT IS THE ONLY VIABLE FILL RATHER THAN THE PREFERRED ONE. `--ground-alt` IS `--cream` — one value, rgb(246,240,230). Since G3 the section behind these cards is --cream, so --ground-alt here would render the tributes at 1.0000 against their own ground and both would disappear. The card reads because of this line. --white on --cream is 1.1336 and there is deliberately NO BORDER — see the ornament ruling above, which governs this section's absences. OO-5 carries the full derivation. */ .mango-card{ margin:0; background:var(--white); padding:32px 34px; } #mango .mango-quote{ margin:0; font-family:var(--serif); font-size:18.5px;line-height:1.5;font-weight:400; color:var(--on-page); } #mango .mango-attrib{ display:block;margin-top:16px; font-family:var(--serif); font-size:15px;line-height:1.5; font-style:normal; color:var(--on-page-body); }