Templates & catalog

The nanohype repo is the factory’s vocabulary: the template + composite catalog, the standards, the Platform Reference, and the SDK + MCP server that render it all.

Templates and composites

• Templates (templates/) — single building blocks, each with declared variables and a rendered output shape.
• Composites (composites/) — assemblies of templates that scaffold a whole app or module in one shot (e.g. platform-tenant, rag-agent). The platform-tenant composite pulls in the k8s-app-tenant template, which is where the chart and the Platform CR come from.
• catalog.json — the index the SDK and MCP resolve against.

Every entry has a page: what it scaffolds, the variables it takes, the files it produces, and what it composes with. Those pages are generated from the catalog at build time, so they describe what the catalog holds rather than what someone last wrote down about it.

Rendering

Two front doors render the same catalog:

• @nanohype/sdk — the programmatic path; resolves a template, fills variables, and writes the output.
• @nanohype/mcp — the MCP server, so an agent can get_template, get_composite, get_standard, and search_templates directly.

The escape hatch

The default path is k8s. When a workload isn’t pod-shaped — Lambda, edge, a static site — the explicit infra-aws template takes the sanctioned AWS/OpenTofu path instead. (This docs site is one such case.)

Standards

The guardrails live in standards/*.json. They’re what the merge gate grades against, and each one has its own page rendering the document itself:

Standard	Covers
language-toolchain	build, lint, test, and docs commands per language
version-currency	current stable runtimes and deps — no inherited defaults
platform-tenant-contract	the three artifacts every k8s deliverable ships
llm-policy	Claude as the primary model, Bedrock as the delivery path
quality-rubric-dimensions	the ten grading dimensions + the canonical lens for each
testing-rubric	the Testing-Trophy distribution and the coverage floor
observability-slo	RED/USE, the golden signals, burn-rate error budgets
telemetry-pipeline	the OTLP waist every workload emits through, and the tier it lands in
resource-naming	the naming grammar for cloud and k8s resources
resource-tagging	the org-wide tag / label / OTel-attribute taxonomy
seo-baseline	one canonical origin + the discovery artifacts a public site ships