Generalize live material consumption architecture

docs/enlyze-api.md

@@ -73,18 +73,49 @@ Each requested variable contains required UUID and optional `resampling_method`:
 
 `Downtime` requires UUID, machine UUID, type (`THRESHOLD` or `NO_DATA`), timezone-aware ISO 8601 start, nullable end, and nullable comment/reason/update information. A null end denotes an ongoing downtime. It supports historical downtime retrieval but does not establish a complete machine-state timeline.
 
-## VERIFIED WITH LIVE CUSTOMER API
+## VERIFIED WITH CUSTOMER EXPLORATION
 
-None. This execution environment has no ENLYZE DNS/network access, so no customer operation has been sent in this milestone.
+The following are customer-specific observations, not general ENLYZE API
+semantics:
+
+- K7 candidate fiber mass-flow variable: `Stundenleistung Anlage` (kg/h).
+  Historical behaviour supports interpreting it as a process-responsive
+  band-scale signal. It can remain frozen at a non-zero value during stops.
+- Validated K7 integration gate: `Geschwindigkeit Gesamtanlage > 0.5 m/min`.
+  Do not use the boolean `Anlage läuft` as the primary gate for this
+  calculation.
+- `production_run.quantity_total` is populated from ERP/BI production feedback
+  received by ENLYZE for this setup, not necessarily from machine signals. The
+  tested CSV source field is `PCO_FEEDB_QUANTITY`. For inspected
+  machines/articles it is reported finished-product area in m²: 5.00 m × 50 m
+  = 250.00 m², 4.75 m × 50 m = 237.50 m², and 5.80 m × 50 m = 290.00 m².
+  `quantity_total.unit` is separately configured and is not authoritative
+  without configuration validation.
+
+Historical validation case (plausibility only): production order
+`K 7-12026000842`, Production Run 2026-08-31T10:57:54Z to
+2026-08-31T18:23:11Z, had ERP `quantity_total` 12,420 m². Speed-gated
+integration produced approximately 5.206 active hours, 5,180.1 kg fiber feed,
+2,174.2 m machine length, and 995.1 kg/h average active throughput. Article
+external ID `213408` (width 6.0 m; static mean basis weight 390.16 g/m²) gives
+an approximate reported finished-product mass of 4,845.8 kg. This supports the
+physical plausibility of the feed integration; it is not a precise material
+yield calculation.
 
 ## STILL UNKNOWN
 
-- Customer response values, permissions, authentication success/failure behavior, default page size, and rate/retention limits.
+- Full customer response coverage, permissions, authentication
+  success/failure behavior, default page size, and rate/retention limits.
 - Whether production-run filters have the desired interval-overlap behavior; completed-run `start`/`end` are candidate integration boundaries but require live confirmation.
-- Which customer variable is a consumption signal and whether its unit/scaling factor makes it usable for integration.
+- Whether the validated K7 signal/gate generalize to other machines, articles,
+  production conditions, or future signal configuration.
 - Whether omitted `resampling_interval` yields native/raw resolution; its unit and exact temporal meaning of resampling methods.
 - Sample ordering, boundary inclusion, native sampling behavior, gaps, nulls, quality/bad samples, late arrivals, corrections, and backfills.
 - A complete historical machine operational-state resource beyond downtimes.
+- Exact per-order material yield: band-scale material may remain in the machine
+  at an order transition and ERP feedback can arrive asynchronously or
+  periodically. WIP/transport-delay accounting is required before interpreting
+  feed-versus-finished-product differences as yield or scrap.
 
 ## Exact bounded manual exploration sequence