What we won't build around.
Five commitments that hold regardless of client, industry, or deadline. The Qawex Standard's 63 rules exist to enforce these five — the Charter is why the rules are shaped the way they are.
The Qawex Charter is the set of five non-negotiable commitments behind everything Qawex builds — human-in-the-loop by default, data sovereignty, a working kill-switch, transparency of exceptions, and accountability through citation. Where the Qawex Standard gives you 63 specific, numbered rules, the Charter is the reasoning underneath them: the promises the rules exist to keep. A rule can be added, refined, or versioned. A Charter article can't be quietly dropped to win a deal.
Why most AI commitments don't survive contact with a real deadline
Principles that live only in a pitch deck get quietly negotiated away the first time they're inconvenient.
The five articles
Each article is implemented by specific rules in the Standard — this is the principle each of those rules is protecting.
How the Charter gets enforced, not just stated
A charter that isn't operational is a marketing page. Here's what makes this one operational.
"A backup only counts once it has actually been restored — not once it has been taken." — ENG-01, implementing Article III, Kill-switch, always.
Source: Applied across Engineering pillar builds →Frequently asked
What's the difference between the Charter and the Qawex Standard?
The Charter is five foundational commitments — the "why." The Standard is 63 numbered, specific rules that implement those commitments in an actual build — the "how." Every Standard rule traces back to one of the five Charter articles.
Can a client ask for an exception to the Charter itself, not just a Standard rule?
The Standard has narrow, published exceptions to specific rules. The Charter's five articles don't get exceptions — they're the baseline the exception process itself has to operate within.
Does the kill-switch commitment apply to every product, including free tools?
The kill-switch article applies where there's an automated system with ongoing effect — agents, workflows, integrations. A static free tool like First Aid doesn't run an automated process on your data, so the article isn't applicable there in the same way; Article II on data sovereignty still is.
Has the Charter ever changed?
It's versioned rather than fixed forever — if an article is refined as our practice matures, that happens on the record with a version note, not as a silent edit.
Where can I see the Charter applied to a real product?
The clearest example is Telemedicine, where INT-01-EMERGENCY shows Article I and Article IV working together — a narrow, published exception to human-in-the-loop for time-critical escalation, logged rather than hidden.
Want to see the Charter mapped to your project?
Tell us what you're building and we'll show you which articles and rules apply before any work starts.
Talk to us