# Proposal Template Registry

Maps programme IDs to proposal scaffolds and final-output template-pack metadata.

## Structure

```text
proposal-template-registry/
|-- registry.json
|-- horizon-europe/
|-- digital-europe/
|-- open-call/
`-- README.md
```

Each template directory can now contain two different layers:

- `src/` for the Markdown-first authoring scaffold
- `template-pack/` for final DOCX rendering metadata

Example:

```text
programme-template/
  src/
  template-pack/
    manifest.yaml
    section-map.yaml
    styles.yaml
    placeholders.yaml
    budget-schema.yaml
    reference.docx
```

## Usage

The `init-proposal` MCP tool reads `registry.json` to scaffold a new proposal
directory. When the user specifies a programme such as `digital-europe`, the
tool copies the corresponding template and writes `.proposalengine.json` with
programme defaults.

Templates that ship with ProposalEngine are read-only scaffolds. The copied
proposal directory is fully editable.

Template packs are separate from the scaffold. They describe how the final Word
document should be rendered and validated.

## Adding a Programme Template

1. Create a new directory under `proposal-template-registry/`, for example `life/`
2. Add the section directories matching the programme scaffold under `src/`
3. Add `_meta.json` per section with programme defaults
4. Add `.call/requirements.json` and `.call/template-schema.json`
5. Add `.proposalengine.json` with programme defaults
6. Add `template-pack/` when final Word output is supported
7. Register the template in `registry.json`
