Reference pattern · Grid × HVAC

Your building should know the grid.

A grid signal could inform a bounded HVAC proposal: pre-cool before a price spike, shed approved non-critical load, and preserve comfort limits. This is an illustrative reference pattern, not a live Fibric building connection or current self-service install.

A building that watches the market: a bronze loom weaving a live signal through A building that watches the market
The governed loop
Sense· Reason· Act· Receipt
Illustrative grid snapshot · reference pattern
0 $/MWh, real-time, right now

the cost your building isn't watching.

example ISO signalsample data
Real-time price spike
ERCOT West · $980/MWh
2 min
Demand-response event
Load-shed window called
14 min
Peak window
5–7pm forecast
1 hr
The Plan

The whole loop, applied.

One pass through four moves, with a record at each step.

01Sense

A price spike forms upwind

Minutes-to-hours before the peak, the market signal is already in the loop.

ISO price + DR signal → ingest & normalize → signal logged
02Reason

The operator proposes a plan

Weighed against your priorities (comfort, cost, occupancy) before anything moves.

Signal + your rules → propose plan → proposal id
03Act

Pre-cool, shed, coast

In a managed deployment, an approved connector could dispatch the bounded change with idempotency and single-flight controls.

Trust gate pass → dispatch · single-flight → action receipt
04Receipt

Record the supported outcome

The proposal, approval, and reported result belong on the record. Recovery depends on what the BMS and site procedure support.

Proposal + outcome → attribute & record → execution trail
The Plays

A price signal is a lead-time tripwire.

Price spike
Hours ahead

Pre-cool the thermal mass

+2–4 hr
DR event
Minutes ahead

Shed non-critical load

+5–15 min
Peak window
Scheduled

Coast on stored cold

5–7pm
Preview the pattern

Preview the signal-to-review pattern.

Reference capability path

Pre-cool your zones before the price spike.

The preview shows a proposed signal path. A real deployment requires a validated connector, explicit policy, human approval, and a tested recovery boundary.

Give your building market sense.

Request a managed review
Referencenot production
Managedreview required
Samplegrid snapshot
Boundedsite-specific policy

No public Fibric MCP endpoint or one-click install exists for this pattern. Scope it through managed early access.