Current releases: Core 3, Astro 3, React 1 and Jekyll 2.
Martlet and Krigsvold have separate experimental language references, existing theme-site marks, proposed application grammars, and working collection/editor patterns. Each includes an independent HTTP/stdio MCP with 66 attributed references and a companion builder skill. Origin reconciliation and grammar coverage 0.3 are implemented; neither grammar is locked. See the 67-item disposition ledger for restored source objects, retained extensions and open vocabulary. The October 23 origin audit records source differences and recommended dispositions, including palette-role, navigation, TOC, typography, spacing and interaction findings. Read the demonstration walkthrough, language brief, reference apps, and agent setup. Software is MIT licensed; original grammar snapshots and the local registry remain experimental. The first task pattern is session-only, and package/endpoint availability is recorded separately in distribution status.
A working component registry for Martlet and Krigsvold, with independent React presentations and one shared data contract. Use it to manage component requirements, target platforms, family decisions, maturity, and usage evidence. MIT licensed, including the application, specifications, and both component packages.
Use Node 24.19 or a later Node 24 release and npm 11.
npm ci --ignore-scripts
npm run build
npm startOpen http://127.0.0.1:4173/martlet/ or http://127.0.0.1:4173/krigsvold/. Both views edit the same database. The default database is var/registry.sqlite; set REGISTRY_DB to choose another path and PORT to choose another loopback port. For development, build once, then run npm run dev and reload after changes. Dev mode deliberately disables HMR. Node's bundled SQLite may print an experimental-feature warning on the supported Node version.
Read and print full saved specifications in the reading room, including both families’ decisions; review coverage and missing evidence in the overview; search, sort, or paginate the inventory; inspect a component, edit its specification, save, and reload. Record six structured readiness observations, review gaps, and renewed outcomes after specification changes. Saving observations does not promote maturity or publish packages. Add components as work expands. Failed writes preserve drafts, stale revisions produce an explicit conflict, and unsaved navigation offers a choice. The initial 38 records reflect the exported Astro and React component inventory, with historical implementation status captured at seed creation; current publication status is recorded in docs/distribution.json. All seed maturity stages remain experimental and evidence starts empty. Seed records are installed once when the database is created; restarting never replaces edits.
This is an experimental, single-user local application. It binds only to 127.0.0.1, rejects unexpected Host/Origin requests, and has no account or authentication model. It is usable for actual registry work now. Public or team hosting requires authentication, authorization, operational backups, persistent storage, and a deployment review. Do not expose the local service through a public tunnel. It is not a production multi-user administration service.
Edits update the local registry and its revision history. Earlier contracts can be reviewed and opened as drafts; saving them appends a new revision. They do not publish packages, alter GitHub, modify either source site, or automatically certify a component. Implementation availability is the checked-in inventory snapshot; user-editable target platforms express intended reach. Stable maturity requires human-reviewed usage and verification evidence; deprecation requires migration guidance. A text field is a record of a decision, not an automated certification.
- @martlet/react: readable hierarchy, related groups, continuity, Cambo/Lato/Cinzel typography.
- @krigsvold/react: purposeful regions, alignment, precise state, Roboto/Roboto Slab typography.
Both export AppShell, Button, TextInput, Select, Textarea, Field, Notice, Badge, DataTable, Dialog, Checkbox, Fieldset, Disclosure, ErrorSummary, Article, TableOfContents, FileInput, Radio, Pagination, DefinitionList, Switch, and Tabs. Their independent npm 1.0.1 releases use matching @martlet/core 3.0.1 / @krigsvold/core 3.0.1 foundations and support light/dark modes. latest resolves to 1.0.1; historical next remains 0.1.0 with theme 2.1.0. The public React component contract is released; original grammar maturity records remain unchanged. The private workbench copies and npm run pack:react are local test fixtures; publication belongs to the independent repositories. Both families support top, side or focused frames according to the task. See current distribution and capability status.
npm run build:docs creates docs-dist/martlet and docs-dist/krigsvold. Each is a complete static documentation app with 22 live specimens, state controls, copyable JSX, source-install guidance and component contracts. Only the selected family's components, styles and fonts enter each build. These outputs contain no local registry service. See the documentation apps and review destinations.
The manual candidate workflow prepares unpublished tarballs and source/hash manifests after verification. It cannot publish to npm. See experimental release preparation.
- Construction plan
- Registry contract and acceptance criteria
- Explicit inventory updates
- Specification reading room
- Reviewed JSON specification import
- Structured readiness reviews
- Martlet foundations specification PR
- Krigsvold foundations specification PR
- Component contracts and states
- Maturity, compatibility, and migration policy
- Martlet charter
- Krigsvold charter
The companion foundations specifications live with each theme package. The original live websites remain publishing baselines; this registry is the emerging administration baseline. Evidence from real use may replace inherited design decisions and must feed back into the source sites.
npm run check
npx playwright install --with-deps chromium
npm run test:browser
npm run pack:reactNode tests cover validation, real SQLite reopen persistence, revision conflicts, creation, immutable availability, export, and HTTP request boundaries. Browser tests exercise both families through the same workflow and check light/dark accessibility and 320/1440-pixel reflow. Automated checks do not replace manual screen-reader, text-spacing, zoom, or sustained-use review. See the review record for the checks actually completed in this change.
Before starting this version against an existing registry, stop the server and copy the complete SQLite database. It upgrades database schema 1 to 2 transactionally without reseeding; older builds refuse schema 2. API/export schema 1 remains unchanged. See the upgrade and review contract.
“Export registry” downloads a schema-versioned JSON snapshot of the latest records. This portable snapshot contains current specifications and availability, without revision history. Import specifications validates a selected schema 1 file and shows exact changes before atomic application. Existing maturity and implementation inventory stay under local control; new contracts start proposed without implementation claims. Stale revisions and name conflicts block the entire import. See the import policy and provenance contract. To preserve the complete database, stop the server, copy var/registry.sqlite to a safe location, then restart. To restore, stop the server and point REGISTRY_DB at the saved database (keep the old one). WAL/SHM sidecars may exist while the server is running; do not copy a live database file alone. The database and exports are never committed to git. Seed changes do not silently migrate existing inventories. Use Inventory updates to preview and explicitly apply bundled additions and implementation metadata, retaining edited specifications and history. See the update contract.
Both views below use the same saved inventory and functionality.
| Martlet | Krigsvold |
|---|---|
![]() |
![]() |
Martlet inventory · Krigsvold inventory
Third-party fonts and dependencies retain their own licenses; see NOTICE.md.
The reading room uses the same saved Button specification in both family compositions:
| Martlet | Krigsvold |
|---|---|
![]() |
![]() |
Reviewed import uses identical source content and exact field changes in both families:
| Martlet | Krigsvold |
|---|---|
![]() |
![]() |
Readiness-review workspace captures use the same unreviewed Button contract and collapsed specification context; the remaining review areas continue below the viewport:
| Martlet | Krigsvold |
|---|---|
![]() |
![]() |
The review queue prioritizes saved observations needing renewal, recorded needs-work outcomes, absent reviews, partial reviews, and all-passed reviews. Search, area/position/outcome filters, ordering, and bounded pages survive reload and family navigation in the URL. Current basis never implies verified evidence, stable maturity, or release approval. Both React packages now expose twenty-two experimental exports, including the queue's native Pagination. New databases seed 38 actual export contracts; existing databases gain Pagination only through explicit Inventory updates.
Concurrent specification recovery compares the editing base, retained draft and latest saved fields after a conflict or uncertain existing-record save. Choose a source for each difference, review the prepared draft, then save through the normal validation/revision checks. Reads and comparison choices write nothing. A matching committed result returns without duplicate history. Both packages now include the comparison's native DefinitionList.
Browser specification recovery and settings protect unfinished specifications across reloads when browser storage is available, retain explicit revision-safe recovery, and provide saved workspace preferences with confirmed clearing of recovery copies. Readiness observations and comparison choices remain memory-only. Queue entry now reads its selected record before opening, including records added in another window after the parent inventory loaded.
See experimental release preparation, the changelog, and independent React references. Current reference destinations are https://react.martletdesign.dev/ and https://react.krigsvolddesign.dev/. A build or merge alone does not establish their deployed source identity.
Browser engine selection: WORKBENCH_BROWSER=firefox npm run test:browser or WORKBENCH_BROWSER=webkit npm run test:browser; Chromium remains the default. Install the selected Playwright engine and host dependencies first. WORKBENCH_TEST_PORT selects an isolated test-server port when running independent engines concurrently. CI runs all three engines.
The grammar coverage review records clarified rules and remaining evidence. Each React reference adds validated-form, query/selection and coverage pages under ?page=patterns.
50 shared page recipes now exercise both languages with identical fictional content, typed section roles, semantic article/event contracts, and separate family compositions. Complete standalone sources are in examples/jekyll/martlet and examples/jekyll/krigsvold; porting guidance defines the path to Astro and React without parsing Liquid or copying rendered HTML.







