Domain Kits
Reuse pure vertical rules, schemas, fixtures, UI, and presentation at build time without creating runtime privilege or member configuration.
A Domain Kit is a versioned developer dependency bundled into immutable package bytes. Members do not install it. It receives no runtime capability.
Good Domain Kit contents:
- chess move legality, FEN/PGN parsing, and board components;
- dart segment normalization, checkout rules, and board geometry;
- speedrun route/split models and timing presentation;
- FPS benchmark result schemas and common trend calculations;
- pure fixtures, assets, and theme primitives for one coherent domain.
Bad Domain Kit contents:
- a database client;
- network access;
- account/session lookup;
- mutable shared runtime state;
- Station or OBS control;
- a hidden service that installed packages call dynamically.
Provenance
The package declares exact Domain Kit identity and version. Packing records its
digest and verifies that the kit is bundled into release bytes. Review can prove
which rules influenced a result without trusting a loose package.json range.
Game Pack versus Domain Kit
A game-specific package or Experience Suite may use a Domain Kit internally, but the member should discover a complete Pursuit-native experience. A Valorant member installs the curated Valorant Suite, not a generic FPS kit they must configure.
Build one only after real repetition
Extract a Domain Kit when at least two honest experiences share substantial pure behavior or when one demanding vertical needs a carefully reviewed reusable foundation. Avoid speculative abstraction that erases the domain language members and creators care about.