Content-Transformation Proxy, a published vault
A three-part as-built engineering brief published as a documentation site inside a vault: ten authored slides, a diagram library and the source PDFs, all served from one read key.
Source: https://sgit.ai/demos/vaults/content-transformation-proxy/index.html↗ · site v0.6.8 · this file is generated from the same content as the page, so the two cannot drift. Every page on this site has a .md twin; internal links below point at them.
Home↗ / Vaults↗ / Content-Transformation Proxy
Content-Transformation Proxy
"The proxy that shows you only what your policy allows." A request passes through mitmproxy, a service injects a transformation script, and the page is rewritten before the user sees it. This vault is the as-built write-up, three parts, ten authored slides, a diagram library and the original source decks, published as one navigable documentation site.
Open it yourself. The key is the whole credential.
Read key: sgit_public_read_18bf8b2aa558fec879edb39c79ee66d6b9594ada2dff71039b3f66f5b14e4839:3c90c2bff2b1
In the official UI: open it read-only in a new tab ↗ · From the CLI: sgit clone sgit_public_read_18bf8b2aa558fec879edb39c79ee66d6b9594ada2dff71039b3f66f5b14e4839:3c90c2bff2b1
Published deliberately, and derived one-way from a vault key that is not published and never will be.
See it live, here
Both surfaces open automatically below. You can also open the app in its own window ↗ ↗.
What is in it
the shape
A dev brief that reads like a site, not a folder of PDFs
Nine sections across the top (Overview, Architecture, Vault, Deployment, Slides, Diagrams, Decks, Gallery, Sources) over material from a three-part dev brief dated 11 June 2026. Each part is written up in full with its slides and architecture diagrams placed inline, plus a deck viewer, a diagram library and a reader for the original PDFs.
Two deployment modes are worked through: an inline proxy, and a streamed remote browser where a container runs one browser per user and only pixels reach the client, "nothing to install, all you need is a browser."
The overview: the thesis, the flow through mitmproxy, and the as-built provenance line.
the point
Source material and finished explanation in the same object
The vault carries the rendered site, the ten authored infographics, the architecture diagrams, and the source PDFs the write-up came from. A reader who doubts the summary can open what it was made from without asking anyone.
That is the property a document attachment loses the moment it is emailed: the explanation and its evidence stop travelling together. Here one read key moves both.
The vault browser: the rendered site, the diagram library and the source decks in one tree.
Notes
Checked before publishing. No client, no third-party project, no external company, no contact details, in the text, and by eye across the slide and diagram images that a text scan cannot read. The only third-party product named is NotebookLM, as the tool that produced three blueprint decks. "permissions": {}.