[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7AR9FMHMHFTGER6NTAY2WC6":3,"skill-same:01M7AR9FMHMHFTGER6NTAY2WC6":48},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":29,"ownerHtmlUrl":30,"ownerBlogUrl":31,"ownerDescription":32,"updatedAt":33,"install":34,"resources":47},"01M7AR9FMHMHFTGER6NTAY2WC6","power-inverters-storage-markets-and-datacenters",null,"Use when working on the modern grid: inverters, renewables and the inertia problem including grid-following versus grid-forming and other inverter-based-resource realities, storage technologies and their roles, markets and dispatch, writing grid software including the character of the domain and why OT security is not IT security, and datacenter power from the facility down to what software engineers actually control.","the-vibey-project\u002Fvibey","the-vibey-project","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F329298758?v=4","01M7AJHGZ9722CTJ4JNQZVRH0Q","the vibey project","01M7AJHGZVMG2K7TGXQ6XFHVG3",5,"MIT","https:\u002F\u002Fgithub.com\u002Fthe-vibey-project\u002Fvibey\u002Fblob\u002Fdevelop\u002Fsrc\u002Fvibey_tools\u002Fskills\u002Fplugins\u002Fpower-engineering\u002Fskills\u002Fpower-inverters-storage-markets-and-datacenters\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: power-inverters-storage-markets-and-datacenters\ndescription: \"Use when working on the modern grid: inverters, renewables and the inertia problem including grid-following versus grid-forming and other inverter-based-resource realities, storage technologies and their roles, markets and dispatch, writing grid software including the character of the domain and why OT security is not IT security, and datacenter power from the facility down to what software engineers actually control.\"\n---\n\n# Power Engineering: Inverters and Renewables, Storage, Markets, Grid Software, and Datacenter Power\n\n> **Part 4 of 5** of the *Power Engineering* reference (plugin `power-engineering`), covering §8–§12. Sibling skills: `power-ac-fundamentals-generation-and-grid` (§0–§3), `power-system-analysis-and-protection` (§4–§5), `power-scada-ems-and-protocols` (§6–§7), `power-reference` (§13–§18). Section numbers are shared across the set; a reference written as §N → `skill` points into that sibling skill.\n>\n> **Currency:** Circuit theory and power system analysis are settled; the inverter-dominated grid and datacenter load growth moved fast. See §15 → `power-reference` for both, dated.\n\n> **Scope.** Complements an electrical-engineering reference, which is circuit-level —\n> components, op-amps, PCB layout, signal integrity. ⚠️ **This is grid scale: kilovolts\n> and megawatts, and the software that runs it.**\n>\n> **⚠️ GOTCHA** boxes mark what kills people, destroys equipment, or causes blackouts.\n>\n> **The three ideas that organize the whole field:**\n> 1. **⚠️ Generation must equal load, continuously, everywhere.** The grid stores almost\n>    nothing. **Frequency IS the balance signal** — it falls when load exceeds generation\n>    and rises when it doesn't, in real time, across a continent (§1.4 → `power-ac-fundamentals-generation-and-grid`).\n> 2. **⚠️ Reactive power is not \"wasted\" power — it's a separate commodity that must also\n>    balance, and it's local.** Real power flows across a system; reactive power doesn't\n>    travel well, so voltage is a local problem and frequency is a global one (§1.2 → `power-ac-fundamentals-generation-and-grid`).\n> 3. **⚠️ Protection is the fastest software in the system and it acts on trust.** A relay\n>    decides in milliseconds to disconnect equipment, and it must be right — a false trip\n>    causes an outage, a missed trip destroys equipment or kills someone (§5 → `power-system-analysis-and-protection`).\n\n---\n\n## §8. Inverters, Renewables, and the Inertia Problem\n\n**⚠️ This is the defining engineering transition in power systems, and it is not primarily\nabout intermittency — it's about the loss of physics-based stabilization.**\n\n### 8.1 The mechanism\n**A synchronous generator's rotating mass stores kinetic energy that opposes frequency\nchange automatically.** ⚠️ **As one source puts it well: the beauty of that system was its\nsimplicity — the stored rotational energy required no control systems, no communication\nnetworks, and no human intervention.**\n\n**⚠️ Replace those machines with inverter-based resources (IBRs) and that mechanical\nbuffer disappears.** **Documented consequences:**\n- **Reduced inertia → larger frequency deviations and higher RoCoF** for the same\n  disturbance.\n- **⚠️ Reduced short-circuit strength → falling Short-Circuit Ratio (SCR)**, which breaks\n  protection (§5 → `power-system-analysis-and-protection`) and can cause grid-following inverters to lose synchronization\n  entirely.\n- **Subsynchronous resonance and oscillation risk** from converter control interactions.\n\n### 8.2 Grid-following vs grid-forming\n**⚠️ The distinction to understand:**\n- **Grid-following (GFL)** — ⚠️ **operates as a controlled current source, deriving\n  synchronization from grid voltage via a PLL** and injecting commanded P and Q.\n  **This worked precisely because the grid's stability was guaranteed by other means.**\n  ⚠️ **The paradox that's now acute: GFL's own success displaced the machines that made it\n  viable.**\n- **Grid-forming (GFM)** — ⚠️ **operates as a voltage source, generating the frequency and\n  amplitude reference rather than following one.** Can run islanded, provides **synthetic\n  inertia**, primary frequency response, voltage regulation, and ride-through, and\n  **improves stability under low SCR.** Some can black start, with additional design work\n  for inrush current.\n\n**⚠️ Control approaches**: droop, **virtual synchronous machine (VSM) \u002F virtual synchronous\ngenerator** control, and **adaptive inertia injection with virtual damping** — which points\nat something conceptually important: ⚠️ **future grids may be intentionally designed around\nthe fast, programmable response of GFM inverters rather than trying to replicate\nrotating-machine dynamics.** **Stability through software-defined control rather than\ninertia-heavy mechanical systems.**\n\n> **⚠️ GOTCHA — GFM inverters are not the silver bullet they're sometimes presented as,\n> and the deployment evidence is sobering.** ⚠️ **In the UK's Stability Pathfinder\n> procurement rounds, GFM inverters were largely unsuccessful in winning contracts — only\n> around 12% of the UK's contracted inertia will be met by GFM inverters by 2026**, with\n> the rest going to **synchronous machines, dominated by synchronous condensers.**\n> ⚠️ **A synchronous condenser is a spinning machine that generates no power — it exists\n> purely to provide inertia and reactive support. The market's revealed preference has\n> been to add back rotating mass.** **Germany's 2026 market-based inertia procurement,\n> which differentiates remuneration by technology type, may produce a different answer —\n> and it's genuinely uncertain whether GFM remuneration will be sufficient.**\n\n### 8.3 Other IBR realities\n**Curtailment**, **the duck curve** (⚠️ **midday solar depresses net load, then a steep\nevening ramp — the ramp rate is the operational problem, not the energy**), **forecasting**\nas a first-class operational input, and ⚠️ **hosting capacity limits on distribution\nfeeders — reverse power flow from rooftop solar breaks assumptions built into voltage\nregulation and protection.**\n\n**⚠️ Standards are catching up**: **IEEE 1547** for DER interconnection, **IEEE 2800** for\ntransmission-connected IBRs, and NERC guideline revision work explicitly addressing IBR\nfault performance. ⚠️ **Interconnection requests in 2026 increasingly ask whether equipment\nis grid-forming capable.**\n\n---\n\n## §9. Storage\n\n| Technology | Duration | ⚠️ Notes |\n|---|---|---|\n| **Li-ion BESS** | ⚠️ **~1–4 h** | Dominant; fast, and duration-limited |\n| **Pumped hydro** | 8–24 h+ | ⚠️ **~95% of world storage capacity; geography-limited** |\n| **Flow batteries** | 4–12 h | Decoupled power and energy |\n| **Compressed air, thermal** | Long | Niche |\n| **Hydrogen** | Seasonal | ⚠️ **Poor round-trip efficiency** |\n\n**⚠️ Batteries are inverter-interfaced (§8), which means their grid services are a software\nquestion**: frequency regulation (⚠️ **the highest-value early application, because they're\nfaster than any generator**), energy arbitrage, capacity, **synthetic inertia via GFM\ncontrol**, black start, and **T&D deferral.**\n\n**⚠️ The one that matters for software**: **state of charge is a hard constraint that\ncouples decisions across time.** A battery dispatched greedily for regulation revenue can\nbe empty when the capacity obligation lands. **Every storage optimization is a temporal\none, and cycling degrades the asset — so the objective function has to include\ndegradation cost or it will destroy the battery profitably.**\n\n---\n\n## §10. Markets and Dispatch\n\n**Unit commitment** — ⚠️ **which units to turn on over the next day, a mixed-integer\nprogram with minimum up\u002Fdown times and startup costs.**\n**Economic dispatch** — how much from each committed unit, continuously.\n**Optimal power flow (OPF)** — ⚠️ **dispatch subject to the physical network constraints of\n§4.1 → `power-system-analysis-and-protection`.** **AC OPF is non-convex and hard; DC OPF is what most markets actually clear on.**\n\n**LMP (locational marginal price)** decomposes into **energy + congestion + losses** —\n⚠️ **which is why prices differ between buses, and why congestion is visible as a price\nsignal rather than only as an engineering limit.** **Negative prices occur** when\nmust-run generation and inflexible renewables exceed load.\n\n**Market structure**: day-ahead and real-time, **ancillary services** (regulation, spinning\nand non-spinning reserve, voltage support, black start — ⚠️ **and increasingly inertia,\n§8.2**), and capacity markets.\n\n**⚠️ For a software engineer, the notable property**: this is a **large-scale optimization\nrunning on a schedule with hard deadlines and real money attached.** ⚠️ **A market\nclearing that doesn't converge in time is an operational emergency, not a failed job.**\n\n---\n\n## §11. Writing Grid Software\n\n### 11.1 The character of the domain\n**⚠️ Timescales span twelve orders of magnitude**, and which one you're in dictates\neverything:\n```\nµs–ms      protection, GOOSE, sampled values     ⚠️ hard real-time, safety-critical\nms–s       inverter control, AGC\ns–min      SCADA, state estimation\nmin–h      dispatch, markets\nh–yr       planning\n```\n**⚠️ Reliability expectations are extreme**: control-room systems target very high\navailability, field devices run for 20+ years, and **the cost of a wrong answer is\nmeasured in outages and lives.** **This is much closer to avionics and automotive\npractice (see those references) than to web engineering.**\n\n### 11.2 ⚠️ Security — OT is not IT\n**NERC CIP** in North America is a mandatory, auditable, **fineable** standard covering\nasset identification, security management, personnel and training, electronic security\nperimeters, physical security, system security management, incident response, recovery,\nconfiguration change management, and supply chain risk.\n**⚠️ The OT\u002FIT differences that catch software engineers out:**\n- **Availability outranks confidentiality** — ⚠️ **the reverse of most IT threat models.**\n- **⚠️ You cannot patch on Tuesday.** Devices may not be patchable at all, and taking them\n  out of service requires a switching order.\n- **⚠️ Air gaps are largely mythical in practice** — segmentation, unidirectional gateways\n  and rigorous perimeter control are the real controls.\n- **Legacy protocols with no authentication** (§7 → `power-scada-ems-and-protocols`) mean **network position is\n  authorization**, which is exactly why segmentation carries the load.\n- ⚠️ **Ukraine 2015\u002F2016 and Industroyer\u002FCRASHOVERRIDE are the reference cases** — grid\n  malware that spoke the protocols in §7 → `power-scada-ems-and-protocols` natively.\n\n### 11.3 Practice\n**Testing**: simulation against a network model, **hardware-in-the-loop** with real relays\n(⚠️ **real-time digital simulators are standard for protection validation**), replay of\nrecorded disturbances, and **model validation against actual event data** — ⚠️ **which is\nwhere a lot of models are found wanting after a real disturbance.**\n**Tools**: **PSS\u002FE, PowerWorld, PSCAD\u002FEMTP** (⚠️ **electromagnetic transient simulation —\nrequired for inverter control studies, because phasor-domain tools miss the fast\ndynamics**), **OpenDSS** and **GridLAB-D** (distribution), **PYPOWER, pandapower, PowerModels.jl,\nMATPOWER** (⚠️ **the open research stack**), **GridPACK**, **Grid2Op** for RL work.\n**Data**: CIM (§7 → `power-scada-ems-and-protocols`), historians, PMU archives, and ⚠️ **an obsession with time\nsynchronization — PTP\u002FIEEE 1588 and GPS, because sequence-of-events analysis after a\ndisturbance depends entirely on trustworthy timestamps.**\n\n---\n\n## §12. Datacenter Power\n\n**⚠️ The part of this document most software engineers will actually touch — and the\nindustry has crossed a threshold where compute demand is now a first-order power system\nproblem** (§15.2 → `power-reference`).\n\n### 12.1 The facility\n```\nUtility feed → transformer → switchgear → UPS → PDU → rack PDU → PSU → server\n                     ↕                      ↕\n                  generator             battery\u002Fflywheel\n```\n**Redundancy notation**: **N** (no redundancy), **N+1**, **2N** (⚠️ **fully duplicated**),\n**2N+1**. **Tier I–IV** (Uptime Institute) — ⚠️ **Tier III is concurrently maintainable,\nTier IV is fault tolerant, and the distinction is whether a single failure during\nmaintenance takes you down.**\n\n**UPS topologies**: double-conversion (⚠️ **best isolation, worst efficiency**), line-\ninteractive, and **eco\u002Fmulti-mode** which bypasses conversion when input is clean.\n**Generators** for extended outages (⚠️ **and the fuel contract is the real constraint,\nnot the generator**).\n\n**⚠️ PUE (Power Usage Effectiveness)** = total facility power \u002F IT equipment power.\n**1.0 is perfect; hyperscale runs near 1.1; older enterprise 1.5–2.0.**\n> **⚠️ GOTCHA — PUE measures facility overhead, not useful work.** ⚠️ **A facility at\n> PUE 1.05 running inefficient inference wastes more energy per useful output than a\n> facility at higher PUE running efficient workloads.** **PUE cannot see software\n> efficiency at all**, which is why \"tokens per watt\" style metrics are the ones that\n> matter to the people reading this. **Optimizing PUE while ignoring compute efficiency\n> is optimizing the denominator you don't control.**\n\n### 12.2 What software engineers control\n**⚠️ Rack density is the current design driver** — modern AI racks reach **~140 kW**,\nagainst a traditional ~5–15 kW, which is why **liquid cooling** moved from exotic to\nstandard. **⚠️ Air cooling runs out well below current GPU rack densities.**\n\n**Levers that are actually software decisions:**\n- **⚠️ Utilization.** An idle server draws a large fraction of peak. **Consolidation and\n  autoscaling are power engineering.**\n- **Efficiency per unit of work** — model choice, quantization, batching, caching.\n  ⚠️ **The largest lever, and invisible to every facility metric.**\n- **Carbon-aware scheduling** — ⚠️ **shift flexible work in time or geography toward\n  low-carbon grid conditions.** Real, and limited to genuinely deferrable workloads.\n- **⚠️ Demand flexibility** — and this is now a grid-interface question, not just an\n  internal one (§15.2 → `power-reference`).\n","# Power Engineering: Inverters and Renewables, Storage, Markets, Grid Software, and Datacenter Power\n\n> **Part 4 of 5** of the *Power Engineering* reference (plugin `power-engineering`), covering §8–§12. Sibling skills: `power-ac-fundamentals-generation-and-grid` (§0–§3), `power-system-analysis-and-protection` (§4–§5), `power-scada-ems-and-protocols` (§6–§7), `power-reference` (§13–§18). Section numbers are shared across the set; a reference written as §N → `skill` points into that sibling skill.\n>\n> **Currency:** Circuit theory and power system analysis are settled; the inverter-dominated grid and datacenter load growth moved fast. See §15 → `power-reference` for both, dated.\n\n> **Scope.** Complements an electrical-engineering reference, which is circuit-level —\n> components, op-amps, PCB layout, signal integrity. ⚠️ **This is grid scale: kilovolts\n> and megawatts, and the software that runs it.**\n>\n> **⚠️ GOTCHA** boxes mark what kills people, destroys equipment, or causes blackouts.\n>\n> **The three ideas that organize the whole field:**\n> 1. **⚠️ Generation must equal load, continuously, everywhere.** The grid stores almost\n>    nothing. **Frequency IS the balance signal** — it falls when load exceeds generation\n>    and rises when it doesn't, in real time, across a continent (§1.4 → `power-ac-fundamentals-generation-and-grid`).\n> 2. **⚠️ Reactive power is not \"wasted\" power — it's a separate commodity that must also\n>    balance, and it's local.** Real power flows across a system; reactive power doesn't\n>    travel well, so voltage is a local problem and frequency is a global one (§1.2 → `power-ac-fundamentals-generation-and-grid`).\n> 3. **⚠️ Protection is the fastest software in the system and it acts on trust.** A relay\n>    decides in milliseconds to disconnect equipment, and it must be right — a false trip\n>    causes an outage, a missed trip destroys equipment or kills someone (§5 → `power-system-analysis-and-protection`).\n\n---\n\n## §8. Inverters, Renewables, and the Inertia Problem\n\n**⚠️ This is the defining engineering transition in power systems, and it is not primarily\nabout intermittency — it's about the loss of physics-based stabilization.**\n\n### 8.1 The mechanism\n**A synchronous generator's rotating mass stores kinetic energy that opposes frequency\nchange automatically.** ⚠️ **As one source puts it well: the beauty of that system was its\nsimplicity — the stored rotational energy required no control systems, no communication\nnetworks, and no human intervention.**\n\n**⚠️ Replace those machines with inverter-based resources (IBRs) and that mechanical\nbuffer disappears.** **Documented consequences:**\n- **Reduced inertia → larger frequency deviations and higher RoCoF** for the same\n  disturbance.\n- **⚠️ Reduced short-circuit strength → falling Short-Circuit Ratio (SCR)**, which breaks\n  protection (§5 → `power-system-analysis-and-protection`) and can cause grid-following inverters to lose synchronization\n  entirely.\n- **Subsynchronous resonance and oscillation risk** from converter control interactions.\n\n### 8.2 Grid-following vs grid-forming\n**⚠️ The distinction to understand:**\n- **Grid-following (GFL)** — ⚠️ **operates as a controlled current source, deriving\n  synchronization from grid voltage via a PLL** and injecting commanded P and Q.\n  **This worked precisely because the grid's stability was guaranteed by other means.**\n  ⚠️ **The paradox that's now acute: GFL's own success displaced the machines that made it\n  viable.**\n- **Grid-forming (GFM)** — ⚠️ **operates as a voltage source, generating the frequency and\n  amplitude reference rather than following one.** Can run islanded, provides **synthetic\n  inertia**, primary frequency response, voltage regulation, and ride-through, and\n  **improves stability under low SCR.** Some can black start, with additional design work\n  for inrush current.\n\n**⚠️ Control approaches**: droop, **virtual synchronous machine (VSM) \u002F virtual synchronous\ngenerator** control, and **adaptive inertia injection with virtual damping** — which points\nat something conceptually important: ⚠️ **future grids may be intentionally designed around\nthe fast, programmable response of GFM inverters rather than trying to replicate\nrotating-machine dynamics.** **Stability through software-defined control rather than\ninertia-heavy mechanical systems.**\n\n> **⚠️ GOTCHA — GFM inverters are not the silver bullet they're sometimes presented as,\n> and the deployment evidence is sobering.** ⚠️ **In the UK's Stability Pathfinder\n> procurement rounds, GFM inverters were largely unsuccessful in winning contracts — only\n> around 12% of the UK's contracted inertia will be met by GFM inverters by 2026**, with\n> the rest going to **synchronous machines, dominated by synchronous condensers.**\n> ⚠️ **A synchronous condenser is a spinning machine that generates no power — it exists\n> purely to provide inertia and reactive support. The market's revealed preference has\n> been to add back rotating mass.** **Germany's 2026 market-based inertia procurement,\n> which differentiates remuneration by technology type, may produce a different answer —\n> and it's genuinely uncertain whether GFM remuneration will be sufficient.**\n\n### 8.3 Other IBR realities\n**Curtailment**, **the duck curve** (⚠️ **midday solar depresses net load, then a steep\nevening ramp — the ramp rate is the operational problem, not the energy**), **forecasting**\nas a first-class operational input, and ⚠️ **hosting capacity limits on distribution\nfeeders — reverse power flow from rooftop solar breaks assumptions built into voltage\nregulation and protection.**\n\n**⚠️ Standards are catching up**: **IEEE 1547** for DER interconnection, **IEEE 2800** for\ntransmission-connected IBRs, and NERC guideline revision work explicitly addressing IBR\nfault performance. ⚠️ **Interconnection requests in 2026 increasingly ask whether equipment\nis grid-forming capable.**\n\n---\n\n## §9. Storage\n\n| Technology | Duration | ⚠️ Notes |\n|---|---|---|\n| **Li-ion BESS** | ⚠️ **~1–4 h** | Dominant; fast, and duration-limited |\n| **Pumped hydro** | 8–24 h+ | ⚠️ **~95% of world storage capacity; geography-limited** |\n| **Flow batteries** | 4–12 h | Decoupled power and energy |\n| **Compressed air, thermal** | Long | Niche |\n| **Hydrogen** | Seasonal | ⚠️ **Poor round-trip efficiency** |\n\n**⚠️ Batteries are inverter-interfaced (§8), which means their grid services are a software\nquestion**: frequency regulation (⚠️ **the highest-value early application, because they're\nfaster than any generator**), energy arbitrage, capacity, **synthetic inertia via GFM\ncontrol**, black start, and **T&D deferral.**\n\n**⚠️ The one that matters for software**: **state of charge is a hard constraint that\ncouples decisions across time.** A battery dispatched greedily for regulation revenue can\nbe empty when the capacity obligation lands. **Every storage optimization is a temporal\none, and cycling degrades the asset — so the objective function has to include\ndegradation cost or it will destroy the battery profitably.**\n\n---\n\n## §10. Markets and Dispatch\n\n**Unit commitment** — ⚠️ **which units to turn on over the next day, a mixed-integer\nprogram with minimum up\u002Fdown times and startup costs.**\n**Economic dispatch** — how much from each committed unit, continuously.\n**Optimal power flow (OPF)** — ⚠️ **dispatch subject to the physical network constraints of\n§4.1 → `power-system-analysis-and-protection`.** **AC OPF is non-convex and hard; DC OPF is what most markets actually clear on.**\n\n**LMP (locational marginal price)** decomposes into **energy + congestion + losses** —\n⚠️ **which is why prices differ between buses, and why congestion is visible as a price\nsignal rather than only as an engineering limit.** **Negative prices occur** when\nmust-run generation and inflexible renewables exceed load.\n\n**Market structure**: day-ahead and real-time, **ancillary services** (regulation, spinning\nand non-spinning reserve, voltage support, black start — ⚠️ **and increasingly inertia,\n§8.2**), and capacity markets.\n\n**⚠️ For a software engineer, the notable property**: this is a **large-scale optimization\nrunning on a schedule with hard deadlines and real money attached.** ⚠️ **A market\nclearing that doesn't converge in time is an operational emergency, not a failed job.**\n\n---\n\n## §11. Writing Grid Software\n\n### 11.1 The character of the domain\n**⚠️ Timescales span twelve orders of magnitude**, and which one you're in dictates\neverything:\n```\nµs–ms      protection, GOOSE, sampled values     ⚠️ hard real-time, safety-critical\nms–s       inverter control, AGC\ns–min      SCADA, state estimation\nmin–h      dispatch, markets\nh–yr       planning\n```\n**⚠️ Reliability expectations are extreme**: control-room systems target very high\navailability, field devices run for 20+ years, and **the cost of a wrong answer is\nmeasured in outages and lives.** **This is much closer to avionics and automotive\npractice (see those references) than to web engineering.**\n\n### 11.2 ⚠️ Security — OT is not IT\n**NERC CIP** in North America is a mandatory, auditable, **fineable** standard covering\nasset identification, security management, personnel and training, electronic security\nperimeters, physical security, system security management, incident response, recovery,\nconfiguration change management, and supply chain risk.\n**⚠️ The OT\u002FIT differences that catch software engineers out:**\n- **Availability outranks confidentiality** — ⚠️ **the reverse of most IT threat models.**\n- **⚠️ You cannot patch on Tuesday.** Devices may not be patchable at all, and taking them\n  out of service requires a switching order.\n- **⚠️ Air gaps are largely mythical in practice** — segmentation, unidirectional gateways\n  and rigorous perimeter control are the real controls.\n- **Legacy protocols with no authentication** (§7 → `power-scada-ems-and-protocols`) mean **network position is\n  authorization**, which is exactly why segmentation carries the load.\n- ⚠️ **Ukraine 2015\u002F2016 and Industroyer\u002FCRASHOVERRIDE are the reference cases** — grid\n  malware that spoke the protocols in §7 → `power-scada-ems-and-protocols` natively.\n\n### 11.3 Practice\n**Testing**: simulation against a network model, **hardware-in-the-loop** with real relays\n(⚠️ **real-time digital simulators are standard for protection validation**), replay of\nrecorded disturbances, and **model validation against actual event data** — ⚠️ **which is\nwhere a lot of models are found wanting after a real disturbance.**\n**Tools**: **PSS\u002FE, PowerWorld, PSCAD\u002FEMTP** (⚠️ **electromagnetic transient simulation —\nrequired for inverter control studies, because phasor-domain tools miss the fast\ndynamics**), **OpenDSS** and **GridLAB-D** (distribution), **PYPOWER, pandapower, PowerModels.jl,\nMATPOWER** (⚠️ **the open research stack**), **GridPACK**, **Grid2Op** for RL work.\n**Data**: CIM (§7 → `power-scada-ems-and-protocols`), historians, PMU archives, and ⚠️ **an obsession with time\nsynchronization — PTP\u002FIEEE 1588 and GPS, because sequence-of-events analysis after a\ndisturbance depends entirely on trustworthy timestamps.**\n\n---\n\n## §12. Datacenter Power\n\n**⚠️ The part of this document most software engineers will actually touch — and the\nindustry has crossed a threshold where compute demand is now a first-order power system\nproblem** (§15.2 → `power-reference`).\n\n### 12.1 The facility\n```\nUtility feed → transformer → switchgear → UPS → PDU → rack PDU → PSU → server\n                     ↕                      ↕\n                  generator             battery\u002Fflywheel\n```\n**Redundancy notation**: **N** (no redundancy), **N+1**, **2N** (⚠️ **fully duplicated**),\n**2N+1**. **Tier I–IV** (Uptime Institute) — ⚠️ **Tier III is concurrently maintainable,\nTier IV is fault tolerant, and the distinction is whether a single failure during\nmaintenance takes you down.**\n\n**UPS topologies**: double-conversion (⚠️ **best isolation, worst efficiency**), line-\ninteractive, and **eco\u002Fmulti-mode** which bypasses conversion when input is clean.\n**Generators** for extended outages (⚠️ **and the fuel contract is the real constraint,\nnot the generator**).\n\n**⚠️ PUE (Power Usage Effectiveness)** = total facility power \u002F IT equipment power.\n**1.0 is perfect; hyperscale runs near 1.1; older enterprise 1.5–2.0.**\n> **⚠️ GOTCHA — PUE measures facility overhead, not useful work.** ⚠️ **A facility at\n> PUE 1.05 running inefficient inference wastes more energy per useful output than a\n> facility at higher PUE running efficient workloads.** **PUE cannot see software\n> efficiency at all**, which is why \"tokens per watt\" style metrics are the ones that\n> matter to the people reading this. **Optimizing PUE while ignoring compute efficiency\n> is optimizing the denominator you don't control.**\n\n### 12.2 What software engineers control\n**⚠️ Rack density is the current design driver** — modern AI racks reach **~140 kW**,\nagainst a traditional ~5–15 kW, which is why **liquid cooling** moved from exotic to\nstandard. **⚠️ Air cooling runs out well below current GPU rack densities.**\n\n**Levers that are actually software decisions:**\n- **⚠️ Utilization.** An idle server draws a large fraction of peak. **Consolidation and\n  autoscaling are power engineering.**\n- **Efficiency per unit of work** — model choice, quantization, batching, caching.\n  ⚠️ **The largest lever, and invisible to every facility metric.**\n- **Carbon-aware scheduling** — ⚠️ **shift flexible work in time or geography toward\n  low-carbon grid conditions.** Real, and limited to genuinely deferrable workloads.\n- **⚠️ Demand flexibility** — and this is now a grid-interface question, not just an\n  internal one (§15.2 → `power-reference`).\n",{"name":5,"description":7},"develop","ae32736a1aabddabca5d2c96d665aa0ebc7d8700","src\u002Fvibey_tools\u002Fskills\u002Fplugins\u002Fpower-engineering\u002Fskills\u002Fpower-inverters-storage-markets-and-datacenters",3,"https:\u002F\u002Fgithub.com\u002Fthe-vibey-project\u002Fvibey","https:\u002F\u002Fthe-vibey-project.github.io\u002Fvibey\u002F","https:\u002F\u002Fgithub.com\u002Fthe-vibey-project","https:\u002F\u002Fvibewithadam.matthewsteinberger.com","freedom for software engineers","2026-11-15 05:47:42",{"source":8,"skillName":5,"commands":35,"prompt":45,"zipAvailable":46},[36,39,42],{"tool":37,"command":38},"npx","npx skills add the-vibey-project\u002Fvibey --skill power-inverters-storage-markets-and-datacenters",{"tool":40,"command":41},"bunx","bunx skills add the-vibey-project\u002Fvibey --skill power-inverters-storage-markets-and-datacenters",{"tool":43,"command":44},"pnpm","pnpm dlx skills add the-vibey-project\u002Fvibey --skill power-inverters-storage-markets-and-datacenters","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fthe-vibey-project\u002Fvibey\u002Fblob\u002Fdevelop\u002Fsrc\u002Fvibey_tools\u002Fskills\u002Fplugins\u002Fpower-engineering\u002Fskills\u002Fpower-inverters-storage-markets-and-datacenters\u002FSKILL.md",true,[],[49,56,63,70,77,84],{"skillNo":50,"name":51,"nameZh":6,"description":52,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":53,"categories":54,"keywords":55,"publishedAt":19},"01M7AT1FQJAE1FQYAMDTF490Y4","white-paper-writing","Use when writing white papers, technical reports, policy documents, thought leadership pieces, or any long-form authoritative document. Triggers on requests to write, structure, outline, or review white papers, technical reports, position papers, policy briefs, or evidence-driven arguments. Also use for B2B content marketing strategy, technical documentation requiring authority, academic-style reports, or any document that must educate while persuading. Use when someone asks \"how should I structure this\" for a long-form document.","https:\u002F\u002Fgithub.com\u002Fthe-vibey-project\u002Fvibey\u002Fblob\u002Fdevelop\u002Fsrc\u002Fvibey_tools\u002Fskills\u002Fplugins\u002Fwriting-craft\u002Fskills\u002Fwhite-paper-writing\u002FSKILL.md",[],[],{"skillNo":57,"name":58,"nameZh":6,"description":59,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":60,"categories":61,"keywords":62,"publishedAt":19},"01M7AT16BJRJJKK2MASXRZS76G","prose-technical-mechanics","Use when editing or writing prose at a technical\u002Fmechanical level: choosing between Anglo-Saxon and Latinate diction, placing information in topic vs stress positions, writing periodic vs cumulative sentences, handling sentence rhythm, punctuation as logic, transitions, paragraph structure, or phonesthetics. Use when someone wants to understand WHY prose works or doesn't, not just surface-level style advice. Triggers on word choice, sentence structure, emphasis, rhythm, diction, or any deep writing mechanics question.","https:\u002F\u002Fgithub.com\u002Fthe-vibey-project\u002Fvibey\u002Fblob\u002Fdevelop\u002Fsrc\u002Fvibey_tools\u002Fskills\u002Fplugins\u002Fwriting-craft\u002Fskills\u002Fprose-technical-mechanics\u002FSKILL.md",[],[],{"skillNo":64,"name":65,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":67,"categories":68,"keywords":69,"publishedAt":19},"01M7AT0W9HT0ZZ9Y287NW99MR3","prose-mechanics","Use when writing, editing, or analyzing prose style; when trying to avoid generic AI-sounding writing; when applying specific prose styles such as journalistic, academic, narrative, KJV biblical, Hemingway plain, Latinate\u002FJamesian, Orwellian, Augustan, Victorian, Early Modern (Bacon, Browne, Milton), or free indirect discourse; or when coaching someone on writing voice and mechanics. Triggers on any request to improve, analyze, or write in a specific prose style, to fix \"AI-sounding\" writing, to make prose more vivid or concrete, to vary sentence rhythm, or to understand how a particular writer achieves their effects.","https:\u002F\u002Fgithub.com\u002Fthe-vibey-project\u002Fvibey\u002Fblob\u002Fdevelop\u002Fsrc\u002Fvibey_tools\u002Fskills\u002Fplugins\u002Fwriting-craft\u002Fskills\u002Fprose-mechanics\u002FSKILL.md",[],[],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":19},"01M7AT0KR635JX66X2X6F3E2CP","narrative-structure","Use when structuring stories, pitches, presentations, white papers, or any persuasive narrative; analyzing the hero's journey in fiction or non-fiction; applying StoryBrand for business communication; designing narrative arcs for thought leadership; or understanding Vogler, Snyder, Propp, or Campbell frameworks. Triggers on any narrative structure, storytelling, pitch structure, StoryBrand, hero's journey, three-act structure, Freytag, Save the Cat, narrative arc, or \"how should I structure this story\u002Fpitch\u002Fpresentation\" request.","https:\u002F\u002Fgithub.com\u002Fthe-vibey-project\u002Fvibey\u002Fblob\u002Fdevelop\u002Fsrc\u002Fvibey_tools\u002Fskills\u002Fplugins\u002Fwriting-craft\u002Fskills\u002Fnarrative-structure\u002FSKILL.md",[],[],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":19},"01M7AT0AKGW09NKKZDYBT8VRDE","legal-brief-writing","Use when writing legal briefs, motions, or any court filing; when analyzing judicial cognition and persuasion; when applying elite brief-writing techniques from Roberts, Clement, Kagan, Garner; or when structuring legal arguments for maximum persuasion. Also use for autistic\u002Fneurodivergent advocates who need to understand how their natural communication style maps to elite legal advocacy. Triggers on any legal writing, brief drafting, motion preparation, or legal argument structuring request.","https:\u002F\u002Fgithub.com\u002Fthe-vibey-project\u002Fvibey\u002Fblob\u002Fdevelop\u002Fsrc\u002Fvibey_tools\u002Fskills\u002Fplugins\u002Fwriting-craft\u002Fskills\u002Flegal-brief-writing\u002FSKILL.md",[],[],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":19},"01M7AT00VWPS4Q8B5VEMXX9NQT","journal-publishability-criteria","Use whenever a research paper, article or preprint is being written, revised, reviewed or published, and specifically before every publication of docs\u002Fpaper.md. Covers what legitimate journals actually gate on, in order of gating — the editor's desk screen (scope, novelty, package problems), what reviewers judge (methodological soundness, claims the evidence can carry, statistical and qualitative reporting), EQUATOR reporting guidelines, the ICMJE authorship criteria, COPE's view of text recycling, the near-universal generative-AI policy (no AI author, disclosure, author responsibility), TOP 2025 transparency standards, how to verify a journal is legitimate, submitting without an institution, and a pre-submission checklist. Triggers on requests to evaluate, review, prepare or submit a paper, to judge publishability, to write a declarations or data-availability section, to disclose AI use, or to check a journal.","https:\u002F\u002Fgithub.com\u002Fthe-vibey-project\u002Fvibey\u002Fblob\u002Fdevelop\u002Fsrc\u002Fvibey_tools\u002Fskills\u002Fplugins\u002Fwriting-craft\u002Fskills\u002Fjournal-publishability-criteria\u002FSKILL.md",[],[]]