View a policy, buy a policy: the store linked, pricing as the four levels, the vault pages open on the vault itself, and the Lab steps back

The store is live, so the site can say buy. store.sgit.ai↗ put its four levels up on 15 September, one price each: the pack by email for £5, a working vault for £50, corrected for your situation for £500, two sessions and a professional's signature for £1,500. The homepage's hero now offers two things, view a policy↗ and buy one, and its closing panel says the same; every vault page carries buy this policy to the store's page for the same application (the store uses this site's slugs); and Pricing↗ is rebuilt around the four levels, each row linked to its level at the store, with the store's own ledger states copied beside them: two of the four exist and run, two are specified and have never been sold once. The three platform tiers the page used to describe, and the conformity-adjacent line under one of them, are gone.

The third level is a prompt you run. The lead's memo of 15 September says what the £500 level actually is: we give the customer a prompt, they run it where the agent runs, they send back what it found, and we build, correct and return the vault with a note of what changed. The prompt already exists and travels in every vault as MAP-A-GRANT.md. The pricing page now writes the workflow out in five steps↗, with what does not arrive stated beside what does. The brief behind it, a policy per use case, and the £500 level is a prompt the customer runs, is in docs/briefs/, with our own Voice Debrief workflows as the first two use-case vaults to build.

The vault pages open on the vault. The lead's reading of a vault page↗ was that it was confusing, and it was: this site's tables, then the vault's renderer booted in a sandbox by this site, then a loader page that announced it was a static copy. Nothing on it was the product as a buyer receives it. It now opens on See it live: two frames, both the official SG/Vault interface opened read-only by the host with the key handed over the page's handshake, never in a URL. The first is the vault's own app, what whoever is handed the policy sees; the second is the vault browser, every file in the tree, the history, and the app under index.html. That is how sgit's own demo pages show a vault, and it is the mechanism this site's live-demo pages have used since v1.0.0. The sandboxed copy and the button to the loader are gone from the page; the sections are numbered once. The review, and the change it asks for next — stop deploying a copy of the vault from this site at all — is docs/briefs/review__vault-pages-vs-the-vault.md and task brief T09.

The Lab steps back from the top level. Eight top-level entries was one too many for the header, and the Lab is where we argue, not where a visitor starts. It is now The Lab under More; its seven entries are unlisted and reached from the Lab page↗, as before.

Two voice memos registered. The transcripts of the graph memo and the use-case memo arrived as files and are in the brief register↗ as D7 and D8, byte for byte, with what each produced and what each is still owed. Thirteen items now, and the pricing item the first informal entry has carried since 11 September is done.

Not done, and not verified here. The host's vault-browser embed was wired from sgit's own embed script and could not be exercised from the container this was built in, which cannot reach the host; if a frame does not open, the status chip says so after twenty seconds and the open in its own tab link beside it carries the same key. The site still carries a copy of every vault under site/vaults/, which is the next change and not this one. The Voice Debrief vaults are the workflow-owning agent's to produce. No page on this site collects a payment; the store does that on the payment provider's pages.