enumwaiiDocumentation
Learn enumwaii's ownership model, API, integrations, and tooling.
These pages document enumwaii's public API, ownership guarantees, integrations, and tooling. Start with Getting started to declare a vocabulary and validate its first external value.
API map
| API | Purpose | Detailed guide |
|---|---|---|
em([...]) | Declare a non-empty closed string set | Branding and identity |
.enum | Branded application members | Member surfaces |
.rawEnum, .rawValues | Canonical unbranded integration values | Member surfaces |
.cases | Raw discriminants for native union narrowing | Member surfaces |
.parse, .safeParse, .is | Validate untrusted values at a boundary | Runtime boundaries and integrations |
.pick, .omit, .extend, em.combine | Compose related declarations | Branding and identity |
.derive, .deriveTo | Build exhaustive lookups while preserving provenance | Derivation |
~type, ~keys, ~safeParseResult | Declaration-local TypeScript utilities | Member surfaces |
eslint-plugin-enumwaii | Enforce source-level ownership conventions | Enforcement model |
Design foundations
Enumwaii centers one guarantee: application code receives members from the declaration that owns them.
Five foundations carry that guarantee across application code and integrations:
- Required TypeScript brands attach ownership to each member while runtime values remain ordinary strings.
.enumis the application surface; raw views serve literal-only integrations and native union discriminants.- Provenance-sensitive APIs accept members in value positions so their ownership survives inference.
- Frozen plain objects provide predictable behavior across frameworks, serializers, inspectors, and test tools.
- Runtime parsing and optional lint rules extend the ownership model to external data and source conventions.
The branding and identity guide explains the type contract and records the alternatives tested during API design. Runtime boundaries establish trust for external values, and the enforcement model maps each source convention to TypeScript or lint.
Guarantees by layer
| Layer | Responsibility |
|---|---|
| TypeScript | Carries declaration ownership through branded members and composition. |
| Runtime parsing | Establishes membership when values enter from JSON, forms, URLs, databases, providers, or agent output. |
| Standard Schema | Lets compatible consumers use the declaration as their validation contract. |
| ESLint | Guides casing, member extraction, comparisons, subsets, .cases, and union authoring. |
| Plain runtime values | Preserve native string equality, serialization, persistence, and framework interoperability. |
For coding agents
The AI agents guide provides a packaged SKILL.md, an llms.txt discovery index, an llms.md library brief, and prompts for both initial setup and read-only repository migration analysis. Every documentation page is also available as Markdown at the same path with a .md suffix.