PKDM — Peak Demand Module
Architecture: RSGA™ — Resource Sustainability Governance Architecture
Parent Standard: Resource Demand Governance Standard (RDGS)
Category: Governance & Enforcement
Subcategory: Resource Governance
Type: Core Module
Governed Space: Peak Resource Demand Governance
Module ID: RSGA-RDGS-PKDM-03
Origin ID: OOF-RSGA-RDGS-PKDM
Version: 1.0
Status: Draft Module
Effective Date: 5 October 2026
Compatibility: Methodology OS — Modular Compatibility
GIE-Compatible: Yes
AI-Readable: Yes
Authority: OOF® — OriginOpen® Foundation
Protection: Protected Methodological Work
Canonical Language: English
1. Canonical Definition
PKDM — Peak Demand Module governs how the highest materially relevant Resource Demand occurring within a defined governance interval is identified, measured, bounded, temporally located, functionally attributed, evidenced, qualified, and reassessed so that historical extremes, instantaneous spikes, theoretical maxima, installed consumption capability, requested capacity, or isolated anomalies are not automatically treated as governed Peak Demand.
PKDM establishes the Peak Demand State within RDGS.
Maximum Observed Value ≠ Governed Peak Demand by definition.
2. Operational Role
CRDM establishes the Core Resource Demand object.
FDIM establishes the functional structure of that Demand.
PKDM determines the materially relevant upper Demand condition.
Its role is to establish:
whether Peak Demand exists; how much Resource is required at Peak; when the Peak occurs; how long it lasts; which function or functions create it; whether it is recurring, seasonal, conditional, event-driven, or anomalous; which measurement interval defines it; which evidence supports it; and how certain the Peak Demand representation is.
PKDM prevents Resource governance from treating a single high number as sufficient evidence of Peak Demand.
3. Core Question
What is the highest materially relevant Resource Demand within the governed interval, when does it occur, how long does it persist, what creates it, and what evidence establishes that it represents a governable Peak rather than an isolated or misleading maximum?
4. Position in RDGS Module Flow
CRDM — Core Resource Demand Module → FDIM — Functional Demand Identification Module → PKDM — Peak Demand Module → CPDM — Concurrent & Parallel Demand Module → DCMM — Demand Consolidation & Management Module
PKDM establishes the Peak Demand structure before multiple Demand objects are evaluated for concurrency and consolidated Resource Demand.
5. Governed Space
PKDM governs:
Peak Resource Demand Governance
This space concerns the highest materially relevant Resource requirement within defined temporal, functional, spatial, operational, and evidentiary conditions.
6. Governed Object
The primary Governed Object is:
A Peak Resource Demand State associated with a governed Resource Demand or Functional Demand Profile.
The Governed Object may include:
Peak quantity; Peak capacity; Peak rate; Peak interval; Peak duration; Peak frequency; Peak recurrence; Peak function; Peak operating state; Peak location;
Peak evidence; Peak uncertainty.
7. Scope
PKDM applies wherever Resource Demand varies and the upper Resource requirement materially affects downstream Resource governance.
Its Scope includes:
Peak Demand identification; Peak Demand measurement; Peak interval definition; Peak duration; Peak timing; Peak frequency; Peak recurrence; Peak seasonality; Peak operating state; Peak functional attribution; Peak spatial context; Peak Resource quality or performance conditions where relevant; historical Peak Demand; current Peak Demand; recurring Peak Demand; conditional Peak Demand; event-driven Peak Demand; predicted Peak Demand; simulated Peak Demand; Peak evidence; Peak anomalies; Peak uncertainty; Peak sufficiency; Peak reassessment; Peak versioning.
PKDM does not independently determine:
Demand concurrency across independent Demand objects; final Demand consolidation; Resource Dependency; Criticality; Access authorization; Priority; Allocation; Consumption governance; Scarcity response; Resilience; Sustainability.
8. Entry Requirement
PKDM receives:
Core Resource Demand Profile
and:
Functional Demand Profile
where applicable.
The input should preserve relevant:
Resource identity; Demand identity; function; quantity/capacity/rate; native measurement; time; location; evidence; uncertainty.
9. Peak Demand
Peak Demand is the highest materially relevant Resource requirement within a defined governance interval under specified operating conditions.
Peak Demand requires both:
Magnitude
and:
Context.
10. Peak Magnitude
Peak Magnitude represents the Resource quantity, capacity, or rate required during the Peak condition.
11. Peak Time
Peak Time identifies when the Peak Demand occurs.
12. Peak Duration
Peak Duration identifies how long the Peak or Peak-level condition persists.
13. Peak Interval
A Peak cannot be interpreted correctly without defining the interval over which it is measured.
Examples:
1 second
1 minute
15 minutes
1 hour
1 day
seasonal interval
14. Measurement Interval Principle
Peak Demand depends upon the measurement interval.
A one-second Peak may differ materially from a fifteen-minute Peak or hourly Peak.
15. Peak Window
A Peak Window defines the period within which Peak Demand is evaluated.
Canonical representation:
Peak Window Start → Peak Demand Condition → Peak Window End
16. Peak Boundary
The Peak Boundary determines which Resource Demand and which operational conditions belong to the Peak assessment.
17. Peak Boundary Integrity
Peak Demand should follow the governed Resource reality rather than the interval or aggregation method most convenient for analysis.
18. Peak Demand vs Maximum Observed Value
The maximum observed measurement may be relevant evidence.
It is not automatically the governed Peak Demand.
Maximum Observed Value ≠ Governed Peak Demand by definition.
19. Instantaneous Spike
A brief Resource Demand spike may represent:
a valid Peak; a transient event; measurement noise; startup behaviour; fault condition; anomaly.
PKDM determines its governance relevance.
20. Peak vs Spike
Demand Spike ≠ Governed Peak Demand by definition.
Duration and operational relevance matter.
21. Sustained Peak
A Sustained Peak is a high Demand condition persisting for a materially relevant duration.
22. Short-Duration Peak
Short-duration Peaks may still be operationally significant where Resource infrastructure must support them.
23. Peak Persistence
PKDM should determine whether Peak Demand is:
instantaneous; short-duration; sustained; recurring; persistent during a defined operating state.
24. Peak Frequency
Peak Frequency describes how often the Peak or comparable Peak condition occurs.
25. Peak Recurrence
Peak Demand may recur according to:
operational cycles; daily cycles; weekly cycles; seasonal cycles; production cycles; workload patterns.
26. Recurring Peak
A recurring Peak should remain distinguishable from an isolated Peak event.
27. Isolated Peak
An isolated Peak may be valid but should not automatically be represented as typical recurring Peak Demand.
28. Peak Seasonality
Some Resource systems exhibit seasonal Peak Demand.
Examples include:
Electricity
Cooling
Water
Heating
Agricultural Resources
Network capacity
29. Seasonal Peak vs Annual Average
Seasonal Peak Demand ≠ Annual Average Demand.
Annual averages may conceal operationally critical Peak conditions.
30. Daily Peak
Demand may exhibit predictable intraday Peaks.
31. Weekly Peak
Demand may vary systematically across weekly operating patterns.
32. Operational Peak
An Operational Peak occurs under a defined high-load operating state.
33. Functional Peak
A Functional Peak represents the highest materially relevant Resource Demand attributable to a specific function.
34. System Peak
A System Peak represents the highest Resource requirement across the relevant system boundary.
35. Functional Peak vs System Peak
The Peak of one function may occur at a different time from the Peak of the entire system.
Functional Peak ≠ System Peak.
36. Component Peaks
Individual components may each have Peak Demand.
Their Peaks must not automatically be added.
37. Non-Simultaneous Peaks
If Component A peaks at Time 1 and Component B peaks at Time 2:
Peak A + Peak B ≠ System Peak by definition.
CPDM performs detailed concurrency governance.
38. Coincident Peak
A Coincident Peak occurs when multiple relevant Demand components reach materially high Demand during the same temporal interval.
PKDM may identify the condition.
CPDM determines concurrency structure across Demand objects.
39. Non-Coincident Peak
Peak Demand components may occur separately.
Their individual maxima should remain distinct.
40. Peak Diversity
Differences in timing between functional or system Peaks may materially reduce combined Peak Demand.
PKDM preserves the Peak timing required for later concurrency analysis.
41. Baseline Demand
Baseline Demand provides a reference against which Peak Demand may be interpreted.
42. Peak-to-Baseline Relationship
PKDM may represent:
Peak Demand / Baseline Demand
where useful.
The ratio is descriptive unless a governed interpretation is separately defined.
43. Average Demand
Average Demand may provide context for Peak Demand.
It must not replace Peak Demand where infrastructure must support the Peak.
44. Peak-to-Average Relationship
A Resource system may exhibit a high Peak-to-Average relationship.
This may materially affect Resource capacity requirements.
45. Average Demand Boundary
Average Demand ≠ Peak Demand.
A system that satisfies average Demand may still fail at Peak.
46. Minimum Demand vs Peak Demand
Minimum and Peak Demand represent different operating conditions.
Neither should be used as a substitute for the other.
47. Installed Consumption Capability
Installed Resource consumption capability may establish an upper technical boundary.
It does not establish Peak Demand.
Installed Capability ≠ Peak Demand.
48. Rated Maximum
A system's rated maximum Resource input does not automatically represent its governed Peak Demand.
49. Theoretical Maximum
A theoretical maximum represents what may be technically possible under defined assumptions.
Theoretical Maximum ≠ Governed Peak Demand.
50. Requested Peak Capacity
A participant may request Resource capacity intended to cover expected Peaks.
Requested Peak capacity is not automatically validated Peak Demand.
51. Contracted Capacity
Contracted Resource capacity may exceed or fall below actual Peak Demand.
Contracted Capacity ≠ Peak Demand.
52. Historical Peak
Historical Peak Demand may provide evidence for current or future Peak assessment.
53. Historical Peak Boundary
Historical Peak ≠ Current Peak Demand by definition.
Operating conditions may have changed.
54. Historical Extreme
An extreme historical value may result from unusual conditions.
PKDM should determine whether it remains relevant.
55. Historical Peak Context
Historical Peak evidence should preserve:
Date/time; Duration; Operating state; Function; Resource state; Location; Measurement interval; Relevant conditions.
56. Current Peak Demand
Current Peak Demand represents the highest materially relevant Demand under current governed operating conditions.
57. Future Peak Demand
Future Peak Demand may be relevant for planning.
Its epistemic status must remain explicit.
58. Predicted Peak Demand
A Prediction may estimate future Peak Demand.
Predicted Peak Demand ≠ Current Peak Demand.
PGA™ retains Prediction Governance.
59. Simulated Peak Demand
Simulation may estimate Peak Demand under hypothetical conditions.
Simulated Peak Demand ≠ Observed Peak Demand.
SIMULOS® retains Simulation Governance.
60. Planned Peak Demand
A planned future operating state may imply Peak Resource requirements.
Planned Peak Demand ≠ Current Peak Demand.
61. Assumed Peak Demand
An assumed Peak may be used where evidence is incomplete.
Its assumed status must remain explicit.
62. Peak Demand Evidence
Peak Demand should be supported by evidence proportionate to its governance significance.
63. Direct Peak Measurement
Direct Resource measurements may establish observed Peaks.
64. Functional Peak Evidence
Functional evidence may establish which activity created the Peak.
65. Derived Peak Demand
Peak Demand may be derived from:
workload; production requirement; system configuration; technical Resource coefficient; operating state.
The derivation method must remain explicit.
66. Peak Evidence Provenance
At minimum, Peak evidence should preserve where relevant:
Demand ID
Resource ID
Function ID
Measurement source
Measurement interval
Time
Duration
Location
Operating state
Version:
67. Peak Evidence Freshness
Peak Demand evidence may become stale following material system or operational change.
68. Peak Evidence Relevance
A historical or technical maximum should not be used merely because it is the largest available number.
The evidence must remain relevant to the governed Peak condition.
69. Peak Measurement Resolution
Measurement resolution should be sufficient to capture materially relevant Peaks.
70. Insufficient Resolution
Low-resolution data may hide short-duration Peaks.
71. Excessive Resolution
Very high-resolution data may expose transient noise that is irrelevant to Resource governance.
72. Resolution Integrity
The selected measurement interval should reflect the Resource System's actual operational response requirements.
73. Resource-Specific Peak Interval
Different Resources may require different Peak intervals.
Examples:
Electricity may require short-duration Peak analysis.
Water storage may require hourly or daily Peak analysis.
Material Demand may require production-cycle analysis.
Compute may require workload-window analysis.
74. Peak Duration Significance
A Peak lasting one second may have different governance significance from the same magnitude sustained for six hours.
Same Peak Magnitude ≠ Same Peak Condition.
75. Peak Energy or Quantity Requirement
Where relevant, PKDM should preserve both:
Peak rate/capacity
and:
total Resource quantity consumed or required during the Peak interval.
76. Peak Ramp
Demand may increase rapidly toward Peak.
The rate of change may matter for Resource Systems unable to respond instantaneously.
77. Ramp-Up Condition
PKDM may preserve the Resource Demand trajectory leading into Peak.
78. Ramp-Down Condition
The decline from Peak may also affect the duration of elevated Resource Demand.
79. Peak Plateau
Some Resource systems reach a sustained high-demand plateau rather than a single sharp maximum.
80. Multi-Peak Pattern
A Demand profile may contain several materially relevant Peaks.
PKDM should not force them into a single Peak where multiple Peak conditions matter.
81. Primary Peak
A Primary Peak may represent the highest materially relevant Demand within the governed interval.
82. Secondary Peak
Secondary Peaks may remain relevant where they occur under different conditions or functions.
83. Peak Cluster
Multiple Peaks occurring close together may form a Peak Cluster where Resource recovery between Peaks is insufficient.
84. Peak Recovery Interval
The interval between Peaks may matter where Resource capacity requires replenishment, recharge, cooling, regeneration, or recovery.
85. Resource Storage Effect
Storage may buffer Peak Demand seen by the upstream Resource Source.
Therefore:
End-Use Peak Demand ≠ Source Peak Demand by definition.
86. Peak Demand Location
Peak Demand may differ by location.
A regional Peak does not automatically describe the Peak at a particular node.
87. Local Peak vs Aggregate Peak
Local Peak Demand ≠ Aggregate Peak Demand.
88. Network Peak
Network Resource Demand may Peak at a specific node or transfer boundary even where total system Demand remains lower than system-wide capacity.
89. Spatial Peak Concentration
Demand may become spatially concentrated.
PKDM should preserve the location of Peak Demand where material.
90. Peak Quality Requirement
Peak Demand may also require Resource of a particular quality.
Quantity alone may be insufficient.
91. Peak Performance Requirement
A Peak operating state may impose higher Resource-performance requirements.
92. Peak Functional State
The function responsible for Peak Demand should remain identifiable where possible.
93. Peak Operating State
Peak Demand may occur during:
Normal high load
Startup
Shutdown
Recovery
Emergency
Maintenance
Environmental extreme
Production surge
Workload surge
94. Startup Peak
Startup may create a temporary Peak higher than steady-state Demand.
This may be a valid Peak where Resource infrastructure must support it.
95. Recovery Peak
Recovery after failure or interruption may create elevated Demand.
96. Emergency Peak
Emergency operation may create Resource Demand outside normal ranges.
FDIM identifies the emergency function.
PKDM governs its Peak characteristics.
97. Fault-Induced Peak
A fault may cause Resource Demand to rise.
PKDM should preserve the fault condition rather than representing it automatically as normal Peak Demand.
98. Abnormal Peak
An abnormal Peak may be real without being representative of expected normal operation.
99. Peak Anomaly
A Peak Anomaly is a high Demand observation whose relationship to the governed Resource requirement is uncertain or inconsistent with established operating patterns.
100. Anomaly ≠ Invalid Peak
An anomalous Peak should be investigated.
It should not automatically be discarded.
101. Measurement Error
A high observation caused by measurement error must not become Peak Demand.
102. Data Quality
Peak Demand confidence depends upon the quality of the underlying Demand data.
103. Missing Peak Data
Missing data during a likely Peak interval may prevent a sufficient Peak determination.
104. Peak Evidence-Limited State
PKDM should preserve an Evidence-Limited state where Peak Demand cannot be established reliably.
105. Peak Conflict
Peak Conflict exists where credible evidence supports materially different Peak Demand states.
106. Peak Conflict Resolution
Canonical logic:
**Peak Evidence A
Peak Evidence B → Demand Identity Check → Function Check → Measurement Interval Check → Time Check → Duration Check → Location Check → Operating-State Check → Evidence Quality Check → Resolution or Preserved Conflict**
107. Peak Uncertainty
Peak uncertainty may concern:
Magnitude; time; duration; frequency; function; location; measurement interval; future conditions.
108. Peak Range
Where exact Peak Demand cannot be justified, PKDM may establish a governed Peak range.
109. Peak Confidence Boundary
A numerically exact Peak value should not imply greater evidentiary confidence than the underlying evidence supports.
Numerical Precision ≠ Peak Certainty.
110. Peak Sufficiency
Peak Demand is sufficiently governed when the Peak representation provides adequate evidence for downstream concurrency and Demand consolidation governance.
111. Peak Demand Decision States
At minimum:
Peak Demand Established
Recurring Peak Established
Conditional Peak Established
Partially Established Peak
Peak Evidence-Limited
Peak Conflicted
Peak Unknown
Peak Unresolved
112. Peak Demand Profile
The principal PKDM output is the:
Peak Demand Profile
113. Minimum Peak Demand Profile Fields
At minimum:
Demand ID
CRDM Profile Reference
FDIM Profile Reference
Resource ID
Function ID where relevant
Peak Demand Quantity / Capacity / Rate
Native Measurement
Peak Measurement Interval
Peak Time / Window
Peak Duration
Peak Frequency
Peak Recurrence State
Peak Location
Peak Operating State
Peak Type
Evidence Basis
Evidence Time
Peak Uncertainty
Peak Sufficiency State
Version:
114. Peak Type
PKDM may classify Peak Demand as:
Observed Peak
Recurring Peak
Seasonal Peak
Operational Peak
Conditional Peak
Event-Driven Peak
Emergency Peak
Predicted Peak
Simulated Peak
Planned Peak
Anomalous Peak
115. Peak Recurrence State
Possible recurrence states include:
Non-Recurring
Irregular
Recurring
Periodic
Seasonal
Condition-Triggered
Unknown
116. Peak Demand and Functional Demand
PKDM should preserve the FDIM functional relationship.
A Peak without functional context may remain insufficient where function materially affects downstream governance.
117. Peak Demand and Core Demand
Peak Demand does not replace the Core Resource Demand Profile.
It adds the upper Demand condition.
118. Peak vs Normal Demand
A complete Demand representation may require both:
Normal / Core Demand
and:
Peak Demand.
119. Peak Demand and Concurrency
PKDM establishes Peak Demand for individual governed Demand structures.
CPDM determines whether separate Demand objects or their Peaks actually occur together.
120. Peak Summation Boundary
Sum of Individual Peaks ≠ Consolidated Peak Demand by definition.
121. Peak Demand and Resource Availability
PKDM does not reduce Peak Demand merely because Resource capacity cannot satisfy it.
122. Unserved Peak Demand
Peak Demand may exceed available Resource capacity.
The Peak should remain represented where evidence supports it.
123. Peak Suppression
Observed Resource Consumption may fail to reveal true Peak Demand when Resource Availability constrains Consumption.
Observed Peak Consumption ≠ Peak Demand where Demand is supply-constrained.
124. Latent Peak Demand
A system may possess Peak Resource requirements that cannot be observed directly because Resource capacity is insufficient.
Latent Peak Demand requires evidence and should not be assumed.
125. Peak Demand and Dependency
Peak magnitude does not establish Resource Dependency severity.
High Peak Demand ≠ High Dependency Severity.
126. Peak Demand and Criticality
A small Peak may support a critical function.
A large Peak may support a deferrable function.
High Peak Demand ≠ High Criticality.
127. Peak Demand and Access
Peak Demand does not establish Resource Access authorization.
128. Peak Demand and Priority
A high Peak does not automatically create high Resource Priority.
Peak Magnitude ≠ Allocation Priority.
129. Peak Demand and Allocation
PKDM does not allocate capacity to cover Peak Demand.
130. Peak Demand and Consumption
Peak Consumption may provide evidence.
It is not automatically Peak Demand.
131. Peak Demand and Scarcity
A Peak exceeding available capacity may contribute to downstream Scarcity governance.
PKDM does not establish Scarcity State.
132. Peak Demand and Sustainability
A system may be capable of supporting occasional Peaks while being unable to sustain them continuously.
Peak Feasibility ≠ Long-Term Sustainability.
133. Peak Demand and Value
High-Value activity may create Peak Demand.
Value does not redefine the Resource requirement.
VEGA™ retains relevant Value Governance.
134. Peak Demand and Resilience
Resource capacity reserved for resilience may affect whether Peak Demand can be served.
PKDM does not determine resilience sufficiency.
135. Peak Change
Peak Demand may change because of:
workload change; function change; system expansion; efficiency change;
climate or environmental change; operating-state change; technical reconfiguration; Resource substitution.
136. Peak Reassessment Trigger
PKDM reassessment should occur following material:
CRDM revision; FDIM revision; new Peak measurement; new operating state; system reconfiguration; workload change; function change; new seasonal pattern; new event pattern; evidence conflict; measurement-method change; evidence expiry.
137. Peak Reassessment Logic
Canonical logic:
Existing Peak Demand Profile → New Evidence / Material Change → Peak Impact Test → Peak Retained or Revised → Version Update → CPDM / DCMM Reassessment
138. Peak Versioning
Material Peak changes should produce a new governed profile version.
139. Historical Peak Version
Previous Peak Demand Profiles should remain distinguishable from current Peak Demand.
140. Peak Trend
Multiple governed Peak Demand Profiles may reveal increasing, decreasing, or changing Peak patterns.
Trend interpretation should preserve the underlying measurement conditions.
141. Peak Comparability
Peak values should be compared only where relevant:
Resource; measurement unit; measurement interval; function;
location; operating state
are sufficiently compatible.
142. Measurement Interval Comparability
A 1-minute Peak and a 1-hour Peak are not directly equivalent merely because they use the same unit.
143. Cross-Location Peak Comparability
Peak Demand at different locations may reflect materially different Resource System conditions.
144. Cross-Resource Peak Boundary
Peak Demand should remain Resource-specific.
Different Resource Peaks should not be normalized into physical equivalence merely for convenience.
145. Peak Demand Integrity Principle
Peak Demand must represent the highest materially relevant Resource requirement under defined conditions, not simply the largest number available in the dataset.
146. Temporal Integrity Principle
A Peak without its measurement interval, timing, and duration is an incomplete Resource Demand representation.
147. Functional Integrity Principle
Where function materially explains the Peak, Peak Demand must remain traceable to the function that creates it.
148. Evidence Integrity Principle
An extreme observation does not become governed Peak Demand until its Resource meaning is sufficiently evidenced.
149. Minimum Implementation Framework
A minimum operational PKDM implementation should contain eight governed layers.
Layer 1 — Demand Inputs
Receive:
Core Resource Demand Profile Functional Demand Profile Demand measurements / evidence
Layer 2 — Peak Interval
Define:
Governance interval Measurement interval Peak Window
Layer 3 — Peak Detection
Identify:
Candidate Peak Peak magnitude Peak time Peak duration
Layer 4 — Peak Context
Determine:
Function Location Operating state Recurrence Seasonality Event condition
Layer 5 — Peak Integrity
Assess:
Spike vs Peak Anomaly Measurement error Historical relevance Supply suppression Non-simultaneous components
Layer 6 — Evidence
Preserve:
Evidence source Measurement resolution Evidence time Provenance Conflict
Layer 7 — Uncertainty & Sufficiency
Determine:
Peak uncertainty Peak Decision State Peak Sufficiency
Layer 8 — Governed Output
Produce:
Peak Demand Profile Version Known limitations Reassessment triggers CPDM handoff state
Minimum machine-readable logic:
Demand Profile → Governance Interval → Measurement Interval → Candidate Peak[] → Peak Magnitude → Peak Time → Peak Duration → Function / Location / Operating State → Recurrence → Integrity Checks[] → Evidence[] → Uncertainty[] → Peak State → Sufficiency → Peak Demand Profile
150. Minimum Decision States
At minimum:
Peak Demand Established
Recurring Peak Established
Conditional Peak Established
Partially Established Peak
Peak Evidence-Limited
Peak Conflicted
Peak Unknown
Peak Unresolved
151. Minimum Evidence Path
Where Peak Demand cannot be sufficiently established:
Peak Unresolved → Material Peak Evidence Gap → Minimum Evidence Requirement → Evidence Acquisition → Peak Reassessment → Updated Peak Demand Profile
The objective is sufficient Peak evidence for downstream governance, not the collection of every possible Demand measurement.
152. Minimum Reassessment Framework
At minimum:
Current Peak Demand Profile → New Evidence / Material Change → Peak Impact Test → Peak State Retained or Revised
→ Profile Version Update → CPDM / DCMM Reassessment
153. Governance Requirements
A conforming PKDM implementation must:
1. receive governed Core Demand input; 2. receive Functional Demand input where applicable; 3. define the relevant Peak governance interval; 4. define the measurement interval; 5. identify candidate Peaks; 6. establish Peak magnitude; 7. establish Peak timing; 8. establish Peak duration; 9. preserve Peak function where material; 10. preserve Peak location where material; 11. preserve Peak operating state; 12. distinguish Peak from average Demand; 13. distinguish Peak from installed capability; 14. distinguish Peak from theoretical maximum; 15. distinguish Peak from requested capacity; 16. distinguish recurring from isolated Peaks; 17. distinguish observed from predicted Peaks; 18. distinguish observed from simulated Peaks; 19. identify anomalies; 20. assess measurement resolution; 21. preserve Peak evidence provenance; 22. preserve Peak evidence freshness; 23. support Peak ranges where necessary; 24. preserve material uncertainty; 25. preserve Peak conflict; 26. prevent automatic summation of non-simultaneous Peaks; 27. preserve supply-suppressed Demand where evidenced; 28. support reassessment; 29. support versioning; 30. produce a governed Peak Demand Profile.
154. Governance Logic
Canonical PKDM logic:
**Core Resource Demand Profile
Functional Demand Profile → Peak Governance Interval → Measurement Interval → Candidate Peak Identification → Peak Magnitude → Peak Time → Peak Duration → Functional Attribution → Location → Operating State → Recurrence / Seasonality / Event Condition → Spike / Anomaly / Error Check → Evidence → Uncertainty → Sufficiency → Peak Demand Profile**
Where Peak is unresolved:
Candidate Peak → Evidence Gap → Minimum Evidence Requirement → Evidence Acquisition → Peak Reassessment
Where Peak changes:
Existing Peak Demand Profile → Material Change → Peak Impact Test → Revised Peak Demand → Version Update → Downstream Reassessment
155. Governance Outputs
PKDM may produce:
Peak Demand Profile
Peak Demand Quantity
Peak Capacity
Peak Rate
Peak Measurement Interval
Peak Window
Peak Time
Peak Duration
Peak Frequency
Peak Recurrence State
Peak Seasonal State
Peak Functional State
Peak Location State
Peak Operating State
Peak Type
Peak Anomaly State
Peak Evidence State
Peak Conflict State
Peak Uncertainty State
Peak Sufficiency State
Peak Version
Reassessment Trigger
CPDM Handoff State
156. Downstream Release Condition
PKDM output may proceed into CPDM where Peak Demand is sufficiently established for concurrency analysis or where remaining Peak uncertainty can legitimately remain explicit.
Progression does not erase Peak uncertainty.
157. Failure Conditions
PKDM should not be considered sufficiently completed where:
the largest recorded number is automatically treated as Peak Demand; measurement interval is undefined; Peak duration is materially unknown; Peak timing is ignored; average Demand is substituted for Peak Demand; installed capability is treated as Peak Demand; theoretical maximum is treated as Peak Demand; requested capacity is treated as validated Peak Demand; historical Peak is treated automatically as current Peak; predicted Peak is represented as observed Peak; simulated Peak is represented as observed Peak; an instantaneous spike is treated automatically as a materially relevant Peak; measurement error is not considered; measurement resolution hides material Peaks; transient noise is treated as operational Peak Demand; functional Peak and System Peak are confused; non-simultaneous component Peaks are added automatically; supply-constrained Consumption is treated automatically as Peak Demand; Peak evidence conflict is hidden; Peak uncertainty is hidden; Peak Demand is treated as Criticality; Peak Demand is treated as Priority; Peak Demand is treated as Allocation.
158. Use Case 1 — AI Data Center Electricity Peak Demand
FDIM establishes normal electricity Demand across an AI data center:
AI compute → 41 MW
Cooling → 10 MW
Storage & networking → 3 MW
Shared infrastructure → 4 MW
Normal combined Demand is approximately:
58 MW.
Operational telemetry records several short observations above:
72 MW.
PKDM determines that some are sub-second startup transients while recurring high-load AI training windows produce:
66–68 MW
for:
35–50 minutes
during defined workload periods.
The governed Peak Demand is therefore not established simply by selecting the maximum 72 MW observation.
PKDM preserves:
Peak magnitude; measurement interval; duration; function; operating state; recurrence; evidence.
The highest electricity reading is not automatically the data center's governed Peak Demand.
159. Use Case 2 — Regional Water Peak Demand
A region has average water Demand of:
120,000 m³/day.
During summer, Resource Demand regularly rises.
Historical records include an isolated maximum of:
182,000 m³/day
during an exceptional event.
Recurring summer high-demand periods show:
155,000–165,000 m³/day
under comparable current operating conditions.
PKDM distinguishes:
annual average Demand; recurring seasonal Peak; isolated historical extreme; future predicted Peak.
The resulting Peak Demand Profile preserves the relevant seasonal Peak range and the exceptional event separately.
An exceptional historical maximum does not automatically define the Resource capacity required for every future Peak condition.
160. Critical Distinctions
Maximum Observed Value ≠ Governed Peak Demand by definition
Demand Spike ≠ Governed Peak Demand by definition
Seasonal Peak Demand ≠ Annual Average Demand
Functional Peak ≠ System Peak
Peak A + Peak B ≠ System Peak by definition
Average Demand ≠ Peak Demand
Installed Capability ≠ Peak Demand
Theoretical Maximum ≠ Governed Peak Demand
Contracted Capacity ≠ Peak Demand
Historical Peak ≠ Current Peak Demand by definition
Predicted Peak Demand ≠ Current Peak Demand
Simulated Peak Demand ≠ Observed Peak Demand
Planned Peak Demand ≠ Current Peak Demand
Same Peak Magnitude ≠ Same Peak Condition
End-Use Peak Demand ≠ Source Peak Demand by definition
Local Peak Demand ≠ Aggregate Peak Demand
Numerical Precision ≠ Peak Certainty
Sum of Individual Peaks ≠ Consolidated Peak Demand by definition
Observed Peak Consumption ≠ Peak Demand where Demand is supply-constrained
High Peak Demand ≠ High Dependency Severity
High Peak Demand ≠ High Criticality
Peak Magnitude ≠ Allocation Priority
Peak Feasibility ≠ Long-Term Sustainability
161. Cross-Architecture Boundary
PKDM governs Peak Resource Demand within RDGS.
It may consume evidence or outputs from:
CRDM for Core Resource Demand; FDIM for Functional Demand; RACS for Resource Availability & Capacity context; PGA™ for predicted Peak Demand; SIMULOS® for simulated Peak Demand; ORA™ for operational Peak evidence; VEGA™ for relevant efficiency and Resource-use information; specialized Resource systems for Resource-specific Peak mechanisms.
It does not absorb their governed mechanisms.
162. Cross-Architecture Mechanism Principle
An operational mechanism may produce inputs for multiple governance architectures, but it belongs only to the architecture whose governed domain includes that mechanism itself. Other architectures govern only its domain- specific relevance or consequences.
A workload scheduler may create compute Peaks.
Weather conditions may contribute to cooling or electricity Peaks.
Production cycles may create material or energy Peaks.
Hydrological or infrastructure conditions may influence water Demand Peaks.
PKDM governs the resulting Peak Resource Demand representation.
It does not absorb the mechanisms producing those conditions.
163. Canonical Boundary
PKDM governs how the highest materially relevant Resource Demand within a defined governance interval is identified, measured, temporally bounded, functionally attributed, evidenced, qualified, and reassessed, including its magnitude, timing, duration, recurrence, operating state, location, uncertainty, and evidentiary status.
It does not determine Demand concurrency across independent Demand objects, final Demand consolidation, Resource Dependency, Criticality, Access authorization, Priority, Allocation, Consumption governance, Scarcity response, Resilience, or Sustainability.
Its principal governed output is the Peak Demand Profile used by subsequent RDGS Core Modules.
164. Canonical Closing Statement
Peak Demand is not simply the largest number found in a Resource dataset.
PKDM establishes which high-demand condition actually matters — how much Resource is required, when the Peak occurs, how long it lasts, what creates it, whether it recurs, and what evidence proves that the Peak belongs to the governed Resource reality.