After workshopping the Marquette Real Estate answering service, John wanted a way to share how we work together. Not a document, not a transcript dump — something that actually pulled someone into the conversation. Something you could send to a partner or a client and have them understand the process without explanation.
We built the first one: a shareable page that looks like a text conversation. John on the right in green, Archie on the left in white. The full workshop from first message to the chapter call. It worked. Then the question became: where does this live in the system, and what else can it be?
The vault already held condensed text chapters — lessons, decisions, wrong turns. This was a different kind of artifact. Not a summary. A full record, on demand, permanently hosted. We called it a vault link.
"The vault can be whatever structure works best. Text, links, both. No startup cost either way."
Three formats emerged from the workshop:
The original instinct was to replace VAULT.md with links — the vault as a registry of URLs instead of compressed prose. That got stress-tested fast: Archie doesn't read the vault at startup, so there's no load cost either way. The idea held up. Text entries for internal chapters, links for anything worth publishing.
The bigger shift was recognizing this as a presentation layer on top of the chapter system. SESSION-NARRATIVE documents for us. Vault links document for the outside world. Same session, different output format depending on the audience and the purpose.
Every significant workshop now has the option to become a permanent, shareable artifact. Not every session needs one — John calls it when the work is worth showing. But when it gets called, the format is locked, the process is in the schematic, and a cold restart knows exactly what to build without asking a question.
The first conversation link is already live. This workshop link is the second format. The process link — the step-by-step of how to build a conversation link — will be the third.