# Function Anchors

This folder stores class-level anchor documents that define EVOLV logic truth for long-term maintainability.

## Standard
1. Start each anchor with a **Connection Map (At a Glance)**.
2. Then provide a **Unit Table** as the first data section.
3. Cover the class end-to-end: config, I/O contracts, mode/state logic, full function inventory, calculations, safeguards, tests, invariants, and known gaps.
4. Keep references tied to file/line evidence.

## Mandatory Architecture Rule
All EVOLV node anchors must use the same folder and artifact structure as `rotatingMachine`.

Required per node:
- `.agents/function-anchors/<nodeName>/ANCHOR-<nodeName>.md`
- `.agents/function-anchors/<nodeName>/ANCHOR-<nodeName>.html`
- `.agents/function-anchors/<nodeName>/EVIDENCE-<nodeName>-tests.md`
- `nodes/<nodeName>/test/basic/*.test.js`
- `nodes/<nodeName>/test/integration/*.test.js`
- `nodes/<nodeName>/test/edge/*.test.js`

Enforcement policy:
- Do not ship behavioral changes in `nodes/<nodeName>/` without updating the matching anchor and evidence files.
- New EVOLV nodes must be created with this structure from day one.
- Existing nodes missing this structure are considered incomplete and must be brought to parity.

## Files
- `TEMPLATE.md`: reusable format for all future anchor points.
- `rotatingMachine/ANCHOR-rotatingMachine.md`: current rotatingMachine anchor.
- `rotatingMachine/EVIDENCE-rotatingMachine-tests.md`: test-evidence companion.
- `pumpingStation/ANCHOR-pumpingStation.md`: pumpingStation anchor preparation baseline.
- `pumpingStation/ANCHOR-pumpingStation.html`: pumpingStation visual topology anchor baseline.
- `pumpingStation/EVIDENCE-pumpingStation-tests.md`: pumpingStation test plan/evidence baseline.
- `monster/ANCHOR-monster.md`: monster node anchor baseline with API/report integration context.
- `monster/ANCHOR-monster.html`: monster visual topology anchor baseline.
- `monster/EVIDENCE-monster-tests.md`: monster test evidence baseline.