@krigsvold/theme 2.0.0 → 2.2.0

package/dist/layout.json

@@ -0,0 +1,60 @@
+{
+  "schemaVersion": 1,
+  "primitives": [
+    "container",
+    "stack",
+    "cluster",
+    "grid",
+    "sidebar",
+    "split"
+  ],
+  "compositions": [
+    "article",
+    "landing",
+    "documentation"
+  ],
+  "defaults": {
+    "space": "regular",
+    "columns": 3,
+    "splitRatio": "equal",
+    "sidebarSide": "end"
+  },
+  "tokens": {
+    "layout-gap": "2rem",
+    "layout-gap-small": "1rem",
+    "layout-gap-large": "3rem",
+    "layout-sidebar-width": "20rem",
+    "layout-main-min": "30rem",
+    "layout-grid-min": "20rem",
+    "layout-split-min": "22rem",
+    "layout-section-space": "clamp(4.5rem, 8vw, 7.5rem)"
+  },
+  "sources": [
+    {
+      "url": "https://krigsvold.org/",
+      "repository": "basuhoward/krigsvold.org",
+      "commit": "a3cf072c516c59ed35814e0fa153028cc91ceecd",
+      "files": [
+        "src/layouts/Page.astro",
+        "src/components/HomeContent.astro",
+        "src/components/HomeHero.astro",
+        "src/styles/site.css"
+      ]
+    },
+    {
+      "url": "https://krigsvoldtheme.dev/",
+      "repository": "krigsvoldtheme/krigsvoldtheme",
+      "commit": "880bdd2bd8430bbdfd8d728faaae0c21199540b1",
+      "files": [
+        "site/src/pages/index.astro",
+        "site/src/styles/global.css",
+        "site/src/components/FoundationSpecimen.astro"
+      ]
+    }
+  ],
+  "normalization": {
+    "intrinsicSizing": "Columns and sidebars respond to their available container width, including nested containers, rather than only to viewport breakpoints.",
+    "readingOrder": "Sidebar side selects matching DOM order; split content retains its source order at all widths.",
+    "scope": "Namespaced optional layout classes; no global reset, framework dependency, image, personal identity, or scripts."
+  }
+}

package/dist/legacy.css

@@ -72,6 +72,14 @@
   --breakpoint-lg: var(--krigsvold-breakpoint-lg);
   --breakpoint-xl: var(--krigsvold-breakpoint-xl);
   --breakpoint-xxl: var(--krigsvold-breakpoint-xxl);
+  --layout-gap: var(--krigsvold-layout-gap);
+  --layout-gap-small: var(--krigsvold-layout-gap-small);
+  --layout-gap-large: var(--krigsvold-layout-gap-large);
+  --layout-sidebar-width: var(--krigsvold-layout-sidebar-width);
+  --layout-main-min: var(--krigsvold-layout-main-min);
+  --layout-grid-min: var(--krigsvold-layout-grid-min);
+  --layout-split-min: var(--krigsvold-layout-split-min);
+  --layout-section-space: var(--krigsvold-layout-section-space);
   --navy-950: var(--krigsvold-color-navy-950);
   --navy-900: var(--krigsvold-color-navy-900);
   --navy-800: var(--krigsvold-color-navy-800);

package/dist/light.json

@@ -1,5 +1,5 @@
 {
-  "version": "2.0.0",
+  "version": "2.2.0",
   "id": "krigsvold-light",
   "name": "Krigsvold Light",
   "mode": "light",

package/dist/patterns.css

@@ -0,0 +1,47 @@
+/* Additive pattern anatomy. Existing classes and default layouts are unchanged. */
+.krigsvold-reading-context { container:krigsvold-reading / inline-size; }
+.krigsvold-reading-layout { display:grid; gap:2.5rem; align-items:start; }
+.krigsvold-reading-layout > * { min-inline-size:0; max-inline-size:100%; }
+.krigsvold-contents { min-inline-size:0; max-inline-size:100%; padding:1.2rem 1.4rem; font:1rem/1.5 var(--krigsvold-font-sans); color:var(--krigsvold-source-ink,var(--krigsvold-text)); background:var(--krigsvold-source-support,var(--krigsvold-panel)); overflow-wrap:anywhere; }
+.krigsvold-contents__label { margin:0 0 .5rem; font-weight:700; }
+.krigsvold-contents ul { list-style:none; padding:0; margin:0; }
+.krigsvold-contents > ul > li { margin-block:.5rem 1rem; break-inside:avoid; }
+.krigsvold-contents a { display:block; padding-block:.35rem; text-decoration:none; }
+.krigsvold-contents a:hover { text-decoration:underline; }
+.krigsvold-contents > ul > li > a { font-weight:700; }
+.krigsvold-contents li ul { padding-inline-start:.85rem; }
+.krigsvold-contents li li { margin-block:.25rem; }
+.krigsvold-contents--inline > ul { columns:2 16rem; column-gap:2rem; }
+@container krigsvold-reading (min-width:74rem) {
+ .krigsvold-reading-layout { grid-template-columns:20rem minmax(0,760px); gap:clamp(2rem,4cqi,5rem); justify-content:center; }
+ .krigsvold-reading-layout__contents { position:sticky; top:6rem; max-block-size:calc(100vh - 7rem); overflow:auto; }
+ .krigsvold-reading-layout .krigsvold-contents--index { background:transparent; padding:1.25rem 0 0; }
+}
+@media (orientation:portrait) { .krigsvold-reading-layout { grid-template-columns:minmax(0,1fr); } .krigsvold-reading-layout__contents { position:static; max-block-size:none; overflow:visible; } }
+.krigsvold-site-footer--grouped { background:var(--krigsvold-color-navy-950); color:rgba(255,255,255,.72); font:1rem/1.65 var(--krigsvold-font-sans); border:0; padding-block:5rem 1.5rem; }
+.krigsvold-site-footer--grouped a { color:inherit; text-decoration:none; padding-block:0; }
+.krigsvold-site-footer--grouped a:hover { color:white; text-decoration:underline; }
+.krigsvold-site-footer__groups { display:grid; grid-template-columns:repeat(4,minmax(0,1fr)); gap:3rem; }
+.krigsvold-site-footer__groups > *, .krigsvold-site-footer__identity, .krigsvold-site-footer__base > * { min-inline-size:0; }
+.krigsvold-site-footer__group h2 { font-family:var(--krigsvold-font-sans); color:white; margin:0 0 1rem; font-size:.76rem; font-weight:700; letter-spacing:.12em; text-transform:uppercase; }
+.krigsvold-site-footer__group ul { list-style:none; padding:0; margin:0; }
+.krigsvold-site-footer__group li { margin-block:.45rem; }
+.krigsvold-site-footer__base { display:flex; justify-content:space-between; align-items:center; flex-wrap:wrap; gap:1rem 2rem; margin-block-start:2.5rem; padding-block-start:1.5rem; border-block-start:1px solid rgba(255,255,255,.16); font-size:.82rem; }
+.krigsvold-site-footer__identity :where(img,svg) { max-inline-size:100%; block-size:auto; }
+.krigsvold-site-footer--grouped :where(:focus-visible) { outline:3px solid white; outline-offset:3px; }
+.krigsvold-site-footer__top { display:grid; grid-template-columns:repeat(6,minmax(0,1fr)); gap:3rem; }
+.krigsvold-site-footer__identity { grid-column:span 2; }
+.krigsvold-site-footer__groups { grid-column:span 4; }
+.krigsvold-site-footer__group a { font-size:.88rem; font-weight:500; }
+.krigsvold-site-footer--grouped > .krigsvold-container { inline-size:100%; padding-inline:12px; }
+@media(min-width:576px) { .krigsvold-site-footer--grouped > .krigsvold-container { max-inline-size:540px; } }
+@media(min-width:768px) { .krigsvold-site-footer--grouped > .krigsvold-container { max-inline-size:720px; } }
+@media(min-width:992px) { .krigsvold-site-footer--grouped > .krigsvold-container { max-inline-size:960px; } }
+@media(min-width:1200px) { .krigsvold-site-footer--grouped > .krigsvold-container { max-inline-size:1140px; } }
+@media(min-width:1400px) { .krigsvold-site-footer--grouped > .krigsvold-container { max-inline-size:1320px; } }
+@media(max-width:991.98px) { .krigsvold-site-footer__top { display:block; } .krigsvold-site-footer__identity { margin-block-end:2.5rem; } }
+@media(max-width:767.98px) { .krigsvold-site-footer__groups { grid-template-columns:repeat(2,minmax(0,1fr)); gap:2rem; } }
+@media(max-width:359px) { .krigsvold-site-footer__groups { grid-template-columns:minmax(0,1fr); } }
+@media print { .krigsvold-reading-layout { display:block; } .krigsvold-reading-layout__contents { position:static; max-block-size:none; overflow:visible; margin-block-end:2rem; } }
+
+.krigsvold-site-footer__top:not(:has(.krigsvold-site-footer__identity)) .krigsvold-site-footer__groups { grid-column:1 / -1; }

package/dist/source-profile.css

@@ -0,0 +1,23 @@
+/* Opt-in source translation. Existing semantic palettes and default primitives are unchanged. */
+.krigsvold-source-profile {
+  --krigsvold-field-gap:.5rem; --krigsvold-group-gap:1.5rem; --krigsvold-region-gap:3rem;
+  color:var(--krigsvold-source-ink,var(--krigsvold-text));
+}
+[data-krigsvold="light"] {
+  --krigsvold-source-ink:var(--krigsvold-color-ink);
+  --krigsvold-source-heading:var(--krigsvold-color-navy-900);
+  --krigsvold-source-support:var(--krigsvold-color-ice-100);
+  --krigsvold-source-label:var(--krigsvold-color-blue-600);
+  --krigsvold-source-button-bg:var(--krigsvold-color-navy-950); --krigsvold-source-button-hover:var(--krigsvold-color-blue-600); --krigsvold-source-button-text:white;
+}
+.krigsvold-source-profile .krigsvold-prose { font-size:var(--krigsvold-text-body); line-height:var(--krigsvold-leading-body); }
+.krigsvold-source-profile :where(h1,h2,h3) { color:var(--krigsvold-source-heading,var(--krigsvold-text-strong)); }
+.krigsvold-source-profile .krigsvold-page-header__copy::after { display:none; }
+.krigsvold-source-profile { font-size:1rem; }
+.krigsvold-source-profile .krigsvold-button:not(:disabled) { background:var(--krigsvold-source-button-bg,var(--krigsvold-accent)); border-color:var(--krigsvold-source-button-bg,var(--krigsvold-accent)); color:var(--krigsvold-source-button-text,var(--krigsvold-on-accent)); }
+.krigsvold-source-profile .krigsvold-button:not(:disabled):hover { background:var(--krigsvold-source-button-hover,var(--krigsvold-accent-hover)); }
+.krigsvold-source-profile .krigsvold-prose :where(blockquote) { border-inline-start:4px solid var(--krigsvold-color-blue-600); padding-inline-start:1.2rem; font-family:var(--krigsvold-font-serif); }
+
+[data-krigsvold="dark"] { --krigsvold-source-ink:var(--krigsvold-text); --krigsvold-source-heading:var(--krigsvold-text-strong); --krigsvold-source-support:var(--krigsvold-panel); --krigsvold-source-label:var(--krigsvold-accent); --krigsvold-source-button-bg:var(--krigsvold-accent); --krigsvold-source-button-hover:var(--krigsvold-accent-hover); --krigsvold-source-button-text:var(--krigsvold-on-accent); }
+
+.krigsvold-source-profile .krigsvold-page-header { background:transparent; color:var(--krigsvold-source-ink,var(--krigsvold-text)); }

package/dist/tokens.json

@@ -1,6 +1,6 @@
 {
   "name": "Krigsvold",
-  "version": "2.0.0",
+  "version": "2.2.0",
   "heritage": {
     "navy950": "#061325",
     "navy900": "#0A1D35",
@@ -146,7 +146,15 @@
       "breakpoint-md": "768px",
       "breakpoint-lg": "992px",
       "breakpoint-xl": "1200px",
-      "breakpoint-xxl": "1400px"
+      "breakpoint-xxl": "1400px",
+      "layout-gap": "2rem",
+      "layout-gap-small": "1rem",
+      "layout-gap-large": "3rem",
+      "layout-sidebar-width": "20rem",
+      "layout-main-min": "30rem",
+      "layout-grid-min": "20rem",
+      "layout-split-min": "22rem",
+      "layout-section-space": "clamp(4.5rem, 8vw, 7.5rem)"
     },
     "typographyRoles": {
       "serif": {
@@ -210,7 +218,8 @@
         "spacing",
         "shape",
         "depth",
-        "interaction variables"
+        "interaction variables",
+        "layout primitives"
       ],
       "optional": [
         "font loading",
@@ -225,7 +234,13 @@
         "container",
         "section heading",
         "card",
-        "button"
+        "button",
+        "page header",
+        "site header",
+        "site footer",
+        "article layout",
+        "landing layout",
+        "documentation layout"
       ],
       "hostOwned": [
         "navigation",
@@ -296,6 +311,66 @@
       ]
     }
   },
+  "layout": {
+    "schemaVersion": 1,
+    "primitives": [
+      "container",
+      "stack",
+      "cluster",
+      "grid",
+      "sidebar",
+      "split"
+    ],
+    "compositions": [
+      "article",
+      "landing",
+      "documentation"
+    ],
+    "defaults": {
+      "space": "regular",
+      "columns": 3,
+      "splitRatio": "equal",
+      "sidebarSide": "end"
+    },
+    "tokens": {
+      "layout-gap": "2rem",
+      "layout-gap-small": "1rem",
+      "layout-gap-large": "3rem",
+      "layout-sidebar-width": "20rem",
+      "layout-main-min": "30rem",
+      "layout-grid-min": "20rem",
+      "layout-split-min": "22rem",
+      "layout-section-space": "clamp(4.5rem, 8vw, 7.5rem)"
+    },
+    "sources": [
+      {
+        "url": "https://krigsvold.org/",
+        "repository": "basuhoward/krigsvold.org",
+        "commit": "a3cf072c516c59ed35814e0fa153028cc91ceecd",
+        "files": [
+          "src/layouts/Page.astro",
+          "src/components/HomeContent.astro",
+          "src/components/HomeHero.astro",
+          "src/styles/site.css"
+        ]
+      },
+      {
+        "url": "https://krigsvoldtheme.dev/",
+        "repository": "krigsvoldtheme/krigsvoldtheme",
+        "commit": "880bdd2bd8430bbdfd8d728faaae0c21199540b1",
+        "files": [
+          "site/src/pages/index.astro",
+          "site/src/styles/global.css",
+          "site/src/components/FoundationSpecimen.astro"
+        ]
+      }
+    ],
+    "normalization": {
+      "intrinsicSizing": "Columns and sidebars respond to their available container width, including nested containers, rather than only to viewport breakpoints.",
+      "readingOrder": "Sidebar side selects matching DOM order; split content retains its source order at all widths.",
+      "scope": "Namespaced optional layout classes; no global reset, framework dependency, image, personal identity, or scripts."
+    }
+  },
   "themes": {
     "light": {
       "id": "krigsvold-light",

package/docs/charter.md

@@ -0,0 +1,57 @@
+# Krigsvold design charter
+
+Version 1.0 · Adopted October 21, 2026
+
+This charter establishes the direction for Krigsvold's development as a complete design system. Its starting observation is agreed: Krigsvold feels icy. The meaning of that character is still developing; the principles below make it specific enough to explore and evaluate. Existing package contracts remain in force; this document introduces no token, API, or compatibility changes and does not imply that the proposed component inventory has shipped.
+
+## Purpose and character
+
+Krigsvold should give digital experiences a sense of clarity, stillness, precision, and space. Its icy character should emerge through crisp typography, deliberate boundaries, aligned regions, and controlled contrast. People should be able to understand the structure of an unfamiliar page and find the information or action they need.
+
+The existing navy, glacier blue, paper surfaces, bronze accents, and Roboto family provide a starting vocabulary. Roboto supports body and interface text; Roboto Slab gives headings a strong presence; Roboto Mono supports code and numerical work. Literal imagery of ice is optional. The character should remain apparent in an ordinary form or table and in both Light and Dark modes.
+
+Krigsvold's originating sites offer useful evidence, but the system should support publishing, services, collections, and interactive applications. A reading experience deserves as much care as a working panel. Adopting projects supply their own identity, content, and organizational purpose.
+
+## Design principles
+
+**Make structure legible.** Establish clear regions for orientation, content, supporting information, and action. Use alignment, typographic hierarchy, boundaries, and contrasting surfaces to explain those regions. A boundary should communicate a meaningful change in purpose, state, or context.
+
+**Give space a defined role.** Separate major regions generously when their purposes differ. Within a working region, spacing should group related information and support efficient comparison. A compact table and an expansive page can belong to the same system. Density must be an explicit choice with readable text and usable controls.
+
+**Use contrast to clarify importance.** Navy, glacier tones, light surfaces, and bronze should establish an understandable hierarchy. Assign color through semantic roles, including status and interaction states. Color is one source of information; labels, shape, position, and other cues must preserve meaning when color distinctions are unavailable.
+
+**Treat precision as assistance.** Labels should identify what information is required. Status should distinguish what has happened, what is happening, and what someone can do next. Errors should explain a useful recovery path and retain entered work where possible. Icy clarity must remain approachable when a person is uncertain or a task fails.
+
+**Keep change controlled.** Transitions should establish a new state or location without competing with the task. Use restrained motion and provide understandable updates when motion is reduced or absent. Stable alignment and persistent context matter during loading, filtering, expansion, and navigation.
+
+## Foundations and component contracts
+
+The specification should cover semantic color, typography, spacing, reading and content widths, responsive composition, density, borders, shape, elevation, layering, and motion. Define the relationships among page regions and the local spacing inside them. Reference scales, semantic tokens, and component dimensions need separate explanations. Numerical values and public names belong in versioned specifications; the charter supplies criteria for their development.
+
+Expand the component inventory through forms, navigation, feedback, disclosure, overlays, data presentation, and complete task patterns. Each supported component needs a purpose, anatomy, applicable states, interaction rules, content guidance, responsive behavior, and accessibility acceptance criteria. Demonstrate combinations such as a filtered collection or a validated form. Distinguish planned, experimental, and stable capabilities.
+
+Accessibility is a condition of acceptance. Review keyboard operation, focus visibility and restoration, labels and announcements, contrast, text enlargement, reflow, forced colors, and reduced motion where applicable. Support long content, localization, and changes in reading direction. Document what works without JavaScript and which interactions require it. Preserve source order and access to information as layouts change.
+
+## Relationship with Martlet
+
+Krigsvold and Martlet share blue, white, gold, order, and restraint. Their different emotional temperatures emerged through their development. Krigsvold's charter should describe its own character; each design decision does not need an opposing Martlet decision. Sound usability and accessibility can produce identical answers in both families.
+
+Share interaction contracts, accessibility work, tests, and tooling where practical. Keep independent judgments about typography, spatial organization, surfaces, and visual emphasis. Krigsvold's icy character needs to be recognizable beyond its palette or a distinctive hero. Neither family is restricted to institutional or editorial work.
+
+## Living baselines
+
+[krigsvold.org](https://krigsvold.org/) is the starting ground truth for Krigsvold and remains a live baseline throughout the system's development. Its real content, tasks, and ongoing use provide evidence for design decisions. The baseline describes what works today and can evolve as generalization exposes better solutions.
+
+An inherited decision that fails when generalized should be removed or revised. Establish a working replacement against both the originating site's real usage and the broader conditions that exposed the failure. Historical fidelity does not justify retaining a design that no longer works.
+
+Carry the validated improvement into the packages and specifications, then back into the originating website. Verify the revised site in use so it becomes the next live baseline. Record the failure, the replacement, and the reasons for the change, and follow the release and migration requirements of affected contracts.
+
+This feedback loop continues throughout development: observe real use, generalize, test, replace what fails, and improve the baseline. Controlled examples and automated checks support that work; they cannot establish real-world fitness on their own.
+
+## Evidence and review
+
+The next milestone is four comparative experiences: an article with supporting material, a substantial form, a searchable collection, and an application dashboard. Ground these comparisons in real content and tasks, and give both families the same content and functionality. Continue evaluating changes against the live baseline while exploring contexts beyond it. With brand marks removed, review whether Krigsvold's structure, rhythm, and emphasis still convey its character. Check that generous regional spacing and any compact local density remain useful at narrow widths and with enlarged text.
+
+The live sites should exercise the system as consumers. Move reusable decisions into the packages and specifications while keeping site identity, navigation, routing, content, analytics, and consent policy with the host. Examples embedded in a site should use its shared page shell. Standalone starters should make their purpose clear.
+
+Maintainers should document the reasons for consequential changes and identify provisional decisions. Review proposals against the charter, demonstrated user needs, and compatibility obligations. Version and deprecate stable contracts deliberately. The charter can change as practical use gives greater precision to the meaning of icy clarity.

package/docs/consolidation.md

@@ -0,0 +1,29 @@
+# Krigsvold consolidation
+
+Core 2.2.0 and Astro 1.2.0 are **experimental release candidates**. Existing theme colors, typography defaults, component defaults, and Astro slots are retained. Do not install an unpublished version from npm. Use the paired review branches or packed archives to evaluate this change.
+
+The core owns [grammar](grammar.md), [source decisions](source-decisions.md), [foundation requirements](foundations.md), `language.json`, and framework-independent pattern CSS. Astro owns rendering and slots. React owns its events, controlled state and focus APIs. Documentation and agent references must identify the exact guidance revision. Publication does not establish grammar stability.
+
+## Opt into source roles
+
+Import `@krigsvold/theme/source-profile.css` after the regular core styles. Apply `krigsvold-source-profile` to an existing `.krigsvold` container (or pass it through Astro `bodyClass`) within `data-krigsvold="light"` or `"dark"`. This restores audited reading roles and removes the unsupported page-header accent in that scope. New field/group/region relationships remain experimental. Nested opposite appearances must start their own source-profile scope.
+
+`full.css` includes additive `patterns.css`; color-only imports still load no pattern styling. Existing palette JSON is unchanged apart from version metadata. No personal identity, analytics, legal policy, imagery, automatic global stripe, or navigation orientation is imposed.
+
+## Content and footer anatomy
+
+Use TableOfContents with `items` containing `href`, `label`, and optional `depth: 2 | 3`; the default depth is 2. A depth-3 item requires a preceding depth-2 parent. Native nested lists retain parent/child semantics. `variant="index"` belongs in ArticleLayout's `contents` slot. `variant="inline"` is an in-body alternative. Localize `label` explicitly.
+
+ArticleLayout retains its existing `sidebar` slot and end-side supporting region. Its new `contents` slot precedes the body; supporting material still follows the body. DocumentationLayout's existing `navigation` slot is unchanged. A TOC does not make every page require a left rail.
+
+SiteFooter defaults to the existing plain rendering. `variant="grouped"` accepts `groups: {label, links: {href, label}[]}[]`, plus `identity` and `base` slots. Existing `links`, `navigationLabel`, class and default slot remain supported in either variant. The host supplies its own mark, ownership, contact, translated group names and destinations. Krigsvold uses a wide identity column plus four groups and an independent base row; fewer or more groups wrap within that region.
+
+## Navigation and interaction boundaries
+
+Both languages permit top, side and focused frames. Astro SiteHeader remains a wrapping link header; no dropdown, menu controller or React state API is claimed. The source desktop dropdown is white even on a dark parent; below 992px it becomes transparent and in-flow. This is guidance for a host-owned menu, not a new Astro dropdown component.
+
+Preserve native semantics, focus visibility, retained input, actionable validation, save retry, draft protection and undo where appropriate. These behavioral obligations cross frameworks; their React implementations do not become Astro props. Full dark mode and new app controls remain extensions. Figure, footnote, maths, archive/card variants and richer data workflows remain gaps.
+
+## Experimental distribution
+
+The GitHub pre-release publishes the verified package under npm’s `next` dist-tag. The existing `latest` tag stays unchanged. An experimental publication does not establish grammar stability or manual assistive-technology conformance. Promote a release only through a separate reviewed release decision.

package/docs/coverage.md

@@ -0,0 +1,40 @@
+# Krigsvold grammar coverage review
+
+Review 0.3 · October 24, 2026 · Experimental
+
+The baseline grammar described intent and an experimental collection/editor. This review adds decision rules for grouping, density, action scope, layers, validated forms and queried results. Existing origin objects remain authoritative. New application patterns are justified extensions and are not retrospectively attributed to the origin site.
+
+| ID | Domain | Disposition | Rule or remaining work | Evidence surface |
+| --- | --- | --- | --- | --- |
+| G01 | Source authority | Documented | Origin objects, translations and extensions remain distinct. | Source audit and source-decisions.md |
+| G02 | Field / group / region spacing | Rule clarified + reference | Use relational roles; do not inherit page-section spacing inside forms. | Validated-form reference |
+| G03 | Density and targets | Claim corrected; compact open | Comfortable examples only; 44px is a design target, not blanket certification. | Foundations; target-size checks |
+| G04 | Typography and hierarchy | Observed roles retained | Keep prose, UI, selective display and code roles; no decorative monospace. | Source decisions; existing React/Astro checks |
+| G05 | Surfaces and layers | Rule corrected + reference | Modal, popup and inline disclosure have different interaction contracts. | Native dialog in form/results |
+| G06 | Action placement and scope | Rule clarified + reference | Commands name and follow their field, object or collection scope. | Validated-form and results references |
+| G07 | Responsive composition | Reference checks | Reflow fields/actions; scroll only genuine comparison surfaces; retain source order. | Narrow/enlarged-text browser checks |
+| G08 | Substantial forms | New experimental contract | Validate, retain values, retry and guard specimen reset. | docs/patterns/forms.md |
+| G09 | Query / sort / page | New experimental contract | Draft query differs from applied results; changed query starts page 1. | docs/patterns/query-results.md |
+| G10 | Selection | New bounded contract | Binary current-page selection; scope changes reset on commit, failure retains it. | Results reference; no mixed/select-all API |
+| G11 | Pending / failed / empty states | Reference coverage expanded | Keep useful previous content and distinguish no matches from empty source data. | Form/results/collection specimens |
+| G12 | Focus and recovery | Reference checks; manual open | Summary links, modal dismissal, return trigger and late-response cancellation. | Browser assertions; manual AT still open |
+| G13 | Top / side / focused frames | Existing support retained | Frame follows task; source navigation direction is not a family restriction. | AppShell and existing browser checks |
+| G14 | Reading / contents / footer | Existing source contracts retained | Contents, body, support and host identity remain separate. | Astro candidate and source audit |
+| G15 | Cross-framework agreement | Availability clarified | Rules cross frameworks; React state/focus props do not become Astro APIs. | language.json; native-HTML guidance |
+| G16 | Figure / footnote / maths / archive vocabulary | Open | Do not infer shipped components from origin CSS. | Source decisions; no new API claim |
+| G17 | Localization / RTL / assistive technology | Open | Long-text checks are partial evidence; no manual or locale certification. | Consumer and manual review required |
+| G18 | Sustained use / dashboard breadth | Open | Focused references do not establish production fitness or cover all application patterns. | Future consumer evidence |
+
+## Acceptance and limits
+
+Each pattern contract names its purpose, anatomy, scope, states, keyboard/focus behavior, responsive behavior and implementation availability. Automated results are recorded separately from documented requirements. A rule is not stable merely because a specimen passes. New form and results specimens use deterministic session state and simulated latency/failure. They do not add a new application or change the collection/editor into a production service.
+
+The foundations no longer claim that every React target is 44 pixels, no longer require a backdrop for all overlays, and now acknowledge the optional core source-profile aliases. Modal focus behavior, native read-only/disabled distinctions, selection scope and draft-versus-applied query are explicit. Compatibility remains additive; existing package defaults and APIs are retained.
+
+## Framework boundaries
+
+Core owns grammar, semantic roles and source profiles. React supplies interactive specimens using existing exports. Astro retains its documented component inventory and can use the same native HTML semantics; host scripts own form/query controllers. The main reference and agent snapshots identify this exact canonical revision. No framework receives an implementation claim from shared prose alone.
+
+## Reference method
+
+The source audit, adopted charter and actual exported APIs govern these decisions. Carbon's [form](https://www.carbondesignsystem.com/building-blocks/core/patterns/forms), [loading](https://www.carbondesignsystem.com/building-blocks/core/patterns/loading) and [filtering](https://www.carbondesignsystem.com/building-blocks/core/patterns/filtering) guidance informed the breadth of questions, not either language's palette or composition. Our search controls retain visible labels under our own grammar. Target sizing follows the distinctions in [W3C SC 2.5.8](https://www.w3.org/WAI/WCAG22/Understanding/target-size-minimum.html), without treating automated checks as overall WCAG certification.

package/docs/foundations.md

@@ -0,0 +1,108 @@
+# Krigsvold foundations specification
+
+Version 0.1 · Working specification · October 21, 2026
+
+The [adopted charter](charter.md) governs this specification. The values below describe the shipped `@krigsvold/theme` 2.1.0 foundation and layout contracts. Normative requirements describe what new components must satisfy; they do not certify existing components. Application-specific experiments must remain identifiable until real usage validates them.
+
+## Character and hierarchy
+
+Krigsvold makes substantial work feel clear and composed. Roboto supports continuous interface work; Roboto Slab establishes strong headings. Use aligned regions, precise rules, explicit metadata, restrained ice surfaces, and space between tasks. Precision must never become terse or hostile error copy.
+
+A page identifies its purpose, then its primary task, then supporting information. Use one main landmark and a descriptive h1. Related controls form a group with a visible heading or legend. Put explanations close to the decisions they explain. Do not communicate hierarchy, selection, validation, or maturity through color alone.
+
+## Shipped measurements
+
+All CSS properties carry the `--krigsvold-` prefix. Numbers in spacing token names are family-local identifiers, not interchangeable units. In particular, `space-3` differs between Martlet and Krigsvold. Cross-family components use semantic relationships and family adapters rather than copying numeric token names.
+
+| Token | Shipped value |
+| --- | --- |
+| `space-1` | `.25rem` |
+| `space-2` | `.5rem` |
+| `space-3` | `.75rem` |
+| `space-4` | `1rem` |
+| `space-6` | `1.5rem` |
+| `space-8` | `2rem` |
+| `space-12` | `3rem` |
+| `space-16` | `4rem` |
+| `space-24` | `6rem` |
+| `reading-width` | `760px` |
+| `content-width` | `1320px` |
+| `archive-width` | `1320px` |
+| `radius-control` | `.15rem` |
+| `radius-card` | `0` |
+| `motion-duration` | `.15s` |
+| `text-body` | `1.06rem` |
+| `text-h1` | `clamp(2.8rem, 6vw, 5.5rem)` |
+| `text-h2` | `2.1rem` |
+| `text-h3` | `1.42rem` |
+| `text-display` | `clamp(3.4rem, 7vw, 6.8rem)` |
+| `text-section` | `clamp(2rem, 4vw, 3.5rem)` |
+| `leading-body` | `1.65` |
+| `leading-heading` | `1.13` |
+| `leading-display` | `.98` |
+| `focus-width` | `3px` |
+| `focus-gap` | `3px` |
+| `gutter` | `.75rem` |
+| `control-height` | `2.75rem` |
+| `control-padding` | `.9rem` |
+| `button-padding` | `.625rem 1.5rem` |
+| `text-button` | `.75rem` |
+| `leading-button` | `1.667` |
+| `layout-gap` | `2rem` |
+| `layout-gap-small` | `1rem` |
+| `layout-gap-large` | `3rem` |
+| `layout-sidebar-width` | `20rem` |
+| `layout-main-min` | `30rem` |
+| `layout-grid-min` | `20rem` |
+| `layout-split-min` | `22rem` |
+| `layout-section-space` | `clamp(4.5rem, 8vw, 7.5rem)` |
+
+The complete [foundation JSON](../dist/foundation.json) and [layout contract](../dist/layout.json) remain the machine-readable sources for shipped values. Typography roles are Cambo/Lato/Cinzel/IBM Plex Mono for Martlet and Roboto/Roboto Slab/Roboto Mono for Krigsvold. A missing font must leave the page readable using the supplied fallback stacks. Font loading must not hide controls or critical instructions.
+
+## Spacing relationships
+
+Use small layout spacing inside a related group, regular spacing between sibling groups, and large spacing between distinct tasks. Public reading pages use the shipped section spacing; an application does not inherit a public hero's vertical padding merely because it has a title. Margins on content must not double the parent's layout gap. A nested layout establishes its own spacing context.
+
+The initial React workbench proposes `field-gap`, `group-gap`, `region-gap`, `page-gutter`, and `row-padding` as application roles. The 2.2.0 candidate also exposes the field/group/region aliases in an opt-in source profile. These assignments remain experimental and do not alter the stable reference scale. Measure the distinction between fields, groups, and regions during real registry work before promoting them. Never compress an interface simply to fit more rows.
+
+## Responsive composition
+
+Containers are bounded by reading, content, or archive measure. Layout primitives wrap according to their content minima: grids use their minimum cell size; sidebar and split regions wrap without changing source order. The smallest viewport must have one coherent reading and focus order. Breakpoints are consequences of content, not device names.
+
+At 320 CSS pixels and at 400% zoom on a 1280-pixel viewport, navigation wraps, forms become one column, and action groups wrap. Long identifiers and translated copy cannot force page-wide overflow. A genuinely two-dimensional table may scroll inside a labelled, keyboard-focusable region. Keep captions, selection controls, and row actions discoverable. Do not remove columns solely to conceal overflow.
+
+## Type and density
+
+Use the documented font roles and unitless line heights. Application fields, tables, and navigation use the sans family. Preserve a clear heading-to-body hierarchy without applying public hero sizes to an editor panel. Text must remain usable at 200% resizing and with user text-spacing overrides. Labels remain visible when a field contains a value.
+
+This specification recognizes comfortable density only. Compact density is proposed and requires a real high-volume task before adoption. New standalone actions should target 44 by 44 CSS pixels where practical. This is a design target, not a measured claim about every existing link or control. Assess WCAG 2.2 target sizing at 24 by 24 CSS pixels or a documented exception; inspect adjacent target spacing and inline/native exceptions in the actual composition. A denser row changes padding and hierarchy, never silently shrinks interaction targets or body text. Existing smaller legacy controls need review rather than retrospective certification.
+
+## Surfaces and layering
+
+Use semantic canvas, subtle, sunken, and overlay colors from the theme. Flat surfaces and rules establish most structure. Shadow tokens exist but do not justify elevating every section. Modal dialog content needs an accessible name, a clear dismissal path and modal background treatment. Non-modal popups and disclosures retain their own interaction contracts; they do not automatically require a backdrop or focus trap.
+
+Proposed application layers are base 0, sticky context 10, and transient non-modal feedback 20. Native modal dialogs use the browser top layer and must not depend on a fabricated large z-index. Sticky regions may not obscure focused controls or error summaries. Avoid sticky layout on small screens unless it remains usable at zoom.
+
+## Motion
+
+Use the shipped duration and easing for brief state changes. Motion communicates a change; it must not delay submitting, saving, navigating, or reading feedback. With `prefers-reduced-motion: reduce`, remove nonessential transitions, smooth scrolling, and decorative animation. Never require animation to understand a saved or failed state. Loading and saving states include text and remain announced without repeated alerts.
+
+## Accessibility and interaction contracts
+
+Target WCAG 2.2 AA. Verify normal text contrast of 4.5:1, large text 3:1, and essential control boundaries and focus indicators 3:1 against adjacent colors. Measure actual combinations in both light and dark modes. Tokens alone cannot certify a composition. Retain a visible focus ring, logical keyboard order, a skip link, native form semantics, and meaningful names.
+
+Validation associates field errors with controls, marks invalid controls, and offers an error summary that can receive focus. Keep entered values after failure. Announce successful saves with a polite status; use an alert for blocking failures. A modal traps focus through native dialog behavior, supports Escape, and returns focus to its trigger. Disabled and read-only are distinct states. Loading, empty, no-match, invalid, unavailable, saving, saved, failed, conflict, and unsaved-navigation states must be explicitly designed.
+
+## Evidence and change control
+
+The live baseline is https://krigsvold.org/. It supplies evidence for publishing and public navigation. The [design workbench](https://github.com/howardjp/design-workbench) supplies an experimental administration consumer. Its existence is not proof of sustained use or complete accessibility. Record the task, observed failure, proposed change, tests, and result in real use. Replace an inherited decision when generalization fails, then update the original site and verify the result there.
+
+Before a foundation becomes stable, document its consumers, browser and assistive-technology coverage, responsive and contrast checks, migration impact, and acceptance criteria. Review same-content article, substantial form, searchable collection, and dashboard experiences across both families. Promote aliases only after evidence; version public changes and publish migrations. The current React packages and workbench remain experimental. The construction plan and registry contract describe the remaining work.
+
+## Source reconciliation and consolidation
+
+The October 23 source audit refines this working specification. Use [source decisions](source-decisions.md) for observed objects, [grammar](grammar.md) for experimental application relationships, and [consolidation](consolidation.md) for opt-in profiles and framework support. The shipped 2.1.0 measurements above are historical baseline values, not proof that all defaults match the observed source cascade. The 2.2.0 candidate adds opt-in relationship aliases without promoting them to stable foundation requirements.
+
+## Coverage review 0.3
+
+The [coverage ledger](coverage.md) records the reviewed domains, corrections, focused form/results contracts and remaining evidence. The new references supply controlled state coverage, not sustained production use. Target-sizing interpretation follows [W3C SC 2.5.8](https://www.w3.org/WAI/WCAG22/Understanding/target-size-minimum.html).

package/docs/grammar.md

@@ -0,0 +1,75 @@
+# Krigsvold: a grammar of clear regions
+
+Experimental grammar 0.3 · Core 2.2.0 candidate · Astro 1.2.0 candidate · React 0.1.0
+
+Krigsvold makes complex work legible through purposeful regions, stable alignment, controlled contrast, and precise state. Its clarity must remain approachable when a person is uncertain or an operation fails. Its adopted charter supplies the criteria for these experimental application rules.
+
+## Source authority and current decisions
+
+Existing origin objects are the baseline. Read the `decisions` MCP reference or the source-decision profile before choosing visual rules. Distinguish observed source roles, a contextual translation, and a new application extension. Do not add a global gold stripe, decorative monospace labels, arbitrary accent rules, or mechanically opposite family layouts. Keep new capabilities only with a stated task purpose. The October 23 audit is a fixed record; the reconciliation ledger records implemented decisions and remaining gaps. This remains an experimental grammar, not a declaration of stability.
+
+## Assign each region a job
+
+Identify orientation, scope, work, supporting information, and commands. Align related information so that a person can compare it without reconstructing the layout. Use a boundary when purpose or context changes; use local proximity inside a working region. A border around every field does not explain the larger structure, and a large empty gap does not automatically make it clear.
+
+The optional source profile exposes `--krigsvold-field-gap`, `--krigsvold-group-gap`, and `--krigsvold-region-gap`. This pattern maps local grouping to the existing 0.5rem scale step, groups to 1.5rem, and distinct regions to the existing 3rem scale step. These experimental application roles explain relationships rather than replacing the foundation's reference scale. Regional space and compact local rows can coexist. Density is a region-level decision; keep readable text, visible focus, and usable targets.
+
+## Make hierarchy exact
+
+Use Roboto for interface and body text, Roboto Slab for heading roles, and Roboto Mono where code or numerical comparison benefits. Establish common edges for related labels, values, and actions. Keep the existing navy, glacier, paper, and bronze vocabulary assigned through semantic roles. Contrast should identify importance and interaction state, not merely alternate decorative sections.
+
+Keep the desktop navigation popup white with ink text and source pointer/elevation, even inside a dark header. Below 992px its source mobile submenu becomes transparent and in-flow. Use other surface changes only to distinguish purpose or depth. A selected result needs a visible non-color cue as well as contrast. Metadata must remain subordinate without becoming illegible. Truncation is appropriate only when the complete information remains available at a predictable destination.
+
+## Make scope visible
+
+Keep commands near the region they affect. Distinguish collection operations from object operations and persistent state from draft state. Show the current scope beside filtering and search. A result-row activation opens its record; a separate Edit action starts modification. Selection does not silently imply a destructive command or an edit.
+
+Use explicit labels for what is pending, completed, unavailable, or failed. Put the recovery action where the failure occurred. Precision is assistance: explain a useful next step rather than displaying only a diagnostic code.
+
+## Keep change controlled
+
+Retain context while results, details, and forms change. Prefer stable region boundaries during loading and filtering; preserve useful previous information when it remains valid. A save's pending state prevents duplicate submission without hiding the work. A failed save keeps the changed data visible and recoverable. Move keyboard focus when a new task surface requires orientation, and announce state changes without unnecessary interruptions.
+
+Before leaving a changed editor, offer an explicit choice and preserve the draft when that choice is cancelled. Use reversible operations and undo where the domain permits. Explain irreversible consequences before commitment. Transitions may clarify state, but the same information must remain understandable without animation.
+
+## Let the frame follow the work
+
+A horizontal navbar, side rail, or focused workspace without primary navigation can each be Krigsvold. Choose based on destination count, frequency, available space, and the task's need for persistent context. Vertical navigation is not a language rule. A reading page deserves the same coherent regional structure as an operations console.
+
+At narrow widths, place regions in a meaningful reading order rather than compressing all of them into unusable columns. Keep the current object identifiable and supply a clear return route. Long labels, enlarged text, and translated content must not depend on fixed-width assumptions.
+
+## Choose a grouping, then a density
+
+Assign orientation, query, work, supporting context and commands distinct jobs. Align comparable information within each job. Use a boundary when scope changes; do not repeat a border around every local relationship. A region can be compact internally while remaining clearly separated from the next region.
+
+Use comfortable density for the current reference patterns. A compact mode remains proposed, with no new public density prop. Adjust related padding locally only while preserving readable text, usable targets, visible labels and the field/group/region hierarchy. Source page section spacing does not belong inside an editor. A source index or footer is an object-specific composition; it does not establish a universal application rail or surface.
+
+## Bind actions to committed scope
+
+Put a field's assistance beside that field, object commands beside the object, and collection commands beside a named collection. A pending query and its previous results are different scopes: identify both. Retain input and useful results after failure, with a recovery action that names the failed operation. Selection belongs to stable record identities in a declared result scope; clearing, retaining or extending it must follow a documented transition, not an accidental rerender.
+
+The validated-form and query-results contracts add concrete state transitions, focus destinations and narrow-layout rules. They are application extensions. Shared native keyboard conventions do not make the languages interchangeable, and a shared grammar rule does not imply the same framework API. The coverage ledger distinguishes documented rules, checked reference behavior and open consumer evidence.
+
+## Use layers for their actual purpose
+
+An inline disclosure stays in document flow. A non-modal popup anchors to its trigger and retains the source navigation surface. A modal interrupts the task, names its consequence and uses the native dialog top layer with a clear dismissal route. A backdrop belongs to the modal; it is not required for every overlay. Keep focus visible and return it to a meaningful trigger when a temporary surface closes. Motion never carries the only explanation of a state change.
+
+## Working pattern: collection and detail workspace
+
+The Notes workspace specimen puts collection scope and search in a common command region. Results use aligned rows with title, collection, and preview. A clear selected edge identifies the opened record. The detail region remains beside results when width permits, so a person can move through records without losing the collection. Editing is explicit and stays within the detail region. Local working density supports scanning; stronger separation distinguishes the collection from the current note.
+
+When the available width is insufficient, results precede the detail region and opening a note moves focus to its heading. Closing returns focus to the collection heading. The layout changes while scope and task meanings persist.
+
+This pattern does not require every Krigsvold application to use a split view. A sustained-reading task may use a dedicated page. The language's regional, alignment, contrast, and state rules apply in either frame.
+
+## State and recovery rules
+
+Search names its scope and reports the result count. No matches offer a clear reset; an empty collection offers creation. Changing folders is an explicit context change. Opening and editing remain separate actions. Save success returns the note to a committed reading state; failure keeps the editor and offers retry. A context change from a changed editor requires a keep-or-discard choice. Moving a saved note to trash preserves an undo route.
+
+The specimen contains fictional, session-only data. Reload restores initial examples. Its failure-inspection control deliberately fails one save and is separate from ordinary product commands. It does not implement network retrieval, durable storage, collaboration, or rich text.
+
+## Review the grammar
+
+Can someone identify the current region, command scope, selected record, and save state without relying on color? Does aligned information support comparison? Are boundaries meaningful rather than repetitive decoration? Does the regional structure remain understandable in a compact table, a form, and a reading experience? Test these questions across complete transitions, not only the populated initial view.
+
+Expected keyboard behavior and accessible semantics need not differ from Martlet. Independence comes from coherent decisions that serve the task, not arbitrary opposites. Manual assistive-technology review, localization, RTL adaptation, and sustained consumer evidence remain open before stability.