MyJackfruit

Help
Browse topics · Words and meanings

Words and meanings

← Words and meanings

What are system vaults, and why can't I make one?

Checked against GilbApp 96968de.

A system vault is a vault GilbPlatform runs for its own data; no one else can take its name, and only GilbPlatform can make one.

Deeper

A vault is the place where a person or a group keeps their records. A system vault is held by GilbPlatform itself rather than by a person or a group, such as veda.gilb.com, where GilbVeda, the shared list of terms, is kept.

No one can take a system vault's name for a vault of their own. A vault name is used once on GilbPlatform: a name someone has is taken. Names GilbPlatform keeps for itself, such as kaizen, veda, id and support, are reserved, and so is any name shorter than 3 letters or digits. Others are kept too, such as geo, life, connect, books and maintain, and words the service uses in its own addresses, such as www, mail, app and vault; GilbPlatform can reserve more. Capitals and signs do not get round it: Kai-Zen counts as kaizen. A longer word that only starts with a reserved name, such as supporter, is not reserved. At sign-up the line under Vault name then says is a reserved name — please choose another.; in Create a vault the name is refused when you press Create vault, and the window shows the reason in red.

What makes a vault a system vault is a mark on it saying that GilbPlatform holds it. Only GilbPlatform itself can write that mark; it refuses the mark from anyone else, the vault's owner too. So you cannot turn your own vault into a system vault, and no one can turn a system vault into theirs. System vaults are made with a tool that the people who run GilbPlatform start on its own servers; GilbApp has no way to make one.

GilbPlatform refuses every request to delete a system vault. The refusal sits in the one step every vault delete goes through, and a system vault anywhere inside a vault being deleted stops the whole delete. The mark can be taken away only on GilbPlatform's own servers. GilbApp today has no button to delete a vault at all.

You never sign in to a system vault. You sign in to your own vault, and a system vault is reached the way any other vault is: by access given to you, or because it is public, readable by anyone. Being a system vault gives no one extra access and takes none away. Some system vaults can be read without signing in: GilbVeda's terms, for example, answer anyone who asks. Opening a vault in GilbApp changes which vault you look at, not who you are signed in as: SIGNED IN AS under MORE · OTHER ADDRESSES still shows the address you are signed in as, whichever vault you open.

This answer is written for a computer screen.

Source: GilbVeda t:PlatformCustody a:does ("A vault operated by the Gilb platform (E10). The value of a:vaultCustody on veda, id, geo, kaizen, books, connect, planguageglossary and admin.", Approved) and t:AccountCustody ("A vault operated by an account holder … the ONLY custody value that does not itself refuse a tombstone."), public read https://veda.gilb.com/base/terms?q=… 2026-11-10; NOT t:SystemVault, whose live text now names any tenant namespace. GilbPlatform 4d008a55367a6e7453920c463a8923df37de62e9 (https://id.gilb.com/version), code read at 4d008a55: src/auth/reserved-names.ts:18-21 (normalizeName: lower case, a-z0-9 only), :41-75 (DEFAULT_RESERVED_NAMES: system hosts kaizen, veda, geo, id, skills; life, connect, books; maintain; support (GilbSupport help vault (support.gilb.com)); requirements; structural base, lws, i, me, api, auth, login, signup, onboard, app, vault, pod, well-known; infra www, mail, mx, ns, ns1, ns2, cdn, static, assets, root, status; near-forms such as supporter stay claimable), :88-99 (RESERVED_NAMES adds more per server), :139-140 (3-character minimum); src/write/ingest.ts:320-331 (a:vaultCustody a reserved control-plane fact), :556-600 (a non-system write of it refused 403); src/auth/vault-provision.ts:161-169, :215 and scripts/mint-system-vault.ts:242 (the only writer of t/PlatformCustody), src/auth/vault-provision.ts:468-474 (declassify, system side only); src/authz/vault-tombstone.ts:165-171 (one primitive, whole sub-tree in one transaction), :199-237 (custody gate fail closed: only AccountCustody permits; legacy class guard); src/routes/vault.ts:668-686 (POST /base/vault/delete runs through it, soft delete). Developer guide docs/BASE-DEVELOPER-GUIDE.md §4.7a :4394-4406 (mint-system-vault.ts run on the machine that serves the store), §5.7 :6092-6146 (purpose confers nothing and takes nothing away; you never sign in to a system vault; the declaration is not yours to write, 403 whoever you are; declassify is system-side) — the roster and the undeclared-vault sentence there are older than the code, code used; §15.1 :10721-10739 (sign-in is to the personal vault; navigation is not sign-in). GilbApp af0f04ee838a4d55887d2ff1f72edd49a4ff7ca0: no vault delete control (src/admin/adminApi.ts:25, src/admin/VaultHierarchyView.tsx:13: removed), create only through create-named (src/lib/base/createVault.ts); src/components/VaultDetail.tsx:261-290 (Signed in as under the toggle shows the session principal). Public read of GilbVeda terms with no sign-in: https://veda.gilb.com/base/terms?q=SystemVault, 2026-11-10, 200 with terms. Shared sentences word for word: A vault name is used once on GilbPlatform: a name someone has is taken.; vault gloss; GilbVeda gloss; reserved-name sentence; is a reserved name — please choose another.; "refused when you press Create vault, and the window shows the reason in red"; public = readable by anyone.