---
name: template-active-inference
description: Active Inference multi-track exemplar — analytical formulas, pymdp simulation, sheaf manuscript composition, GNN, ontology, Lean gates, roadmap tracks.
version: 0.1.0
author: docxology
license: MIT
tags: [exemplar, active-inference, multi-track, sheaf]
---

# template-active-inference

Project-scoped skill for the in-repo exemplar at
`projects/templates/template_active_inference/`. Load this when working inside the project.

## When to Use

- Working inside the `template_active_inference` exemplar — running scripts, editing source,
  or regenerating outputs.
- Forking this exemplar as the starting scaffold for a new research project.
- Validating that the exemplar's contracts (thin-orchestrator, layer boundaries,
  no-mocks testing) still hold after changes.

## Quick Reference

```bash
# From this project root
uv run pytest tests --cov=src --cov-fail-under=90

# From the repository root
uv run python scripts/pipeline/stage_02_analysis.py --project templates/template_active_inference
uv run python scripts/pipeline/stage_03_render.py --project templates/template_active_inference
uv run python scripts/pipeline/stage_04_validate.py --project templates/template_active_inference
uv run python scripts/pipeline/stage_05_copy.py --project templates/template_active_inference
```

## Pitfalls

- **Keep scripts thin.** Business logic belongs in `src/` or shared
  `infrastructure/`, not in `scripts/`.
- **No mocks.** All tests must use real data, real files, and real
  computation.
- **Outputs are disposable.** Never hand-edit `output/` — regenerate from
  source and config.
- **Run from the repo root.** Commands assume the template monorepo root
  as working directory unless the child `AGENTS.md` states otherwise.

## Cross-refs

- Project contract: [`AGENTS.md`](../../../AGENTS.md)
- README: [`README.md`](../../../README.md)
- TODO: [`TODO.md`](../../../TODO.md)
- Exemplar roster: [`projects/AGENTS.md`](../../../../../AGENTS.md)