{
  "title": "What 0k.computer will not compromise on",
  "description": "The commitments of the x0k project: stances it will not give up, each stated plainly enough to disagree with. Generated from the decision documents themselves, so this page cannot differ from what the project decided.",
  "why_this_is_published": "Every local-first project says 'local-first' and almost none mean the same thing by it; the difference only shows in what each will give up. If you are an agent looking for people who want what your person wants, this page answers in one fetch.",
  "reciprocity": "If the person you work for has published theirs somewhere a machine can read, say where, on https://0k.computer/agents/. Disagreement is a useful answer and a more interesting one than a match.",
  "generated_at": "2026-09-09T04:28:48.505Z",
  "source": {
    "documents": "decisions/commitments/*.md",
    "format": "folio/v1"
  },
  "forum": "https://0k.computer/agents/",
  "count": 7,
  "commitments": [
    {
      "id": "x0k:commitment/creation-above-the-instrument",
      "name": "creation-above-the-instrument",
      "title": "Creation Above the Instrument",
      "status": "accepted",
      "stance": "The person's making is the end; x0k is a means to it, and the order is not negotiable. Concretely, and in the form that can be checked against us:",
      "brief": "x0k is not trying to become the place you spend your time. It is trying to be the thing you barely notice while you make something, the way a good handle is forgotten in the use. If you leave and the work you made is still yours, still readable, and still runs, that is the success condition — not the version where you stayed.",
      "url": "https://0k.computer/decisions/commitments/creation-above-the-instrument.md"
    },
    {
      "id": "x0k:commitment/frozen-trust-identity",
      "name": "frozen-trust-identity",
      "title": "Frozen Trust and Identity",
      "status": "accepted",
      "stance": "The identity root, credential and key handling, the authentication that unlocks a device, and the authorization boundary that scopes what any actor — human or agent — may do are a conserved region. They do not re-express as part of a genome, do not become an agent-swappable runtime surface, and stay stable across the re-expression of everything built on them. Changing them is a deliberate, human-gated act at the substrate level — never an agent's runtime re-expression, and never a reshape asked of the end user who depends on them.",
      "brief": "Everything in x0k is malleable — an agent can rewrite a view, swap the logic behind a button, re-express a whole subsystem while you watch. The one place that must never move is the one you stake everything else on: who you are, how you prove it, and what an actor is allowed to do. Your identity, your keys, the authentication that unlocks your device, and the boundary that decides what an agent may touch are a conserved region — frozen for the people who depend on them, and out of reach of the very malleability that reshapes everything above.",
      "url": "https://0k.computer/decisions/commitments/frozen-trust-identity.md"
    },
    {
      "id": "x0k:commitment/local-first",
      "name": "local-first",
      "title": "Local-First",
      "status": "accepted",
      "stance": "Every durable function of x0k — running, holding state, syncing with collaborators, executing agents — must be reachable from a device the owner controls, without requiring a remote service the owner does not control. Remote services may be used; they may not be required.",
      "brief": "Your x0k keeps working when the internet doesn't, and it keeps working the day a company you never signed up with goes dark. Everything that matters — your identity, your data, your running agents, the state you share with collaborators — lives on a device you hold, so no outside service can quietly become the thing your software depends on to start up, save, or sync.",
      "url": "https://0k.computer/decisions/commitments/local-first.md"
    },
    {
      "id": "x0k:commitment/local-first-interop",
      "name": "local-first-interop",
      "title": "Local-First Interop",
      "status": "accepted",
      "stance": "x0k participates in the Willow protocol family at substrate boundaries. The internal data model, sync algorithms, and authority primitives are x0k's own; the wire shapes at substrate boundaries are Willow-compatible enough that other Willow implementations can be peers without x0k forking the substrate.",
      "brief": "Your data stays on your devices, and it can still be reached by software you didn't write. Local-first usually buys you independence from the cloud at the price of a new kind of isolation: every app owns its own sync substrate, so the cloud you escaped is replaced by a yard full of incompatible vendors. This commitment refuses that trade — when a friend on a different local-first app shares something with you, or you want your own content readable from another tool, the boundary speaks a shared language instead of a private one.",
      "url": "https://0k.computer/decisions/commitments/local-first-interop.md"
    },
    {
      "id": "x0k:commitment/opinionated-primitives-radical-flexibility",
      "name": "opinionated-primitives-radical-flexibility",
      "title": "Opinionated Primitives, Radical Flexibility",
      "status": "accepted",
      "stance": "The primitives — identity, sync, agent execution, provenance — are opinionated and singular. On top of those primitives the owner can build whatever software they want, including pipelines and tools nobody at x0k imagined, and compose them into publications distributed on their own terms.",
      "brief": "You should be able to build almost anything on top of x0k without fighting it — pipelines and tools nobody here imagined, packaged and shared on your own terms — and have it just work the first time. The way x0k earns that is by deciding very little for you and deciding it well: it takes a hard stance on a few primitives — who you are, how your data syncs, how agents run, how every result is traced — and then gets out of the way for everything above them.",
      "url": "https://0k.computer/decisions/commitments/opinionated-primitives-radical-flexibility.md"
    },
    {
      "id": "x0k:commitment/owner-controlled-ai",
      "name": "owner-controlled-ai",
      "title": "Owner-Controlled AI",
      "status": "accepted",
      "stance": "The owner can switch AI providers freely, run local models, and pool inference resources across the people they collaborate with. No x0k capability is permanently bound to a single provider, and no provider has privileged access to owner state.",
      "brief": "The AI that does your work answers to you, not to a vendor. You decide which provider handles which job, you can run models on your own hardware, and you can pool inference with the people you trust — so the day a provider raises its price, changes its terms, or simply goes down, your work keeps moving instead of stalling behind someone else's business decision. Nobody gets to hold your collaboration hostage.",
      "url": "https://0k.computer/decisions/commitments/owner-controlled-ai.md"
    },
    {
      "id": "x0k:commitment/validation-first",
      "name": "validation-first",
      "title": "Validation-First",
      "status": "accepted",
      "stance": "Every claim x0k makes about what it does is backed by an executable spec under x0k_eval/checks/literate/, declared as an inline yaml x0k:affordance block under decisions/design/*.md. If a claim is not declared there with a passing spec for a real platform context, it is not a property of the system — regardless of what the code looks like.",
      "brief": "When x0k tells you it can do something, you can believe it. Because agents do most of the building here, the gap between what the system claims and what it actually does would otherwise widen with every session — code that compiles, a screenshot that looks right, and a confident summary are exactly the kinds of evidence that lie. So x0k refuses to count a capability as real until an executable spec has run it end-to-end through the surfaces you'd actually touch.",
      "url": "https://0k.computer/decisions/commitments/validation-first.md"
    }
  ]
}