Files
EVOLV/.agents/function-anchors/machineGroupControl/ANCHOR-machineGroupControl.md
znetsixe 6a6c04d34b Migrate to new Gitea instance (gitea.wbd-rd.nl)
- Update all submodule URLs from gitea.centraal.wbd-rd.nl to gitea.wbd-rd.nl
- Add settler as proper submodule in .gitmodules
- Add agent skills, function anchors, decisions, and improvements
- Add Docker configuration and scripts
- Add manuals and third_party docs
- Update .gitignore with secrets and build artifacts
- Remove stale .tgz build artifact

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
2026-03-04 21:07:04 +01:00

1.3 KiB

machineGroupControl Function Anchor (Preparation Baseline)

0) Connection Map (At a Glance)

  • Node type: machineGroupControl
  • Scope: baseline anchor scaffold to satisfy EVOLV required architecture.

1) Unit Table (Initial Baseline)

Signal/Field Represents Default Unit Source of Truth Produced By Consumed By Fallback/Degraded Behavior
TBD TBD TBD nodes/machineGroupControl/src/* TBD TBD TBD

2) Class Identity

  • Runtime registration: nodes/machineGroupControl
  • Node-RED wrapper: nodes/machineGroupControl/src/nodeClass.js (when present)
  • Domain logic: nodes/machineGroupControl/src/specificClass.js (when present)
  • Editor UI: nodes/machineGroupControl/*.html (when present)

3) Current Gaps To Resolve Before Declaring Anchor Complete

  • Replace placeholder sections with full contract mapping on first functional change.

4) Standardization Plan

  1. Maintain this anchor and evidence docs with behavior changes.
  2. Maintain tests under test/basic, test/integration, test/edge.
  3. Maintain examples package (README, basic.flow.json, integration.flow.json, edge.flow.json).

5) Acceptance Criteria For Completion

  • Anchor/evidence artifacts exist.
  • Test structure exists.
  • Example structure exists.