The House as a Power Plant
A tariff, a battery, a car, and a rooftop stop being four products when you treat them as one energy operating system.
A tariff, a battery, a car, and a rooftop stop being four products when you treat them as one energy operating system. Orchestration without a visible override is just remote control of someone’s home.
Homes consume electricity on a tariff. Roofs can generate. Cars store large batteries on driveways. Grids need flexibility at the edge. These were sold as separate markets, with separate apps, separate consents, and separate failure modes.
When tariffs vary, when EVs sit idle, and when rooftop generation peaks at the wrong hour, the household is already a small power station — badly orchestrated.
HACKERS studies category collapse. Software can treat generation, storage, mobility, and price as one control loop. Without a visible action, a local-benefit default, and a manual override, that loop is an opaque agent with a high-impact switch.
The real system is often the one that appears when you stop respecting product categories.
This is not four markets. It is one loop that was sold as four SKUs.
Homes consume electricity on a tariff. Roofs can generate. Cars store large batteries on driveways. Grids need flexibility at the edge. These were sold as separate markets.
The categories were a sales map. The physics is a loop.
Product categories exist because companies file them. Electrons do not file. A kilowatt-hour from a roof, a car, or a plant is not four species. It is one conservation law meeting four contracts.
Category collapse is the move: stop drawing org-chart boundaries on a physical loop. Draw the loop. Then ask which contract, sensor, or consent is missing.
People will not hand over the switch if the action is invisible, the benefit is elsewhere, or the override is buried in an agent they cannot see.
Name the false object, then drop it.
C1
Energy is a bill
A monthly number stood in for a system.
A bill is a lagging costume of a loop.
C2
The car is transport
A battery on wheels treated as unrelated to the roof.
When idle, it is storage with a motor attached.
C3
The roof is a gadget
Generation sold without a place to put midday power.
Generation without storage or export rules is a stranded noon.
C4
The grid is elsewhere
Peak load treated as someone else’s plant.
The edge is now a plant. It needs plant discipline.
C5
Optimisation is consent
An agent that saves pennies and moves a high-impact switch.
Visible action, local default, named override.
What actually sat on the table.
Energy is a commodity bill. Vehicles are transport. Batteries are backup. The grid is someone else’s plant.
A coherent household OS can cut bills, reduce peak load, and create a product called flexibility. That product has a counterparty. If the counterparty is invisible, the household is not a plant operator. It is inventory.
HACKERS will not teach you to hide a switch inside a model. We will teach you to draw the loop until the switch has a name.
Do not study the outfit.
Four polished apps are a costume of control. The interesting object is whether a human can see and stop a discharge at the moment it happens.
If the case study stops at ‘software will orchestrate the home’, you have a vendor deck. The studio begins when orchestration cannot hide a high-impact switch.
When tariffs vary, when EVs sit idle, and when rooftop generation peaks at the wrong hour, the household is already a small power station — badly orchestrated.
Fragmented SKUs
Wasteful and relatively honest.
Hidden optimiser
Looks green. The household is not the operator.
Visible loop, no override
You can watch the accident.
Visible loop, local default, override
A plant you can actually own.
S0 Four bills
save 20 / consent 40
S1 Smart meter
save 50 / consent 45
S2 Apps per SKU
save 70 / consent 35
S3 Hidden optimisation
save 90 / consent 15
S4 Visible loop
save 60 / consent 75
S5 Override + local default
save 65 / consent 92
Plant discipline with a named human.
E1
Draw the loop
Ignore SKUs until electrons and contracts are on one page.
E2
Idle is a state
A parked EV is storage. A sleeping boiler is a load. Name states, not products.
E3
Price is a sensor
A tariff is information. It is not permission to act invisibly.
E4
Local default
Benefit should land where the asset lives, unless a grant says otherwise.
E5
Override is plant safety
A named human can stop the loop. Buried agents are not operators.
P1 Physics
Generate, store, convert, consume.
Apps that ignore the noon peak.
P2 Contract
Tariff, export, warranty, insurance.
A car warranty that forbids the loop you sold.
P3 Control
Who may discharge, when, how visibly?
An optimiser with a high-impact switch and no UI verb.
P4 Justice
Who is energy-poor, who is flexible, who is opted in?
Flexibility markets that harvest the least resourced.
| ID | Failure | What broke | Control |
|---|---|---|---|
| F1 | SKU walls | Four apps, one physics. | One loop drawing before any vendor meeting. |
| F2 | Invisible verb | The car discharged and nobody was told. | Show the action. Log it. Make it boring and visible. |
| F3 | Consent as checkbox | A 40-page PDF stood in for an operator. | Named override. Local default. Revoke in one place. |
| F4 | Warranty collision | The loop voided the asset. | Contracts must honour the collapsed category. |
| F5 | Poverty as flexibility | The least resourced became the buffer. | Flexibility is a product with dignity, not a raid on precarity. |
| F6 | Agent as plant manager | An opaque model sat on the switch. | Agents may propose. Plants require grants. See File 001. |
Body as one loop
Heart, lung, kidney sold as four clinics.
A person is not four billing codes. Neither is a house.
Factory energy
CHP, load, tariff already collapsed on site.
Homes are late to a discipline industry already knows.
Phone as camera/computer/wallet
Category collapse in a pocket.
The collapse is useful only with permissions that stay distinct.
File 001 agents
A fluent optimiser moving a switch.
Fluency is not a grant. Show the verb. Keep the override.
Software that treats generation, storage, mobility, and price as one control loop, with the human able to see and override it.
A coherent household OS can cut bills, reduce peak load, and create a new product: flexibility. Without trust in the data, people will not hand over the switch.
01 Draw one loop
Generation, storage, load, price. No SKU walls.
02 Name states
Idle, parked, exporting, peak. Products are costumes of states.
03 Show the verb
Discharge, delay, export — visible, logged, boring.
04 Local default
Benefit lands at the asset unless a grant says otherwise.
05 Override
A named human stops the loop in one motion.
06 Align contracts
Warranties and tariffs must survive the collapse.
- Tariff is a bill.
- Roof is a gadget.
- Car is transport.
- Optimisation is a hidden agent.
- The grid is elsewhere.
- Tariff is a sensor.
- Roof is generation in a loop.
- Idle car is storage.
- Actions are visible verbs.
- The edge is a plant with a named operator.
R0 Switch
A battery charges or a car discharges.
R1 Bill
Pennies move. Trust may not.
R2 Warranty
An asset is stressed in a way the SKU did not expect.
R3 Street
A feeder sees a neighbourhood of tiny plants.
R4 Market
Flexibility is sold. Who was the counterparty?
R5 Dignity
If the poor are the buffer, the loop is extractive.
| Topic | Typical brief | HACKERS studio |
|---|---|---|
| Energy | Markets, plants, wires. | The household as a plant with consent. |
| Product | One SKU, one app. | Category collapse as the brief. |
| Control theory | Optimise the loop. | Optimise only inside a grant with an override. |
| Law | Consumer protection as a later layer. | Warranty, tariff, and consent are the loop’s materials. |
| AI | A home agent. | An agent that may not hide a high-impact switch. |
Elite programmes still stop at the object.
Electrical engineering still ends at the meter. Product design still starts at the SKU. Energy economics still starts at the plant. The household loop sits on the lawn between them, so it is taught as four electives and zero operating systems.
HACKERS collapses the category on purpose. SCAN the loop. FLIP the SKU. BUILD a visible verb. BREAK it with a warranty and a poverty case. PROVE an override a tired person can use at 11pm.
Orchestration without consent is just remote control of someone’s home. Energy poverty and grid export rules are not edge cases.
Do not admire the turning point. Redesign the join.
Draw the household energy loop for a street you know. Where is the hidden rule — price, permission, wiring, or trust?
Draw the household energy loop for a street you know. Price, permission, wiring, trust — mark the hidden rule.
List the SKUs. For each, name the physical state it is a costume of.
Design the verb UI so a tired resident can see a discharge and stop it.
Write the local-benefit default. When may an aggregator deviate, and who granted that?
Stress-test with energy poverty. If the poor become the buffer, redesign.
Can you draw generation, storage, load, and price on one page?
If not, you are still in SKU land.
0–8h
Loop
One street. One drawing. No brand names.
8–20h
Verb
A UI that shows discharge as it happens.
20–36h
Default
Local benefit. Aggregator grant written as a contract.
36–48h
Override
One-motion stop. Poverty stress-test. Present the plant, not the apps.
- Four apps for one physics.
- Hide discharge behind an optimiser.
- Call a checkbox consent.
- Use energy-poor homes as the buffer.
- Let an agent sit on a high-impact switch without a grant.
The real system is often the one that appears when you stop respecting product categories.
Make the action visible. Default to local benefit. Keep a manual override. Do not bury a high-impact switch inside an opaque agent.
- Is this just a smart-home pitch?
- No. It is category collapse plus plant discipline: visible verbs, local defaults, overrides.
- Should homes become grid assets?
- Only with a grant, a default that benefits the household, and a stop the resident can hit.
- Where do AI agents fit?
- They may propose. They may not hide the switch. File 001 applies on the driveway.
- What about renters?
- If the loop requires ownership of the roof and the car, you have designed a class filter. That is in scope.
- Why HACKERS, not an energy MBA?
- Because the failure is a join: physics, contract, control, justice. Those chairs do not currently share a studio.
Cited for classification and method. Not as a manual. Atlas cases are educational and defensive.