# OCETS 1.1

> Open Canonical Energy Telemetry Standard: vendor-independent contracts for observations, events, metrics, registry identity, topology, operational health, security, and conformance.

Use `llms-full.txt` when one URL must provide the complete normative context. Use the individual resources below when selective retrieval is available.

## Required normative resources

- [Complete combined context](llms-full.txt)
- [Core standard](source/01_Open_Canonical_Energy_Telemetry_Standard_v1.1.md)
- [Canonical Metric Catalogue](source/03_Canonical_Metric_Catalogue_v1.1.md)
- [Plant Registry Specification](source/04_Plant_Registry_Specification_v1.1.md)
- [Normative Registry JSON Schema](schema/plant-registry-v1.1.schema.json)
- [Architecture Decision Records](source/05_Architecture_Decision_Records_v1.1.md)

## Implementation resources

- [Reference Implementation Guide](source/02_Reference_Implementation_Guide_v1.1.md)
- [Solar plant implementation prompt](solar-plant-implementation-prompt.txt)
- [Validated example Registry](examples/solar-plant-example.yaml)
- [Registry validator](tools/validate_registry.py)
- [Validator tests](tools/test_validate_registry.py)
- [Reference Telegraf configuration](reference/telegraf/telegraf.conf)
- [Reference edge inputs](reference/telegraf/telegraf.d/edge-device.conf)
- [Reference Mosquitto configuration](reference/mosquitto/ocets-edge.conf)

## Mandatory model behavior

1. Treat the Registry as the authoritative semantic source of truth.
2. Use stable logical IDs; never use addresses, hostnames, or replaceable hardware identifiers as canonical identity.
3. Use only canonical metric names and units from the catalogue, unless a valid namespaced extension is declared.
4. Preserve acquisition timestamps in UTC, Observation quality, and origin.
5. Do not convert missing or stale values to measured zero.
6. Validate a generated Registry before generating or deploying collector configuration.
7. Keep credentials and implementation addresses outside semantic identity and committed Registry data.
8. Do not claim a conformance profile unless all of its mandatory rules and capabilities are satisfied.