arkaos 4.28.0 → 4.30.0

package/departments/landing/skills/page-architect/references/impeccable.LICENSE

@@ -0,0 +1,191 @@
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to the Licensor for inclusion in the Work by the copyright
+      owner or by an individual or Legal Entity authorized to submit on
+      behalf of the copyright owner. For the purposes of this definition,
+      "submitted" means any form of electronic, verbal, or written
+      communication sent to the Licensor or its representatives, including
+      but not limited to communication on electronic mailing lists, source
+      code control systems, and issue tracking systems that are managed by,
+      or on behalf of, the Licensor for the purpose of discussing and
+      improving the Work, but excluding communication that is conspicuously
+      marked or otherwise designated in writing by the copyright owner as
+      "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   Copyright 2025 Paul Bakaus
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

package/departments/landing/skills/page-architect/references/layout-craft.md

@@ -0,0 +1,236 @@
+# Layout Craft — space, rhythm, responsive floors
+
+> Derived from [hallmark](https://github.com/nutlope/hallmark) (MIT) and [impeccable](https://github.com/pbakaus/impeccable) (Apache-2.0) — see `hallmark.LICENSE` and `impeccable.LICENSE` in this references directory.
+
+Layout is where "AI-generated" gets caught. Equal columns, everything centred, every card identical — these are the tells. Space is the most underused design tool: find the layout's *actual* problem (monotone spacing, weak hierarchy, identical card grids) and fix the structure, not the surface.
+
+Hard floors live in `departments/brand/references/uiux-knowledge-and-tools.md` §12 — this file is the craft on top of them, not a restatement.
+
+---
+
+## Spacing scale & rhythm
+
+- **Spacing is a scale, not a value.** Pick one scale. Use it everywhere. Don't type raw px. Values come from a defined set — a framework scale, rem-based tokens, or a custom system — never arbitrary numbers.
+- **4pt base, nine steps, named by role, not size.** This is the same base-4px scale as the doctrine hub §3 (`departments/brand/references/uiux-knowledge-and-tools.md`) — one scale, stated once. Prefer 4pt over 8pt: 8pt is too coarse and you'll frequently need 12px between 8 and 16.
+
+```css
+:root {
+  --space-3xs: 0.125rem;  /*  2px */
+  --space-2xs: 0.25rem;   /*  4px */
+  --space-xs:  0.5rem;    /*  8px */
+  --space-sm:  0.75rem;   /* 12px */
+  --space-md:  1rem;      /* 16px */
+  --space-lg:  1.5rem;    /* 24px */
+  --space-xl:  2.5rem;    /* 40px */
+  --space-2xl: 4rem;      /* 64px */
+  --space-3xl: 6rem;      /* 96px */
+  --space-4xl: 9rem;      /* 144px */
+}
+```
+
+- Name tokens semantically: `--space-xs` through `--space-4xl`, not `--spacing-8`.
+- Use `gap` for sibling spacing. It's cleaner than stacked margins, participates in flex/grid, collapses predictably, and eliminates margin-collapse hacks. Use `margin` only for optical adjustments or breaking out of the flow — never for a list of siblings.
+- Apply `clamp()` for fluid spacing that breathes on larger screens.
+
+**Rhythm** is contrast, not uniformity:
+
+- **Tight grouping** for related elements (8–12px between siblings).
+- **Generous separation** between distinct sections (48–96px).
+- **Varied spacing** within the same layout. If every gap is 24px, the page is a template — mix small, medium, and large gaps; not every row needs the same gap.
+- **Density matches content type.** Data-dense UIs need tighter spacing; marketing pages need more air. Too cramped and it suffocates; too sparse and the whitespace is purposeless.
+- **Generous top, tight bottom** (or vice-versa). Sections don't need to be evenly padded — if the card padding equals the section padding equals the page padding, the rhythm is flat.
+
+---
+
+## Asymmetry & hierarchy
+
+- A layout has a **primary axis**. Left-biased, right-biased, top-heavy, or bottom-weighted. Centre-biased is a default, not a choice.
+- **Asymmetry reads as intentional.** Symmetry reads as generated. When in doubt, shift. But asymmetric composition is a deliberate choice when the content invites it — not a default to chase.
+- **Break the grid on purpose.** A page with one element crossing the grid is stronger than a page that never does.
+
+**The squint test.** Blur your (metaphorical) eyes. Can you still identify the most important element, the second most important, and the clear groupings? Does whitespace guide the eye to what matters? If not, the hierarchy is weak regardless of how the colors and fonts look.
+
+Use the fewest dimensions needed for clear hierarchy — space alone can be enough; generous whitespace around an element draws the eye. The best hierarchy combines 2–3 dimensions at once: a heading that's larger, bolder, AND has more space above it reads as primary without trying.
+
+| Tool | Strong Hierarchy | Weak Hierarchy |
+|------|------------------|----------------|
+| **Size** | 3:1 ratio or more | <2:1 ratio |
+| **Weight** | Bold vs Regular | Medium vs Regular |
+| **Color** | High contrast | Similar tones |
+| **Position** | Top/left (primary) | Bottom/right |
+| **Space** | Surrounded by white space | Crowded |
+
+Be aware of reading flow: in LTR languages the eye scans top-left to bottom-right, but primary action placement depends on context (bottom-right in dialogs, top in navigation). Create groupings through proximity and separation.
+
+**Asymmetry techniques:**
+
+- **Wide left margin.** Treat the left as permanent negative space — narrow column of labels, wide column of content. Labels must NOT be section eyebrows / numbers paired with the heading — that's gate-54-banned. Reserve this technique for body-level micro-labels (caption, footnote, date) alongside body copy.
+- **Hanging headers.** ⚠️ **Opt-in only.** Section labels sit in the left margin; content flows right. Permitted only when the user explicitly asks for an editorial / hanging-header layout AND no eyebrow / number / chapter tag sits in the left margin. The eyebrow-left / heading-right pattern is banned by slop-test gate 54 — the most reliable templated-editorial AI tell. Default to a stacked single-column section head.
+- **Offset grids.** Odd columns wider than even. Or the other way.
+- **Grid-breaks.** One element that deliberately extends past a column boundary: a pull-quote, a photograph, a rule, a number.
+- **Alignment coherence.** A section head's horizontal alignment should be a deliberate choice that *coheres* with the body it introduces — match it (left head over left-flush body; centred head over symmetric body) or break from it on purpose. The AI mistake is the *accidental* mismatch: a narrow head block auto-centred (`margin-inline: auto` plus a `max-width` / `ch` cap) left floating over full-width, left-flush content. Centred, hanging, bottom-aligned, and asymmetric heads all stay on the table — the guard is intentionality, not uniformity.
+
+**Card discipline:**
+
+- Don't default to card grids for everything; spacing and alignment create visual grouping naturally.
+- Use cards only when content is truly distinct and actionable. Never nest cards inside cards — a bordered container inside a bordered container. Pick one; use spacing and dividers for hierarchy within.
+- The identical feature grid — three columns, three icons, three two-line headings, three three-line bodies — is *the* AI tell. Vary card sizes, span columns, mix cards with non-card content, use `grid-template-columns: 1.2fr 1fr 0.8fr`, or give items different spans on a 12-column underlying grid.
+- Don't default to the hero-metric layout (big number, small label, stats, gradient) as a template. A prominent metric works only when it displays actual data, not decorative numbers.
+
+**Depth:**
+
+- Depth is **weight and scale**, not shadow. A heavier weight, a larger size, a warmer hue — these create hierarchy better than drop shadows. Elevation reinforces hierarchy; it is never decoration.
+- If you use shadow, use one from a consistent, subtle scale:
+  - **Whisper** — `0 1px 2px oklch(20% 0.01 <hue> / 0.05)` for hovering cards.
+  - **Hairline** — `0 0 0 1px oklch(30% 0.01 <hue> / 0.06)` as an alternative to a 1px border.
+- Never stack multiple shadows. Never use a coloured glow on a light background; a drop shadow on a dark card creates an accidental glow — that's wrong.
+
+**When in doubt** — if the layout looks fine but flat, do one of these before shipping:
+
+1. Add one break-out element.
+2. Unbalance a column width.
+3. Move the primary CTA out of the centre.
+4. Remove a card and replace it with negative space.
+5. Change one section's padding so the rhythm is uneven.
+
+---
+
+## Optical adjustments
+
+- If an icon looks visually off-center despite being geometrically centered, nudge it. But only if you're confident it actually looks wrong — don't adjust speculatively.
+- Text at `margin-left: 0` looks slightly indented because of letterform whitespace; a negative margin (`-0.05em`) optically aligns it. Geometrically centered glyphs often look off-center (play icons need to shift right, arrows shift toward their direction).
+- Touch targets must be 44×44px minimum even when the visual element is smaller. Expand the hit area with padding or a pseudo-element:
+
+```css
+.icon-button { width: 24px; height: 24px; position: relative; }
+.icon-button::before {
+  content: ''; position: absolute; inset: -10px;
+}
+```
+
+---
+
+## Container & grid
+
+- **Flexbox for 1D layouts**: rows of items, nav bars, button groups, card contents, most component internals.
+- **Grid for 2D layouts**: page-level structure, dashboards, data-dense interfaces, anything where rows AND columns need coordinated control.
+- `grid-template-columns: repeat(auto-fit, minmax(280px, 1fr))` for fluid responsive grids without media queries. On tracks containing images, use `minmax(0, 1fr)`, never bare `1fr` (gate 50).
+- Use **named grid areas** (`grid-template-areas`) for complex page layouts; redefine them at breakpoints.
+- Use **container queries** for components, viewport queries for page layouts. A card in a narrow sidebar stays compact while the same card in a main content area expands automatically:
+
+```css
+.card-container { container-type: inline-size; }
+.card { display: grid; gap: var(--space-md); }
+@container (min-width: 400px) {
+  .card { grid-template-columns: 120px 1fr; }
+}
+```
+
+- **Page-edge clipping.** Any deliberately overflowing element (clipped-edge hero media, full-bleed marquee, oversized headline — see [`hero-enrichment.md`](hero-enrichment.md) E1/HP2) needs `overflow-x: clip` on both `html` and `body` as the global safety net, with the containing section left `overflow: visible`. Use `clip`, never `hidden`: `clip` preserves `position: sticky`/`fixed` on descendants; `hidden` creates a new scroll container that breaks sticky and can trap focus.
+- **Z-index is a named scale**, not freestyle numbers — no `z-index: 9999`.
+
+The layout laws behind these bullets — the z-index level set, the overflow rules, the viewport-unit and width bans — live in the doctrine hub. Point there; don't restate: `departments/brand/references/uiux-knowledge-and-tools.md` §12.
+
+---
+
+## Responsive floors
+
+Mobile-first. Content-driven breakpoints. No desktop-only interactions.
+
+### Non-negotiable widths
+
+Every output must render flawlessly at **320 px, 375 px, 414 px, and 768 px** CSS-pixel widths. Eyeball each viewport before marking the output complete:
+
+- No horizontal scroll (slop-test gate 34)
+- No clickable text wrapping to two lines (gate 49)
+- No image-bearing grid pushing the layout past viewport — `minmax(0, 1fr)`, never bare `1fr`, on tracks containing images (gate 50)
+- Root carries `overflow-x: clip` on both `html` and `body` — never `hidden` (gate 34)
+- Display headers wrap inside long words via `overflow-wrap: anywhere; min-width: 0` (gate 51)
+- Section heads collapse to one column on mobile across every register variant — per-register overrides need a matching mobile rule (gate 52)
+- No scroll-jump on radio-tab clicks — radios in normal flow OR JS guard with `focus({ preventScroll: true })` (gate 53)
+
+This is a hard floor, not a wish list. A page that fails any of these on any of those four widths is not done. Keep this checklist near the screen while building; the design-review skill (`departments/brand/skills/design-review`) audits against it.
+
+### Breakpoints & fluid scaling
+
+- Base styles are for the smallest viewport. `min-width` media queries add as you go up — never `max-width` as the primary direction.
+- Breakpoints are where the *content* breaks, not where a device sits. If the headline reflows awkwardly at 720px, that's a breakpoint — regardless of framework defaults.
+- Three or four breakpoints, content-driven, in `rem` so they respect the user's font size:
+
+```css
+@media (min-width: 40rem) { /* ~640px — tablet, small laptop */ }
+@media (min-width: 60rem) { /* ~960px — desktop baseline */ }
+@media (min-width: 90rem) { /* ~1440px — wide */ }
+```
+
+- Prefer `clamp()` for sizes that change continuously; media queries for layouts that change discretely:
+
+```css
+h1 { font-size: clamp(2.5rem, 4vw + 1rem, 6rem); }
+.container { padding-inline: clamp(1rem, 4vw, 4rem); }
+```
+
+- Use `pointer` and `hover` media queries to detect *interaction capability* instead of width. Never build a mouse-hover interaction that has no touch equivalent:
+
+```css
+@media (hover: hover) and (pointer: fine) {
+  .card:hover { transform: translateY(-2px); }
+}
+@media (pointer: coarse) {
+  .btn { min-height: 48px; }
+}
+```
+
+### Mobile collapse discipline — clickable text never wraps
+
+Buttons, primary nav links, footer links, tab labels, breadcrumbs, and CTAs must read as **single-line affordances at every viewport between 320 px and 1920 px**. A button or nav link wrapping to two lines looks broken — visitors read it as a styling error, not as intentional.
+
+```css
+/* Affordances are single-line — let the parent reflow, not the label. */
+.btn,
+.nav__link,
+.foot__link,
+.cta {
+  white-space: nowrap;
+}
+```
+
+```css
+/* When the row can't fit, collapse the row, not the labels. */
+@media (max-width: 40rem) {
+  .nav__rail { display: none; }         /* desktop nav hides */
+  .nav__sheet-toggle { display: grid; } /* mobile menu shows */
+}
+```
+
+**Order of fixes**, when something does wrap:
+
+1. **Shorten the label.** *"Get started free"* → *"Start free"*. *"Read the documentation"* → *"Read docs"*. *"Schedule a demo"* → *"Book demo"*. Most CTA labels are 30–40 % longer than they need to be.
+2. **`white-space: nowrap`** on the affordance, let the parent flex/grid reflow.
+3. **`hidden=until-found`** the lowest-priority nav item at narrow widths (it remains in DOM for find-in-page and SEO).
+4. **Collapse the nav** into a sheet / off-canvas / disclosure menu below a content-driven breakpoint.
+
+**Never:** let a primary CTA or top-level nav link wrap. Long footer-link labels can wrap *only* in a footer column where wrapping is part of the column's rhythm — not in an inline footer link strip.
+
+### Small-screen residue
+
+- `dvh` / `svh` / `lvh` instead of `vh` for heights that interact with mobile chrome; never `width: 100vw` (scrollbar overflow) — use `width: 100%` with padding.
+- Safe areas for iOS notch / Android nav bars: `viewport-fit=cover` on the meta viewport plus `padding-inline: max(1rem, env(safe-area-inset-left))` and `padding-bottom: max(1rem, env(safe-area-inset-bottom))`.
+- Tables that won't fit: collapse to cards (`display: block` on `<tr>` + `data-label` via `::before`) — or better, redesign the data; tables are rarely the right mobile representation.
+- Images: `srcset` with width descriptors, `<picture>` for art direction, `loading="lazy"` below the fold, and `width`/`height` attributes on every image to avoid CLS.
+- Internationalisation: reserve 30–40% extra horizontal space for German, Russian, and Finnish; use logical properties (`margin-inline-start`, `padding-block`, `border-inline-end`) so RTL comes for free; don't hard-code language-specific punctuation or date formats.
+
+---
+
+## Verify
+
+Answer each item by citing the file, selector, or value that satisfies it — never a bare yes:
+
+- **Squint test**: primary, secondary, and groupings identifiable with blurred vision?
+- **Rhythm**: a satisfying beat of tight and generous spacing?
+- **Hierarchy**: the most important content obvious within 2 seconds?
+- **Breathing room**: comfortable, not cramped or wasteful?
+- **Consistency**: the spacing system applied uniformly, no off-scale values?
+- **Responsiveness**: graceful at 320 / 375 / 414 / 768 px, floors above all green?
+
+A clean mechanical pass is a floor, not a verdict: a monotone grid with uniform spacing passes every lint rule, which is exactly what the squint test exists to catch.

package/departments/landing/skills/page-architect/references/macrostructures/01-bento-grid.md

@@ -0,0 +1,37 @@
+## 01 · Bento Grid
+
+> Derived from [hallmark](https://github.com/nutlope/hallmark) (MIT — see `hallmark.LICENSE` in this references directory). Sanitized and adapted for ArkaOS.
+
+Modular blocks of varying sizes laid out as an irregular grid. Each block is a feature, a quote, an image, a stat. Visual rhythm comes from size variation, not card uniformity.
+
+- **Heading:** centered display in a fixed-height hero (not full viewport).
+- **Body:** asymmetric grid — 8–15 blocks of mixed spans (1×1, 2×1, 1×2, 2×2).
+- **Divider:** consistent 12–24 px gap; no rules; the grid itself is the rhythm.
+- **Button:** outlined chip on the hero; tile-internal CTAs as typographic links.
+- **Image:** tightly cropped inside individual blocks; never full-bleed.
+- **Reveal:** none, or a subtle one-shot fade on grid-tile entry.
+
+Reach for it when the brief is "many small things to show", a feature page, a SaaS landing, or anywhere users have multiple equally-valid entry points.
+
+Avoid when the message is a single hero idea — Bento spreads attention; one-idea pages need Marquee or Stat-Led.
+
+Reference: Apple in-page sections, Framer feature pages, Tailwind UI templates.
+
+**Sample opening lines** (imitate the *specificity*, not the wording):
+> *"Tracejam · v0.4 · for SREs. Distributed tracing that explains itself."* — paraphrased from real observability tools
+> *"Resend is the email API for developers. Send transactional and marketing emails at scale."* — resend.com
+> *"The product development system for teams and agents."* — linear.app
+
+```html
+<header class="hero-fixed">…</header>
+<section class="bento">
+  <article class="cell span-2x2">…</article>  <!-- hero feature -->
+  <article class="cell span-1x1">…</article>
+  <article class="cell span-2x1">…</article>  <!-- wide stat -->
+  <article class="cell span-1x2">…</article>  <!-- tall image -->
+  <article class="cell span-1x1">…</article>
+  <article class="cell span-1x1">…</article>
+</section>
+```
+
+---

package/departments/landing/skills/page-architect/references/macrostructures/02-long-document.md

@@ -0,0 +1,36 @@
+## 02 · Long Document
+
+> Derived from [hallmark](https://github.com/nutlope/hallmark) (MIT — see `hallmark.LICENSE` in this references directory). Sanitized and adapted for ArkaOS.
+
+Reads like a memo, a letter, or a journal entry. No marketing structure. Continuous prose with inline section heads. The page is *literature* about the product.
+
+- **Heading:** inline with body — section heads emerge from the paragraph flow as small caps or bold short phrases.
+- **Body:** single column, generous line-height (1.65+), measure 60–65ch.
+- **Divider:** negative space; the gap is the divider; occasionally a centered ornament for emphasis.
+- **Button:** typographic link inside a paragraph, not a separate block.
+- **Image:** inline, sized to text measure; never full-bleed.
+- **Reveal:** none. The page is just *there*.
+
+Reach for it for case studies, founder posts, mission pages, products whose sale is *philosophical*. The brief is "tell a story", not "list features".
+
+Avoid when there's a single decisive action to take — Long Document hides CTAs, which is wrong for transactional pages.
+
+Reference: Frank Chimero's site, destroytoday.com, long-form Substack essays in product disguise.
+
+**Sample opening lines** (imitate the *specificity*, not the wording):
+> *"Saturday, 6:14 a.m. The dough went in at midnight."* — opens with a time-stamp; the brand introduces itself as a moment in the day
+> *"A monthly art publication featuring contributions by some of the most engaged thinkers working today."* — e-flux.com/journal
+> *"We design everything for everyone."* — pentagram.com — refusal of the verb, treats design as universal practice
+
+```html
+<article class="prose">
+  <p class="lede">…</p>
+  <p>…</p>
+  <h2 class="inline">A small heading.</h2>
+  <p>…</p>
+  <blockquote>…</blockquote>
+  <p>… <a href="">read more →</a> …</p>
+</article>
+```
+
+---

package/departments/landing/skills/page-architect/references/macrostructures/03-marquee-hero.md

@@ -0,0 +1,33 @@
+## 03 · Marquee Hero
+
+> Derived from [hallmark](https://github.com/nutlope/hallmark) (MIT — see `hallmark.LICENSE` in this references directory). Sanitized and adapted for ArkaOS.
+
+The hero IS the page above the fold. A single bold statement or visual fills the viewport. No subhead, no CTA in fold. Below the fold the page becomes something else (a list, a grid, prose).
+
+- **Heading:** display fills the fold — 8–14 vw type, hugging the viewport edges.
+- **Body:** below-fold becomes a list of work or a single content block; the hero doesn't continue.
+- **Divider:** a thick rule between hero and below-fold, OR a hard colour change.
+- **Button:** none in fold; first CTA arrives below.
+- **Image:** none in fold (typography is the visual), OR a single full-bleed photograph as the fold *background*.
+- **Reveal:** the fold is static; below-fold may sweep in horizontally.
+
+Reach for it when the brand or person *is* the message — designer/director portfolios, indie products with a single declarative voice, any "this is who we are" page.
+
+Avoid for products whose value requires explanation in seconds. Marquee makes the user scroll before they understand.
+
+Reference: 14islands.com, destroytoday.com, many design studio homepages.
+
+**Sample opening lines** (imitate the *specificity*, not the wording):
+> *"Type, set with care."* — the Specimen theme — refusal of the verb, treats type as material
+> *"A studio for what's next."* — italic editorial display, names the practice without explaining it
+> *"Design like print: warm, off-register, intentional."* — the Riso theme — declarative, three modifiers, full stop
+
+```html
+<section class="marquee">
+  <h1 class="display-xxl">A statement.</h1>
+</section>
+<hr class="rule-thick" />
+<section class="below-fold">…</section>
+```
+
+---

package/departments/landing/skills/page-architect/references/macrostructures/04-stat-led.md

@@ -0,0 +1,36 @@
+## 04 · Stat-Led
+
+> Derived from [hallmark](https://github.com/nutlope/hallmark) (MIT — see `hallmark.LICENSE` in this references directory). Sanitized and adapted for ArkaOS.
+
+The hero is a giant number — a metric, a count, a percentage. Everything that follows supports or qualifies it. Data is the narrative.
+
+- **Heading:** a large numeric display (8–12 rem, tabular figures) **paired with a worded headline** — the figure is the biggest element, but it is *never the hero's only words*. State what the number means right beside or beneath it as a real headline, not a tiny label. Read the figure and its words together (*"4 seconds. From the alert link to the slow span."*).
+- **Body:** sections each anchored by a supporting stat or chart.
+- **Divider:** hairline rules between stat blocks; tabular-nums everywhere.
+- **Button:** outlined chip aligned beneath the qualifier.
+- **Image:** charts and small data-viz; no photography.
+- **Reveal:** number-tick on the hero figure — counter from 0 to target over ~500 ms.
+
+Reach for it when the brief is "we have proof in numbers" — enterprise/B2B, fundraising platforms, climate or impact pages.
+
+Avoid for products without a defensible single metric. A fake big number is worse than no number.
+
+**The hero header always contains words.** The lead figure never stands alone as the headline — pair it with a worded line that completes it. A bare number as the dominant hero text fails slop-test gate 46.
+
+Reference: Ahrefs, Stripe Sessions stat blocks, climate-impact dashboards, venture firm portfolio pages.
+
+**Sample opening lines** (imitate the *specificity*, not the wording — the number does the work):
+> *"+47% · faster · decide late."* — italicised number, three-word qualifier
+> *"4 seconds. From the alert link to the slow span."* — pairs the number with what it bought
+> *"434 total posts. New CSS you feel like you could use today."* — adam argyle, nerdy.dev — the count grounds the page in real volume
+
+```html
+<section class="stat-hero">
+  <div class="figure tnum">99.97<span class="unit">%</span></div>
+  <p class="qualifier">uptime across 2026, measured externally.</p>
+  <a class="cta-outline">Read the report →</a>
+</section>
+<section class="supporting-stats">…</section>
+```
+
+---

package/departments/landing/skills/page-architect/references/macrostructures/05-workbench.md

@@ -0,0 +1,34 @@
+## 05 · Workbench
+
+> Derived from [hallmark](https://github.com/nutlope/hallmark) (MIT — see `hallmark.LICENSE` in this references directory). Sanitized and adapted for ArkaOS.
+
+Product screenshots in frames are the primary content. The page is a guided tour of the app in use. Less marketing copy, more "here's what you do with it."
+
+- **Heading:** small, functional — workbench pages don't shout.
+- **Body:** sequence of screenshot blocks, each with a short caption and an inline annotation arrow.
+- **Divider:** the screenshot frame *is* the divider; sections separate by gap and frame.
+- **Button:** sticky-bottom CTA bar after the third screenshot ("Try it →"), once context is built.
+- **Image:** central — browser/device frames around real product captures, with annotation arrows.
+- **Reveal:** type-unmask on captions; screenshots load instantly.
+
+Reach for it for SaaS, developer tools, IDE extensions — anywhere seeing the product in motion is the sale.
+
+Avoid when the product is conceptual or services-led. Workbench needs a UI to show.
+
+Reference: Linear.app, Vercel, Raycast, Arc Browser.
+
+**Sample opening lines** (imitate the *specificity*, not the wording — the page walks the user through):
+> *"$ streampipe parse access.log --filter status=5xx | jq"* — open on a real command, not a marketing claim
+> *"Read anything that emits lines. Files, pipes, sockets, kubectl logs."* — names the inputs, refuses abstraction
+> *"Open the trace, find the span, fix the regression. No glossary required."* — three concrete verbs, then a refusal
+
+```html
+<header class="lite">…</header>
+<section class="screenshot-frame">
+  <figure><img src="step-1.png" /><figcaption>Open a project.</figcaption></figure>
+</section>
+<section class="screenshot-frame">…</section>
+<aside class="sticky-cta">Try it free →</aside>
+```
+
+---

package/departments/landing/skills/page-architect/references/macrostructures/06-conversational-faq.md

@@ -0,0 +1,35 @@
+## 06 · Conversational FAQ
+
+> Derived from [hallmark](https://github.com/nutlope/hallmark) (MIT — see `hallmark.LICENSE` in this references directory). Sanitized and adapted for ArkaOS.
+
+Bold questions, brief answers. The page reads like an honest interview with the product. Often each Q/A is a collapsible accordion.
+
+- **Heading:** each section *is* a question — a short, direct phrase ending in `?`.
+- **Body:** answer in 2–4 short paragraphs immediately below the question.
+- **Divider:** thin rule between Q/A pairs, or zero rule and a paper-colour swap.
+- **Button:** typographic link inside answers ("Read the full policy →"); one outlined CTA at the foot.
+- **Image:** sparse — maybe one diagram per long answer; mostly text.
+- **Reveal:** none on load; accordion expand uses 200 ms `--ease-out` on `grid-template-rows: 0fr → 1fr`.
+
+Reach for it near pricing, for products that meet skepticism, for educational/regulated industries.
+
+Avoid as the *primary* page. FAQ usually pairs with another macrostructure that opens the page.
+
+Reference: many SaaS pricing pages, Casper, Substack help pages.
+
+**Sample opening lines** (imitate the *specificity* — questions are real questions, answers are short and concrete):
+> *"What is this for? — A single-binary CLI for parsing log streams from stdin."* — names the form factor, names the input
+> *"How is this different from X? — It's about time."* — cron.com — answers obliquely, with a phrase that has weight
+> *"Who built this? — Three of us, in Lisbon, since 2014."* — date + place + count, no marketing
+
+```html
+<section class="faq">
+  <details>
+    <summary><h2>How long does setup take?</h2></summary>
+    <div class="answer">…</div>
+  </details>
+  <details>…</details>
+</section>
+```
+
+---