Produced with model assistance. Every page on this site, and every document in the dev packs area, was drafted with a large language model and reviewed by a person before publication. Nothing on this site is a compliance assessment, and no page claims conformity to any standard. What we do not say, and why · how every claim here is evidenced

store.sgit.ai / A working vault / paid

You bought: A working vault

£50, arriving 1 to 2 days from your payment. Nothing else is needed from you.

What happens now

A person follows up within 24 hours of the payment landing. The vault key comes by a separate message.

Nothing until the follow-up. Then clone the vault with the key.

Where the deeper material is

riskmandate.ai's page for this level carries the longer form of what is below. You do not need it to get what you bought.

See one of these now

An example, not yours

One agent, its grant of twelve capabilities, its mandate of four, and the eight-capability delta no policy covers. It is the shape of the document you have just bought, built out end to end and published so anybody can open it. Yours will be your own — your shape, your licence, and no public key on it. This one is here because a vault is hard to picture from a description, and reading one takes about a minute.

Vaultposrhzp3
Files121
Accessread-only

Open it in its own tab ↗ or read how it was published at sgit.ai.

This page opens a connection, and here is exactly which one. The surface below is the official vault interface running on dev.vault.sgraph.ai, in a frame this page builds at runtime. The key does not travel in the address: the frame is opened carrying nothing, it announces itself, and only then is the read key handed over by message with the target origin pinned — so it is not in a URL, not in history, not in a referrer and not in the frame’s storage. Replies from any other origin are ignored. It is a read key, which opens a vault and cannot write to it, and sgit.ai publishes it deliberately on that vault’s own page. Every page on this site that sells anything still opens nothing at all — this is a page you reach after buying, and a build check holds that line. One exception, stated because it is real: if the handshake does not complete within twelve seconds the component falls back to opening the vault with the key in the frame’s URL fragment. A fragment is never sent to a server and never appears in a referrer, but it is in that frame’s address. The link above avoids it entirely.

What done looks like

A vault exists, the licence file in it carries your name, the public key is off it, and you have opened it with your key.

How you check it. Your first clone. The licence file is in the tree.

About keys

Out of band, and never on a page. A vault key is never published and never committed, so it reaches you by a separate route agreed when the vault is made.