4eb286771e
The repo's prior docs (CLAUDE.md, MEMORY notes, superproject overview) framed monster as a "multi-parameter biological process monitor" suggesting NH4/NO3/COD/TSS measurement. The source code only emits volumetric pulse + bucket state — no constituent analysis. The framing was misleading. Reframed to match the code. Also updated examples/README.md: removed references to four flow files that don't exist in the repo (`integration.flow.json`, `edge.flow.json`, `monster-dashboard.flow.json`, `monster-api-dashboard.flow.json`) and documented the actual two files (`basic.flow.json`, `02-integrated-e2e.json`). The missing flows stay tracked in wiki/Reference-Examples.md as TODOs. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
monster
Monsternamekast control node for EVOLV.
Primary responsibilities:
- combine measured/manual flow, rain context and schedule context
- predict sampling demand and pulse distribution over sampling window
- enforce bucket/sampling constraints (volume, weight, cooldown)
- emit process fields used by PLC pulse output, report tooling (e.g. Z-Info), and dashboards
Examples:
nodes/monster/examples/monster-dashboard.flow.json(dashboard-ready visualization flow)nodes/monster/examples/monster-api-dashboard.flow.json(full API orchestration template with placeholder credentials)