The upstream vault treats capsule.contract.generator-projection-index.v1 as the authoritative dispatch table for generation. This public repo does not publish the full generator corpus, but it does expose the public doctrine needed to understand how projection works.
- load the projection-index capsule
- enumerate contracts from the declared corpus
- dispatch by
generator_hint - refine placement with
group,surface,sdk, andaggregatetags - emit only artifacts that the projection index recognizes
- fail fast when hints, coverage, or release evidence are inconsistent
generator_hint:*selects the primary emitter rolegroup:*clusters related contracts for package or route-family placementsurface:*distinguishes public APIs, extension APIs, internal boundaries, and storage schemassdk:*marks which generated SDK or compiler profile should include an artifactaggregate:*makes child contracts discoverable from family indexes
- projection doctrine in
projection-doctrine.md - boundary posture in
domain-boundaries.mdand../PUBLIC_BOUNDARY_MAP.json - current public artifact discovery in
../PUBLIC_CONTRACT_CATALOG.json - schema, OpenAPI, examples, client recipes, and release evidence that external consumers can review today
- a concrete public OpenAPI code-generation path in
openapi-codegen-recipes.mdfor tool-builders who want generated TypeScript declarations from the strongest published HTTP contract across repo-local plus CommonJS, ESM, and TypeScript package-consumer styles
- the full upstream generator corpus
- private emitter internals
- unpublished runtime packages
- hosted or operator-only generation workflows
Generator readiness is part of the public trust posture. Outside reviewers should be able to see that projection is governed by explicit rules, not by ad hoc file copying or undocumented compiler behavior.