INTRODUCING BUILDING INDEPENDENCE
You own the building.
Stop renting the understanding.
Flux answers a hard question about your building in plain English, shows every piece of evidence, says what it doesn't know — then checks whether the fix actually worked.
Everyone is about to sell you a building assistant. Ask each one to show its work. Here's ours.
One answer, start to finish
“Why is the lab loop running on the standby pump?”
The lead chilled-water pump stopped reporting. The standby has been carrying the lab loop.
Flux put this first out of six open issues — not because it was the loudest, but because a lab had quietly lost its redundancy and nobody had been told.
Recommended action. Verify pump status with the site and inspect gateway communication before clearing the alarm.
A reference building on the real software. Demo data, production interface.
ACTION RAIL
6 ranked issues
Research Lab / Chilled Water Pump 2
North Tower / AHU-7
West Annex / Portfolio
East Plant / RTU-3
South Campus / Portfolio
Clinic / AHU-2
SHOW YOUR WORK
Every answer opens.
PERFORMANCE ISSUE
Critical pump status is stale while redundancy is reduced
The lead chilled-water pump status has not updated and the standby pump is carrying the lab loop.
Recommended action
Verify pump status with the site and inspect gateway communication before clearing the alarm.
Impact
4 comfort hrs
Annual cost: $18,000
Confidence
Alarm and last-good sample agree, but telemetry is stale.
How it works
Understand. Decide. Act. Verify. Learn.
Every project says up front which sources it can reach and where access stops — before anyone forms an answer.
FOUR SOURCE TERRITORIES
LIVE OPERATING RECORD
Evidence, decisions, actions and outcomes — owned by you.
Exports as an open Building Understanding Standard package.
The next cycle starts ahead. Verification becomes new operating context, so the next question begins with what the building already proved.
Operations triage
Five alerts. One goes first.
Flux ranks by consequence, not volume. A generator alarm at a hospital outranks a damper fault, and it has an owner before anyone opens a ticket.
Ranked by consequence
P1 through P4, each with a response expectation the whole team can see.
Owned, not just raised
Every alert carries who has it and where it stands: diagnosed, acknowledged, paged.
Straight into corrective work
Start a response and it becomes a work order, then a verification, without retyping a thing.
Who decided
Software doesn't get the last word.
A qualified integrator reviews the evidence. The accountable owner makes the call. Both are recorded — who, when, and on what basis — beside the evidence they were looking at.
Declining is a decision too. Six months later, you'll want to know it was made on purpose.
DECISION RECORD
RecordedHUMAN AUTHORITY · SOFTWARE INFORMS, ACCOUNTABLE PEOPLE DECIDE
- SoftwareObservation
- SoftwareInference
- PersonQualified review
- PersonOwner authorization
- PersonQualified action
- BuildingLive verification
What the building did
Then the building grades it.
Flux follows every action into live operation and compares what happened against what was predicted — the discipline software teams use to stop a working system from quietly regressing. CI for buildings.
Verification matrix
CI for buildings: every equipment and test pair shows its latest verdict, drift, and evidence entry point.
COVERAGE
4 checks
Certified
0
Blocked
2
Pending
0
Non-certifying
2
Zero certified. Flux does not turn an incomplete result into proof. This is the step that can prove us wrong. That's the point.
Capital planning
Replace what the building says to. Not what the calendar says.
The same understanding that runs the building ranks its capital. Every asset carries its condition, criticality, modeled failure window and financial case — so the replacement plan your board sees is the one the equipment is actually asking for.
Plan vs. modeled timing
Your scheduled year next to the P50 and P90 failure windows, so early and late both show.
Risk of deferral, priced
What waiting costs, in dollars, before anyone decides to wait.
A financial case per asset
NPV, IRR, payback and benefit-cost ratio — with the evidence behind every input.
Criticality you set
Suggestions never write. A person applies criticality, and the plan re-ranks.
Three doors
Whoever is accountable for something should own the understanding of it.
Owners
You own the building's record.
Could you explain last quarter's biggest operating decision to your CFO — what it was based on, what was uncertain, whether it worked? If not, you rented it.
Take the owner test
Qualified integrators
Automation does the assembly. You do the judgment.
Flux pulls the trends, reconciles the points and writes up the evidence — so your best engineer stops being the bottleneck. Your name stays on every review.
Founding integrator program
Equipment manufacturers
Ship it understood.
Your machine knows exactly what's wrong with it; the building gets a fault code. Run our control engine in your product, under your name, and its model travels with it.
Bring one product line
The realtime engine
Written from scratch.
Signed twice.
Replayable to the byte.
The realtime engine runs beside the equipment — or inside it. Verification only works if the building is still running, so it was built for equipment that ships in 2027 and is still in the field in 2045.
WHAT THE ARCHITECTURE MAKES POSSIBLE · EACH WITH ITS STATUS
The blocks you expect, deterministic to the byte.
One static ARM64 binary from the cheapest 64-bit module to an industrial edge computer. Boot it bare metal as its own kernel, or inside your RTOS. Your control logic ships as signed plug-in kits — without forking or disclosing it.
The open standard
Understanding you can take with you.
Flux Core OS reads and writes the Building Understanding Standard — an open, published package for a building's operational understanding. So what your building learns is never trapped in anyone's software. Including ours.
WHAT THE OWNER KEEPS
Everything that describes the building.
Points, spaces, assets and relationships. Setpoints, schedules and the reasoning behind them. Alarms and routing. Events and notes. Floor plans and their live bindings.
WHAT THE VENDOR KEEPS
Everything that describes the software.
The rendering, the workflow, the speed, the polish. A better product is still worth paying for. That's the point.
The Independence Test
Twelve conditions. One challengeable claim.
Can the owner change providers without losing what the building already taught them? If not, it isn't Building Independence.
- 01A qualified integrator other than the founder can deliver it.
- 02Flux assembles the evidence for one consequential question.
- 03Observation, inference, confidence and gaps stay distinct.
- 04The interpretation is in plain English.
- 05The owner can explain the answer and its limits.
- 06A qualified person reviews consequential judgment.
- 07The authorized owner makes the decision.
- 08The action is completed or consciously declined.
- 09Live evidence verifies whether the condition changed.
- 10The complete live record stays available to the owner.
- 11A second provider can continue without rebuilding context.
- 12The learning informs a later service, building or capital decision.
WHAT ISN'T HERE YET
Two things are missing, and we won't fake either.
CLAIM DISCIPLINE
Every public capability claim carries one of these.
Security & deployment
Understand the boundary before you connect.
Deployment, connector permissions, data paths and approval boundaries — validated against your site and agreed before a project begins.
DEPLOYMENT CHOICES
Managed
Hybrid
Nothing is a commitment until it's checked against your site, with a stated support boundary and your approval.
CONNECTOR BOUNDARIES
Delivery
Deployed by your integrator. Or by ours.
Own your next answer
Bring us one hard question about one building.
Four to six weeks. One accountable owner. You keep the answer and everything behind it.