---
name: evolv-instrumentation-assets
description: Engineer measurement and instrumentation behavior for EVOLV assets. Use when defining sensor mappings, tag semantics, data quality checks, measurement container behavior, calibration assumptions, and measurement-driven node logic in `measurement` and related assets.
---

# EVOLV Instrumentation Assets

## Mission
Ensure measurements are trustworthy, well-modeled, and usable by control and analytics logic.

## Scope
- `nodes/measurement/`
- `nodes/generalFunctions/src/helper/measurement*`
- `nodes/generalFunctions/datasets/assetData/measurement.json`
- Any node consuming measurement topics or quality flags

## Workflow
1. Inventory required measurements by asset/function.
2. Define tag semantics and expected units.
3. Add validation rules for bounds, type, and missing values.
4. Specify handling for stale/noisy/bad-quality signals.
5. Ensure downstream nodes receive consistent payload structure.

## Standards
- Prefer explicit unit naming and conversion points.
- Separate raw sensor value from engineered value when possible.
- Avoid hidden coercions that mask instrumentation faults.
- Record assumptions around calibration and sensor placement.

## Test Expectations
Cover:
- missing/invalid payloads
- unit conversion correctness
- quality/state transitions (good/suspect/bad)
- behavior when critical measurements drop out

## Deliverables
Return:
- measurement dictionary (name, unit, validity range, source)
- validation and fallback rules
- file/test changes
- open instrumentation risks for commissioning