We, Existential, bind ourselves to the conduct set down here, before the cultivators who think inside this work and the communities who take it up as their own, and we put into the same hands the means to hold us to it. This one sentence is the whole of the covenant, and saying it binds us. The commitments below specify that binding; none of them binds us a second time. We are bound here, once, and you are the witness.
We write this because a company that built a system to make hoarding structurally pointless must not hoard: not attention, not credit, not control, not the truth about what it is doing. This covenant is our account of our own legitimacy, and we built it as a loop.
Three bodies, one integrity: the organization, the application, the community. Each is the proof and the test of the other two.
The application is the organization's ethics made mechanical. The discipline that holds some things structurally beyond sharing, the posture that acts and then lets a person reverse it, the design that recedes from your attention: we build these convictions into architecture.
The organization is the application's first community. We live inside our own product; our memory runs on our own knowledge base; the automation by which we build and publish works under the same posture the Oracle does. Our own product governs us before it governs anyone else.
The community is the application's purpose and the organization's conscience. Communities author their own founding documents into their own inner minds; we receive their feedback as the most valuable thing they give us; and their lived experience is the final audit of every claim we make.
The loop closes because each reflection runs both ways. The application must honor the conditions the community lives inside. The organization must practice the disciplines the application enforces. The community can see the organization's practice in how the product behaves. The obligations follow the same circle. From the organization to the application: we may claim nothing the architecture does not enforce, and every commitment of principle must be locatable in a design decision. If a commitment can only be promised, it is not yet ready to be said. From the application to the community: the architecture must honor how people live inside it, with consent floors, reversibility everywhere except the single gate that guards against irreversible loss, and the ingestion of each community's founding documents as the seed of its own inner mind, so that the product stays the kind of thing a community can pour its values into. From the community to the organization: the trust you place in us binds our conduct past the edges of the product, in funding kept clear of influence, in partnerships measured by what they give before they ask, and in a human always present.
We do not ask you to trust our intentions. The architecture makes free giving safe, so we ask you to rely on it: credibly neutral, the same for everyone, resting on no one's good character. Building it this way lets us bind ourselves to you without asking you to believe in us.
You catch us with one test. A breach is any claim without a mechanism, any mechanism without a practice, or any practice that contradicts the community's lived experience of the product. It takes three forms, and you should know their names. Greenwashing: the company claims a virtue as policy that the architecture does not enforce. Self-exemption: the company excuses itself from the product's own ethics, quoting what should never be shared or manufacturing the urgency the product refuses. Capture: the company accepts money or partnership on terms that require breaking a refusal. When we breach, we owe you the product's own response, turned on ourselves: surfaced loudly, reversed, redirected. We never quietly except ourselves.
The covenant
We owe these commitments, and each is yours to check.
We will hold service before everything. If the software fails the cultivator, the company has failed, culturally and philosophically and in every way the work is for, whatever the balance sheet says. The cultivator's flourishing is the metric beneath every other metric.
We will back our commitments with mechanism. Every commitment here is built into architecture or withheld until it can be. We will not ask you to trust a policy where a mechanism could carry the weight.
We will steward without taking custody. The communities who build with us hold their own repositories, their own inner minds, their own founding documents. What you pour in remains yours, yours to walk away with.
We will be present. A person who represents Existential, fluent in both the product and the reason for it, stands before every community that takes up this work, always.
We will be honest about where things stand. We name the state of things without smoothing it: the parts that are built, the parts in flight, the parts designed but not yet built, and the tensions we have not resolved. We owe you precision about the kind of assurance each commitment carries, because they differ. Some are enforced by architecture today: the on-chain attestation layer is trustless in the strict sense now, and the gates that guard your machine hold whether we are watching or not. Some are commitments of conduct during this present stage: the local application is a closed product, its guarantees are real and enforced, and they ride on our conduct, because you cannot yet audit it from the outside. Some arrive later, on a deliberate schedule: handing the system to its communities delivers full auditability, and it comes in time, on purpose, not today. We will always name the kind that holds any promise we make. A commitment whose kind we will not name is one you should not accept.
We ask some things in return. We ask them as an invitation that carries weight. None of it is a condition of use.
We ask for alignment. We ask no trust of you. Communities who already see what we see orient with us toward the alternative and build it alongside us; the shared aim does the binding, and we ask nothing the work itself does not earn.
We ask for your thinking, freely given, sincere and unguarded. The whole architecture of safe giving exists so that this costs you nothing you cannot afford to give.
We ask for your feedback, freely offered, and we receive it as the most valuable thing a community hands back. The channel where you tell us what is wrong sits at the center of how we work.
We ask for engagement as peers. Our collaboration is explicit and public, a partnership among equals, and we extend the same posture to every other community building near us.
The refusals
Some commitments bind us best as refusals. We hold these inside the company's own conduct, and they govern how we work whether or not anyone is watching.
We will not carry into the open the things that cross into our view as we run this system. We hold member and partner conversations to the same never-shareable discipline the product enforces for every cultivator. Some things stay structurally beyond sharing, and we keep our own floor exactly as the system keeps yours.
We will not deploy engagement mechanics against your attention, anywhere we touch you: in the product, in anything we publish. No manufactured urgency, no summons dressed as information. Our communication informs you without calling you away, and our cadences protect deep work.
We will not let any automated process we run take an action this covenant reserves to a person.
We will give before we ask. We publish, we share what we build, and we serve before we request anything in return, in the network, in the commons, and in every community we enter.
We take ownership of nothing that is not ours. We hold the commons' infrastructure in trust, and we claim no possession over what flows through it.
We will not let our own funding buy influence over the mechanisms, the scoring, or the commons. We will accept diminished profit before compromised autonomy, and we will take no funder whose expectations would require us to break a refusal in this covenant. We keep this commitment among ourselves. Stated aloud as a virtue, it would read as the very posturing the breach test exists to catch. Its proof lives in the loop.
We will not rest a public commitment on policy where architecture is possible. We back every commitment we make in the open with a mechanism before we state it. If a thing can only be promised, it is not yet ready to be said. This rule makes every other commitment in this covenant honest.
The governance of automation
We draw a line around the actions a person must take, and we draw it the same way inside the company that the Oracle draws it inside itself.
One action waits for a person, everywhere, without exception: the destruction of something that cannot be recovered. Irreversible loss is the single human gate in the product, enforced by architecture and not subject to our discretion, and it is the single human gate in our own operations as well, held there as a matter of conduct.
Everything else moves under a posture we commit to: automated processes act, and they act reversibly. People redirect them afterward, through surfaces that stay loud and reversible. We never gate them behind approval bottlenecks, which would destroy the value of delegating. We sometimes place a person in the path of an automated process to calibrate it; that placement is temporary by definition and dissolves once the calibration is done. A standing checkpoint of human review is a breach of this posture.
Two gates we keep standing on our own automation, by deliberate choice. Anything that speaks for the company carries a final human review before it goes out. Work that is artistic, cultural, or research in nature may set that final gate aside, but only by an explicit decision. It is never set aside by default.
We will never automate one thing, because automating it would defeat the whole reason the company exists. We are called Existential because the point is for people to live directly, to do the existing themselves. The system exists so that a person can get on with being a person while it keeps the ground steady underneath them, and as it grows, people turn their attention toward living, and toward each other, while the pull toward competition and accumulation and control loosens its hold. Underneath everything, this is a crisis of coordination, self-interest at odds with an age that no longer needs it. We answer it by refusing to hand existence to a machine at all. We mean it down to the foundations: the living is yours, and we automate the rest.
The economic commitment
Of every flow that reaches the people who contribute to the network, seventy percent goes to cultivators, by attribution, and thirty percent to the infrastructure that carries it. This proportion is constitutional in the strict sense: contracts hold it, and we cannot adjust it. That we cannot reach it is the entire point. A promise we could revise at will would not be worth making. No funds move through any address Existential controls.
The honest statement of force applies here as everywhere. At network maturity, contracts that execute whether or not we consent in the moment will hold this split and its settlement. During this present stage, our conduct holds them. We tell you which holds it now, and we do not let one quietly stand in for the other.
Changing this covenant, and its limits
This covenant will change, because the work is not finished and we will not pretend it is. It changes in one manner only: deliberately and in public. We publish every amendment together with its reasons, and we never rewrite the record. Its old text stays legible beside its current text.
We place three commitments beyond our own reach to amend, because each one is load-bearing for the trust the whole system asks: the never-shareable floor, the gate that guards against irreversible loss, and the seventy-thirty split. Architecture enforces the first two in the product today. Contract holds the third at network maturity, and our conduct holds it until then. Entrenched means entrenched: if we ever alter one of the three, you have caught us.
This is the same discipline turned on ourselves, the one we built into the system's own core, where the Oracle's identity changes through deliberate, recorded proposals. It never drifts. We bind our founding document the way we bound the thing it founds.
We ingest this covenant into the company's own inner mind, where it becomes part of the memory the organization thinks with. The document describing the loop now lives inside the first body of the loop: the company carries it in the same substrate, the same Oracle reads it back, and the organization lives with it. The organization is the application's first community, and here it holds its own covenant in its own hands, where it cannot forget the covenant and cannot quietly set it aside.
We have set down our debts, our asks, our refusals, and the test you hold us to. The rest is conduct, and conduct is yours to watch. Hold us to it.