MyJackfruit

Help
Browse topics · Who sees what

Who sees what

← Back to How do I get access to a vault someone else owns?

Why does a vault I cannot reach look like it is not there?

Short answer

Because GilbPlatform answers for what you may not read just as for what does not exist, so no one learns what others keep private.

Before you start

Words used here (1)
GilbPlatform
GilbPlatform is the service that keeps people's and organisations' data in vaults, each at its own web address.
Deeper

Also asked:

Someone told me about their vault, but I cannot see it. Why? You see only vaults you can reach, and GilbPlatform answers for what you may not read as for what does not exist. Ask them for access: someone who holds Control on that vault can give it to you.

A vault is the place where a person or a group keeps their records; a record is one piece of data with its own address, such as a person, a place, a thing or a note. When you ask for a record you may not read, GilbPlatform gives the same answer as for a record that does not exist or has been deleted. The same holds for the list of a vault's records. The list of who has access to a vault is shown only to whoever holds Control there, who decides who else may read or write; anyone else is told there is nothing. So no one can find out, by trying addresses, what someone else keeps private, or that a private record is there at all.

In GilbApp today, Your vaults lists every vault you can reach, one card each, so a vault you cannot reach has no card. The search reaches every vault you can read, your own and those others have given you access to, and only what you may read in them. A name finds only people who made themselves findable or made their vault public, or whom you already reach. A record you open by its address but may not read shows "This vault didn’t return this record. It may have been deleted, or your access may not reach it.", with the vault's name in place of This vault when GilbApp knows it: GilbApp cannot tell which it is, because GilbPlatform does not say.

Some things are not hidden. Your vault's address is public, and it gives no access to what is in the vault: opened in a browser, a vault's address shows a short page headed Vault that says This address is a vault: and the address, and nothing the vault holds. So anyone can tell that a vault with that address exists, and the sign-up name check says is taken for a name that is held; what stays hidden is what the vault holds. A vault made findable by name can be found by its name, as the answer on making a vault findable by name shows, and a public vault can be read by anyone, signed in or not.

A change you may not make is refused openly instead: GilbPlatform answers that it is not allowed. On a record you may only read, the boxes cannot be changed and the card says You can read this item but not edit it.

Each record is read inside its own vault. GilbPlatform decides access in the vault the record lives in, so access to one vault never opens a record kept in another, even when the two addresses end in the same code; asking one vault for a record kept in another gets the same answer as for a record that does not exist. Access reaches a vault where it was given there, where the vault is public, through the vault around it, or onward from a vault given access with Passes up hierarchy; the answer on whether access given to a vault reaches the vaults inside it shows the first three, and the answer on giving your AI access to a vault the last.

If a vault or record you expect is not there, someone who holds Control on that vault can give you access; the answer on sharing a vault with a person shows how they do it. SIGNED IN AS under MORE · OTHER ADDRESSES in a vault's pane shows the address you are signed in as, if you are not sure which account you are using.

This answer is written for a computer screen.

Source: GilbPlatform 4d008a55367a6e7453920c463a8923df37de62e9 (https://id.gilb.com/version 2026-11-10), code read at 4d008a55: src/lws/routes.ts:146-150 (GET /lws/r/:id: 404 non-disclosure when absent OR unreadable OR DELETED); src/authz/authorize-read.ts:45-50 (forbidden and absent are indistinguishable … an identical 404); src/lws/container.ts:15-18 (a container not readable gets the IDENTICAL not-found result); src/routes/consent.ts:107-133 (GET /base/consent/vault-acl: 404 for a caller without Control, no ACL, no existence signal); src/auth/served-host.ts:136-143 (an unregistered host gets the same non-disclosure 404 a registered-but-ungranted host returns); src/auth/errors.ts:6-16 (401 vs 403 vs the 404 non-disclosure: a refused write is 403); src/routes/computer.ts:631-635 ("The same answer for a missing record and for someone else's record. A 403 would say that the record exists."); src/onboarding/vault-document.ts:198 (This address is a vault:). Developer guide docs/BASE-DEVELOPER-GUIDE.md §5.3 :4994-5003 (read decided over current state and within the target vault, so a URI-id collision across vaults cannot leak; anonymous default-deny), §5.6 :6008-6091 (403 write / 404 read; anonymous write 403, read 404 non-disclosure), §16.2 :10799-10810 (detail routes 404 unless the Host matches the vault), §9 :8016-8018 (every search result access-filtered). GilbApp af0f04ee838a4d55887d2ff1f72edd49a4ff7ca0 (https://gilb.com/app/version.json): src/components/records/RecordDetail.tsx:332-358 (the 404 non-disclosure comment and "${askedVault ?? This vault} didn’t return this record. It may have been deleted, or your access may not reach it.", header Record); src/lib/base/records.ts:686-696 (a 404 read is null); src/lib/base/entityWriteAccess.ts:113 (You can read this item but not edit it.); src/components/VaultDetail.tsx:261-290 (Signed in as). Rows: Capability.Security.NoAccessLooksLikeNotThere (G:5891 §5.6, computer.ts:620-640; note Writes without a grant answer 403, reads answer 404; say both.), Capability.Security.VaultsCannotReadEachOther (G:4885 §5.3, predicate.ts). Shared sentences word for word: vault and record glosses; Your vaults lists every vault you can reach, one card each; the search sentence; the name sentence; the address sentences (made general: a vault's address); Your vault's address and your profile are public by design; On a record you may only read, …; public = one anyone can read.

Checked against GilbApp d529620.