Classic Zod 4.2+ embeds Standard JSON Schema on the schema value, so the only Classic Zod entry point is root @arkenv/standard. We will not publish @arkenv/standard/zod as a re-export of that root.
Accepted (#1609)
ADR 0025's 2026-08-24 amendment added @arkenv/standard/valibot and @arkenv/standard/zod-mini because those libraries keep JSON Schema conversion in a standalone function. Classic Zod does not need that binder. The amendment deferred a redundant @arkenv/standard/zod alias to separate exploration.
Option A (canonical root). Reject @arkenv/standard/zod.
- A
/zodsubpath would imply a Zod-specific adapter. The Standard Schema engine's value is validator-agnostic consumption of anything that implements the spec. - ADR 0019 already removed redundant re-exports (
./shared) that duplicated a capability without adding semantics. A/zodalias is the same class of surface bloat. - Shipping
/zodwould invite/typebox,/arktype, and every later Standard Schema library, turning a zero-config root into a maintenance list. /valibotand/zod-ministay. They are not aliases: they bind a converter. Do not flatten Valibot onto the root import in docs orarkenv initto "prove" symmetry.
Discoverability is a documentation problem. The Zod guide, @arkenv/standard reference, Choosing an engine, and the arkenv init Zod dialect already import from the root.
- A — Canonical root (chosen). Classic Zod uses
@arkenv/standard. Converter subpaths remain only where JSON Schema is not on the value. - B — Validator aliases. Add
@arkenv/standard/zod(and maybe more) as thin re-exports. Rejected: fake specialized tooling, ADR 0019 regression, unbounded subpath checklist.
Searchers should expect Classic Zod on root @arkenv/standard; there is no /zod subpath. Cosmetic validator aliases are rejected under this precedent. /valibot and /zod-mini stay as converter binders, not a template for aliases.