MyJackfruit

Help
Browse topics · Vaults and access by API

Vaults and access by API

← Vaults and access by API

Who owns a vault's ownership facts?

Short answer

GilbPlatform alone writes the facts saying who holds a vault and whether it is a system vault; no owner or app can change them.

Deeper

A vault is the place where a person or a group keeps their records. A few facts about each vault decide who holds it and how it is protected, such as who holds it and whether it is a system vault, one GilbPlatform runs for its own data. GilbPlatform writes them itself, when a vault is made and in its own steps, never from what a request sends.

A write through the API that adds, changes or removes one of them is refused with 403, for everyone: the vault's owner and the account that runs GilbPlatform too. The message says the fact is a control-plane fact, written only by the system. Sending the same value back unchanged, as a full write of a record does, is accepted, and nothing changes.

So a vault's holder cannot make their vault a system vault, which GilbPlatform never deletes, and through the API no one can take a system vault for their own or strip its protection; only the people who run GilbPlatform can take the mark away, on its own servers; the answer on system vaults says more.

Holding a vault is not the same as every kind of access to it: who may read, write or manage access comes from grants, which a holder of Control gives with the grant calls; the answer on granting access by API shows them.

What a vault stands for, such as a person or an organisation, is not one of these facts: its owner can set it with POST /base/vault/set-represents, sending vault, the vault's @id from GET https://id.gilb.com/lws/vaults (not its vaultId), and represents, the full GilbVeda type address; a program signed in as itself cannot.

Not checked on production: this is from GilbPlatform's code.

Source: GilbPlatform 498d29a0 (live at https://id.gilb.com/version, read 2026-11-11): src/write/ingest.ts:330-420 (CONTROL_PLANE_ATTRS at :375: the vault deed facts, the system-vault class, custody, the owner's app approvals; why: a holder could otherwise make their vault undeletable or strip a system vault's protection), :641-705 (assertNoForgedControlPlane at :670: only SYSTEM_WRITER; even an owner via /base/ingest may not plant a vault deed; byte-identical re-assert accepted; forge, change or omission → WriteForbiddenError 403 Attribute '…' is a control-plane fact, written only by the system (…)); src/routes/vault.ts:419-480 (set-represents, :426, :429: the caller must own the vault; a:podRepresents is not control-plane). The reserved facts are not named on the page (row note: naming them guides probing). Shared with vaults/what-are-system-vaults-and-why-cant-i-make-one ("Only GilbPlatform itself can write that mark; it refuses the mark from anyone else, the vault's owner too."). GilbVeda (public read https://veda.gilb.com/base/terms?q=control%20plane, 2026-11-11): t/ControlPlaneAttributeMarker (Suggested) DECLARES AN ATTRIBUTE TERM TO BE CONTROL-PLANE.: src/write/ingest.ts:641-705 (the API refuses the write for everyone), :371-420 and src/auth/vault-provision.ts:453 (declassifyVault, run by scripts/declassify-vault.ts on GilbPlatform's own servers), as the system-vaults answer (The mark can be taken away only on GilbPlatform's own servers).: src/routes/vault.ts:122 (vault is the vault ENTITY address, not the vault_id namespace), :441 (A machine credential cannot set a vault's purpose-type — the vault owner does), :455 (400 vault is not a known vault entity); Row: Security.VaultOwnershipFactsPlatformOnly.

Checked against GilbApp d529620.