sgit newsroom v0.1.29 · snapshot 2026-09-24

Reading room · vaults

On this page

Reading room / vaults · raw text

From vaults, a file in the seed packEverything on this sheet is the source site's own text; the newsroom's chrome is outside it.

← The risks · Index · Mock-ups →

10 · Why it is open, and what to open

This plan is published with a read key on a public website, and everything in it may be taken and used. That is not generosity. It is the strategy, for the same reasons the companies behind sgit.ai run on it.

The technology is not the moat

Nothing here is hard to copy: a chat session, a public repository, a free static host. If the plan depended on keeping that secret it would not be a plan. What is hard to copy is fifty customers who trust you, a playbook with a year of mistakes in it, and the referrals that come from doing it well. Those are earned, not protected.

Open makes the customer safe, and safety sells

The customer owns a public repository, a playbook they can read, and a vault they hold the key to. If the operator disappears, nothing is lost. That is the honest answer to the question every small business asks about every supplier, and being able to give it is worth more than any feature.

Open makes the Wide path possible

A hundred independent operators following one playbook is a category. The original company's role becomes the tooling, the training, the templates and the vault service every operator needs, which is a better business than being one operator, and it only exists if the playbook is open.

What to open, concretely

OpenKept
This plan, and every revision of itThe operator's customer list
The playbook and the setup checklistEach customer's vault (theirs, not public)
The templates and the mock-upsPrices actually negotiated, if they differ from the published ones
The change logs of customers who agree, as marketingAnything a customer sent that was not for publication
The numbers: setup hours, maintenance minutes, churn, in aggregateIndividual customers' numbers

The one thing to send back

If you run this and something breaks, or a rule turns out wrong, or a price was off by half, write it down and send it. The plan improves the same way the vaults on sgit.ai did: every mistake became a rule that the next person did not have to learn.


← The risks · Index · Mock-ups →