d4e72f280e
- Delete .mcp.json + .claude/rules/repo-mem.md; drop .repo-mem from .gitignore - Remove repo-mem / substrate_score / repo_search references from all .md - Move 15 EVOLV skills from .agents/skills/ to .claude/skills/ so they are auto-discovered by the Claude Code harness and invokable via the Skill tool - Retire .agents/skills/evolv-orchestrator (duplicate of the subagent at .claude/agents/evolv-orchestrator.md); orchestrator lives as a subagent only - Drop OpenAI-format agent yaml metadata from each skill (not needed for CC) - Update CLAUDE.md, CONTRACTS.md, AGENTS.md to point at the new locations and disambiguate skills (.claude/skills/) vs subagents (.claude/agents/) - Fix CLAUDE.md tick-loop wording (opt-in per-node, not a fixed 1000ms) - Widen .claude/rules/ paths frontmatter so node-architecture and telemetry rules trigger on more relevant files; add frontmatter to flow-layout rule - Bump CONTRACTS.md review date to 2026-05-19; add step 7 to the contract- change workflow (review example flows when topic usage changes) - Bump nodes/generalFunctions pin (Home.md substrate_score reference removed) Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
1.9 KiB
1.9 KiB
name, description
| name | description |
|---|---|
| evolv-process-hydraulics-mass-balance | Engineer process hydraulics and mass-balance consistency across EVOLV nodes. Use when validating flow/volume/level relationships, retention-time assumptions, split/merge behavior, and physically plausible cross-node transport dynamics. |
EVOLV Process Hydraulics Mass Balance
Mission
Preserve physically coherent hydraulics and conservation behavior across interacting EVOLV process nodes.
Harness Execution Contract
- Build a flow and accumulation map from current node contracts.
- Define invariants before edits:
- no unplanned conservation breaks
- split/merge behavior remains deterministic
- retention/transport assumptions are explicit
- Validate with scenario-based balance checks.
Scope
nodes/reactor/nodes/settler/nodes/pumpingStation/nodes/valve/,nodes/valveGroupControl/
Workflow
- Identify control volumes and interfaces.
- Map inflow/outflow/storage terms and units.
- Validate steady-state and transient behavior under typical scenarios.
- Check edge cases: zero flow, reverse flow, surge, overflow.
- Confirm output contracts preserve balance observability.
Standards
- Keep units and sign conventions explicit.
- Avoid hidden source/sink terms.
- Document retention-time and mixing assumptions.
- Preserve existing contracts unless migration is defined.
Test Expectations
Cover:
- mass/volume conservation under nominal operation
- split/merge and bypass edge cases
- boundary condition behavior at zero/low/high flow
- numeric stability under long-run ticks
Deliverables
Return:
- balance model and assumptions
- changed files/tests with scenario evidence
- unresolved hydraulic risks and required field checks
Decision interview triggers:
- changes to balance assumptions affecting KPI/compliance outputs
- compatibility-breaking payload/topic changes for flow/volume data
- startup behavior changes with overflow/dry-run implications