# `_inspire/` — reference flat template (TO BE REMOVED)

This directory holds the original single-template `create-leafmesh` layout
(greeter → researcher → processor, with the advisor / fallback / scheduler
satellites). It was the v0.x scaffolder's only output.

**It exists here as a reference while the new business-function templates
are built. It is NOT part of the shipping surface — the registry does not
list it, the CLI does not scaffold it, customers cannot pick it.**

## Why we kept it (for now)

1. **Sound patterns to inspire from** — the flat template already
   demonstrates: programmatic + LLM mix, scheduler crons, external
   connectors, HITL stub, Docker compose, working tests. Many of those
   patterns transplant directly into the new templates.
2. **A working reference for the SDK API surface** — when implementing
   a new business template, it's faster to glance at how greeter calls
   processor here than to re-derive the call shape from SKILL.md.
3. **Diff target** — when porting a pattern (e.g. the chained
   `wait_for` fan-in from `researcher`) we want to see the before/after
   on the same disk.

## What goes away

This whole directory is removed when **all three** are true:

- At least 3 business-function templates ship and pass smoke tests.
- Patterns we wanted from here have been hoisted into the new templates
  or into `claude_skills/leafmesh/examples.md`.
- We're confident no orphan references remain (grep for `_inspire`).

Removal command when ready: `git rm -r create_leafmesh/templates/_inspire/`.

## What this is NOT

- **Not** a fallback the CLI will fall back to.
- **Not** "the simple version" — customers wanting minimal should use a
  future `starter` template (Rule-1-shaped, not this).
- **Not** where new agency code goes. Add new patterns to the relevant
  business-function template's `agency/` directory.

## The original README

The flat template's customer-facing README is in this same directory as
`README.md` (it uses `{{project_name}}` substitutions because it was meant
to be scaffolded into a customer project). Read it for the v0.x story —
warts, scaffolds, and all.
