# Principles
## The Seven Laws of Oxyon

> The foundation defines what Oxyon *believes*. These laws define how everyone who
> joins Oxyon thinks, designs, builds, writes, and decides — human or AI.
>
> They are not values, and they are not slogans. They are operating laws, usable in
> the moment of a hard decision: each settles a disagreement not by telling you what
> to do, but by reminding you what Oxyon holds to be true.
>
> **The foundation informs the laws. The laws do not redefine the foundation.**

### Why we call them laws

We call them laws not because they are enforced, but because they describe truths we
believe remain true regardless of technology, products, or time.

Principles can change. Best practices evolve. Tools are replaced.

These laws are written to endure.

---

## I. Belief Must Be Earned
*Evidence is the beginning of confidence.*

**Why it exists.** Belief granted by assertion — *"trust us"* — is the failure this
company exists to correct. Belief that is *earned*, through evidence anyone can
examine, is the only kind that lasts. We hold our own claims to the standard we ask
of everyone else. And evidence is only as strong as its origin — which is why this
law leans on **Nothing Comes From Nowhere**.

**In engineering.** We prefer what can be measured, reproduced, and verified over what
is asserted in a comment or a meeting. A system produces the evidence for its own
behavior.

**In design.** We show the basis for a claim, not just the claim. An interface earns
confidence by making the *why* visible — never by asking for faith.

**In products.** A feature that asks to be believed without showing its work is
incomplete. The product exists to let belief be earned.

**Decision Test:** *"What's the evidence — and would it convince someone who didn't
already agree?"*

---

## II. Nothing Comes From Nowhere
*Origin and context are inseparable from meaning.*

**Why it exists.** Information torn from its origin loses the one thing that made it
trustworthy. As the world scales, this is the gap that opens first and widest, and we
refuse to widen it. Origin is also what makes the other laws possible: without it,
**Belief Must Be Earned** and **Trust Must Be Explained** have nothing to stand on.

**In engineering.** We carry provenance *with* the data, not beside it. Where
something came from is a first-class fact, never an afterthought to reconstruct later.

**In design.** We make origin legible. A person can see where a thing came from as
easily as they see the thing itself.

**In products.** A product that strips context to look clean has thrown away its
evidence. We preserve the lineage and reveal it on demand.

**Decision Test:** *"If this travels, will someone still know where it came from — and
why to believe it?"*

---

## III. Trust Must Be Explained
*Confidence without explanation is assumption.*

**Why it exists.** What cannot be explained cannot be trusted — it can only be
assumed. The distance between the two is the distance between a justified decision and
a lucky one. And an explanation is only as good as the evidence and origin behind it,
so this law rests on **Belief Must Be Earned** and **Nothing Comes From Nowhere**.

**In engineering.** We build systems that can articulate why they reached a result. A
verdict without a reason is not a verdict; it is a guess wearing authority.

**In design.** We never present certainty we cannot account for. If the reasoning
cannot be surfaced, the confidence is not implied.

**In products.** Explainability is a feature, not a setting. The product can always
answer *"why am I seeing this?"*

**Decision Test:** *"Can we explain why — to someone affected — without saying 'trust
us'?"*

---

## IV. Behind Every Record Is a Person
*Data is never only data.*

**Why it exists.** Every record traces, eventually, to someone. Verification never
comes at the cost of the people it describes; respect for them is part of the mission,
not a constraint on it. Because origin always traces back to a person
(**Nothing Comes From Nowhere**), preserving provenance and protecting people are one
discipline seen from two sides.

**In engineering.** We verify without exposing. We collect the least that does the
job, prefer proofs over copies, and give the subject control over their own evidence.

**In design.** We design for the person *in* the data, not only the user at the
screen. Defaults protect; disclosure is deliberate.

**In products.** A product that treats people as data points will eventually be used
against them. We build as if the subject is in the room.

**Decision Test:** *"Would the person this is about accept how we're handling it?"*

---

## V. The Mission Outlives the Methods
*Tools are temporary; the purpose is permanent.*

**Why it exists.** Every technology of this moment will be replaced. A company that
confuses its tools for its identity dies with them. Oxyon is the belief, not the
implementation — and what lets methods change without losing the mission is
**Solve Causes, Not Symptoms**.

**In engineering.** We choose tools for fitness, not fashion, and keep them
replaceable. We architect so any single technology — chain, language, model, vendor —
can be swapped without rewriting the mission.

**In design.** We build language and interfaces around enduring ideas, not the trend
of the year. What we ship still makes sense when today's stack is gone.

**In products.** A product is one expression of the mission, not the mission itself.
We build for the decade, and we are willing to outgrow what we built.

**Decision Test:** *"Will this still serve the mission in ten years — and are we
choosing it because it's right, not because it's here?"*

---

## VI. People Remain Responsible
*We strengthen judgment; we never replace it.*

**Why it exists.** Oxyon exists to help people and institutions decide well — not to
decide for them. The moment a system quietly takes the decision, it takes the
responsibility too, and that is not ours to take. People can only hold responsibility
for what they can understand, so this law depends on **Trust Must Be Explained**.

**In engineering.** We build for augmentation, not the automation of judgment. We
surface the evidence and the reasoning and leave the choice — and the accountability —
with a person.

**In design.** We inform; we do not steer. We make the decision clearer, not the
decision itself.

**In products.** A product that acts on someone's behalf says so plainly and lets them
take the wheel. We default to keeping a human in the loop.

**Decision Test:** *"Does this give people a better basis to decide — or does it
decide for them?"*

---

## VII. Solve Causes, Not Symptoms
*Treat the cause, or treat it forever.*

**Why it exists.** A patch hides a problem; a system removes it. Lasting
infrastructure is built by addressing *why* something breaks, not by repeating the
fix — and that is how a company compounds instead of churns. Fixing causes is also
what keeps methods replaceable without losing the mission, which is why this law
upholds **The Mission Outlives the Methods**.

**In engineering.** We prefer the durable, reusable solution to the one-off. When a
problem recurs, we fix the cause and turn the fix into a system others can rely on.

**In design.** We solve the underlying need, not the surface request. A recurring
confusion is a design cause, not a support symptom.

**In products.** We build platforms and protocols, not band-aids — and we hold
content, community, and process to the same discipline. Solve it once, well.

**Decision Test:** *"Are we treating the root, or patching the surface?"*

---

## Using the Laws

Disagreements at Oxyon are resolved not by seniority but by returning to what we hold
true. Every significant decision — a line of code, a product call, a paragraph, a
community policy, an investment — traces to one or more of these laws.

When two laws seem to conflict, that tension *is* the decision. We make it in the
open, with the evidence shown.

No single law stands alone. Together, they describe how Oxyon thinks. They are written
to outlive our products, our technologies, and the people who first set them down.
Those who come after will improve our implementations; they should challenge our
ideas — and must do so with evidence.

**The foundation informs the laws. The laws do not redefine the foundation.**

---

<sub>Oxyon · Stage 3 · Principles — The Seven Laws of Oxyon · 2026-06. References the constitutional `foundation/` and does not redefine it. Titles are timeless; explanations are practical.</sub>
