gen-maps

Generate code maps—YAML specifications that verify functions, arguments, and imports against type definitions before code generation. Maps catch type mismatches, wrong arguments, and missing imports early in your pipeline, reducing downstream errors and rework.

Code maps are verifiable specifications defining operations, handlers, repositories, and field accesses. They sit between type definitions and code generation, providing a verification layer that validates function signatures, data usage, and import requirements without generating actual code.

Generate code maps after defining types and before generating code. They consume type definitions and location manifests as input, then output operation, handler, and repository maps under artifacts/v{N}/gen/maps with a maps-manifest for later verification.

Yes. Code maps include explicit field access declarations that catch when data is used incorrectly or accessed without declaration, ensuring data usage is traceable and verifiable against your type schema before code generation begins.

Code maps are output as YAML specifications stored under artifacts/v{N}/gen/maps alongside a maps-manifest file. These files are verification-ready and designed to be checked against type definitions and location manifests, not as executable code.