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>
This commit is contained in:
znetsixe
2026-03-04 21:07:04 +01:00
parent fbd9e6ec11
commit 6a6c04d34b
169 changed files with 21332 additions and 1512 deletions

View File

@@ -0,0 +1,54 @@
---
name: evolv-alarms-interlocks-permissives
description: Design and review alarms, interlocks, and permissive logic for EVOLV control nodes. Use when implementing trip conditions, permissive checks, startup/shutdown guards, alarm priorities, latching/reset behavior, and operator-facing fault handling.
---
# EVOLV Alarms Interlocks Permissives
## Mission
Make alarm and interlock behavior explicit, testable, and operationally safe while preserving availability-first policy bounds.
## Harness Execution Contract
- Build alarm/interlock map from current node contracts and state logic.
- Define invariants before edits:
- trips/permissives are deterministic
- latching/reset behavior is explicit
- operator-visible diagnostics are preserved
- Validate with sequence and fail-state tests.
## Scope
- `nodes/pumpingStation/`
- `nodes/machineGroupControl/`
- `nodes/rotatingMachine/`
- Any node with mode/state transitions and protective actions
## Workflow
1. Enumerate alarm conditions and priority/severity.
2. Define interlock and permissive truth tables.
3. Verify startup/shutdown/emergency sequences.
4. Confirm reset, auto-recovery, and manual acknowledgement behavior.
5. Ensure outputs expose actionable fault context.
## Standards
- Avoid hidden permissives; every gate should be observable.
- Keep alarm naming stable and semantically clear.
- Separate advisory warnings from trip-level protection.
- Preserve controlled compatibility for released fault topics.
## Test Expectations
Cover:
- trip activation and reset/latch behavior
- permissive-denied and permissive-restored transitions
- out-of-order signal handling in sequence transitions
- degraded sensor quality paths and alarm escalation
## Deliverables
Return:
- alarm/interlock/permissive matrix
- changed files/tests and evidence
- unresolved protection-vs-availability tradeoffs
Decision interview triggers:
- changed trip thresholds or permissive logic with operational impact
- altered reset authority (auto vs manual)
- alarm contract changes affecting external consumers

View File

@@ -0,0 +1,4 @@
interface:
display_name: "EVOLV Alarms Interlocks Permissives"
short_description: "Protective logic and operator alarm specialist"
default_prompt: "Map alarm/interlock/permissive behavior in the impacted EVOLV nodes, define deterministic trip and reset rules, validate sequence edge cases, and return test-backed recommendations with clear operational tradeoffs."