The workflows, and why this is the sgit showcase
Summary
The document behind /workflows/. It traces the service's plumbing to a pipeline already run in March 2026 — statements shared into a vault by short token, an agent working inside the vault, committing and pushing back — and argues that only the destination changes: parsing a ledger becomes parsing a subscription inventory, and the accountant-ready pack becomes a claim file. It defines three vault stores with three different rules: the person's own vault holds anything identifying them; the public register vault holds only company behaviour, never a person's case; and per-provider parser workspaces are the crowdsourced asset, so one person's parser becomes free for everyone after. Its most important discipline is publishing the honest limit of the vault claim: vaults buy portability and controlled sharing, not zero knowledge, and an agent reading bank statements is reading plaintext — which is why bring-your-own-model is the default rather than the hosted option. It closes with the SAR workflow's own constitution: every access request is genuine, never leverage, tested for merit before it is sent, with the decline rate published.
Key concepts
Key ideas
- "Only the destination changes" — the novel work is the legal mapping and the claim file, not the plumbing.
- The unit of the register is a company's behaviour, never a person's case.
- Being the meter puts the operator in the request path, and the content here is bank statements — so BYOM is the default, inverted from the usual ordering.
- No new infrastructure was invented for this business: it was assembled from primitives that already existed.
On this site
Published as /workflows/, as the sgit business-model showcase this pack instructs be featured from sgit.ai and the wider network.