Building against it
Everything here is for building with the stack rather than evaluating it. If you are still deciding what this is, how the factory works andthe atlas are the shorter route.
The Platform Reference is the front door for an agent — a Claude Code session, a Bedrock agent, any client that produces software — and the place to start if you are wiring one up. The rest go deeper on choosing, composing and authoring.
Platform ReferenceThe agent-consumable front door: the stack, the layer boundaries, the contract repos, and the SDK and MCP entry points.Catalog referenceWhich template to reach for, how templates compose, and the module layering from a minimal API up to a full platform.CompositesWhat a composite is, how one is assembled, and when to reach for it over a single template.Production readinessThe cumulative checklist a scaffolded project clears before it is deployed.Authoring a templateCreating a new template, from empty directory to validated and catalog-ready.Template contractThe formal specification a template manifest is validated against — every field, every rule.Composite contractThe formal specification for a composite: how it names its templates and threads variables through them.Building a consumerHow to build a scaffolding tool that renders nanohype templates — the action doc behind the two contracts.The Platform Reference patternThe structure generalised: how any platform can publish an agent-consumable front door of its own.
The machine-readable surfaces
An agent should read the contracts rather than these pages. Each is a stable artifact the factory maintains, and each has a rendered view here for humans:
catalog.json— every template and composite, browsable attemplates and compositesstandards/*.json— the production bar, browsable atstandardsAGENTS.mdin each repo — the per-repo entry point, browsable atrepos@nanohype/sdkto resolve and render them, and@nanohype/mcpto expose the same surfaces as MCP tools