Skip to main content

Starter Templates

Three tiers, increasing in complexity. Each tier is a starting point — copy, then mutate to fit. The Tier 1 fixtures are mirrored in scripts/tests/fixtures/solution-dev/tier1/ and verified by npm run check-snippets so this page does not silently rot.
Future: when the em-service-template repo lands, these tiers collapse to cookiecutter gh:emergenceai/em-service-template --no-input solution_name=<your-name> tier=<1|2|3>. The inline scaffolds here are the bridge until that ships.
Every scaffold pins em-service to v0.0.15 (the version in em-service Chart as of 2026-05-14). Major em-service version bumps trigger a fixture refresh; npm run check-snippets (CI) fails if the inline snippets drift from the canonical fixtures.
The simplest viable solution: one HTTP service, one image, JWT validation, env-injected secrets. Maps to the Quickstart shape with auth and secrets wired in.

File tree

Files

Mirrored fixtures

Canonical copies of the eight files above live at scripts/tests/fixtures/solution-dev/tier1/. npm run check-snippets compares the inline snippets to the fixtures and fails if they drift.

Snippet drift check

The Tier 1 fixture files at scripts/tests/fixtures/solution-dev/tier1/ are the source of truth for the inline snippets above. Run npm run check-snippets to verify they match — CI runs this check on every PR. If you change Tier 1 inline content, update the fixtures (or vice versa), then re-run npm run check-snippets.

Next steps

Quickstart

Walk through Tier 1 step by step.

Package and deploy

Multi-component packaging and per-environment overlays.

Register your first agent

Required for Tier 3 agents to be discoverable.

Data Insights overview

The Tier 3 reference solution in production.