How Stable knows what it knows

Last updated: 25 June 2026

A fair question about any AI assistant is: where does its knowledge come from, and can you trust it? With a human project manager you'd ask about their experience. Here's the equivalent for Stable.

Built AI-first — and deliberate about what it stands on

Stable is unashamedly AI-first; we think it's the best way to take the load off a renovation, and we'll keep experimenting to make it faster and more useful. We're also straight with you about what that means: AI is powerful but fallible, so the more it does, the more its answers should rest on solid, current source material rather than memory alone. That's why its understanding of how a job runs — the stages, the typical sequence, the lead times, and the points where the rules bite — comes from a hand-built knowledge base, one file per renovation type, that we maintain and version like code.

The facts come from official and authoritative sources

When it comes to anything regulatory, we prefer sources in this order:

• Official UK government material first — the Building Regulations Approved Documents on gov.uk and legislation on legislation.gov.uk, which are published under the Open Government Licence.
• Recognised industry bodies where government doesn't cover it — for example the Planning Portal, Local Authority Building Control (LABC), the Gas Safe Register, and Historic England.
• Facts, not copied text. From general trade guides we take only the underlying facts — a typical sequence, a usual lead time — written up in our own structure. We don't republish anyone's words.

Every regulatory trigger in the knowledge base records the source it came from and the date it was checked, so a claim can always be traced back.

Human review is the bar — and we'll tell you where we are with it

This is the part that matters most, so we'll be precise about it. Our standard is that a person reviews each fact before it grounds a live plan. The system is built for exactly that: every knowledge file is marked draft until a reviewer promotes it to reviewed, recording who checked it and when, and the loader can refuse to serve draft files in production. Review is done by people with hands-on building and quantity-surveying experience, so the facts that carry legal and safety weight rest on real expertise.

And we won't overclaim where we are today. During the beta the reviewed knowledge base is still being built. Until a renovation type has been through that review, Stable treats anything not yet reviewed as provisional — it won't present it as settled fact, and flags it to confirm with your trades and the relevant authority rather than relying on it. As each type is reviewed, it becomes the grounded source behind your plan.

A helper, not the last word

Stable is an assistant, not an oracle. It's AI, and AI can get things wrong — so treat it as a sharp pair of hands, not a source of truth: check what matters and use your own judgement. Its job is to raise questions, never to issue rulings — flagging the things worth checking ("this may need Building Control sign-off", "this is the point to bring in a registered electrician") and pointing you at the right professional. Anything structural, regulatory, or safety-related is always for your trades and the relevant authority to decide. Stable organises; it doesn't pretend to be the expert.

It's kept current on purpose

Regulations change on known dates, so we refresh the knowledge base on a schedule tied to those changes rather than waiting for something to go stale. Each file is versioned, so we can tell exactly which revision informed any given prompt.

In short: we're AI-first and we'll keep experimenting to make Stable faster and more useful — while staying deliberate, and honest, about the facts that bite.

Questions

If you'd like to know more about how a particular suggestion was sourced, or you spot something you think is wrong, email hi@meah.ai — we'd genuinely like to hear it.