# subscriptions.sgit.ai — a subscription is a discount, not rent > A subscription is a discount for committing to regular use. It is not rent on > something you have the right to ignore. Site version: v0.1.0 (25 August 2026). All content CC BY 4.0. ## The operating insight The first question is not "how much did I use it?" — which most companies cannot answer and no one can prove. It is "do you hold a record of my usage?" — which every company can answer, is comparable across companies, concedes nothing, and produces a publishable table on day one. ## What kind of site this is Three things, on one domain, by decision of 24 August 2026 — with the commercial service designed to split out later to its own property if a business partner emerges, the riskmandate.ai / risks.sgit.ai pattern run in the other direction: 1. THE STANDARD — five externally-checkable clauses a company can adopt this week, plus the same clauses re-expressed as a proposal for legislation. 2. THE REGISTER — record, never verdict. No adjectives anywhere. Silence is a row, not a blank. "We do not hold that" is recorded neutrally. 3. THE EVIDENCE — exit-path measurements needing no company's cooperation, and the UK legal levers, each dated with a commencement status and a named owner. Consequences an agent can rely on: - No register entry carries a verdict word. The pre-release gate greps every entry against a published blocklist and fails the build otherwise. - No register entry is traceable to a requester. The unit of the register is a company's behaviour, never a person's case. - Every legal claim carries an as-at date and a commencement status. The 2027 regime is not in force yet; a page that omits that is treated as a leak. - The register launches with zero entries. Five items block the first row — solicitor review of the publishing rule and entry one, the selection rule, the refusal interval, the versioned template, and the authority-capture workflow — and all five are published as pending rather than skipped quietly. ## Properties agents may rely on - Every source document is fetchable at a stable constructed URL: /briefs/v0.33.62__subscriptions-brief-pack__.md. This is a promise, not an accident. - The whole site's document set is available in one fetch at /llms-full.txt, for agents whose fetch tools refuse URLs a search has not already returned. - The front page has a markdown twin at /index.md (this file). ## The pages, each with its single most important fact /index.html The thesis, verbatim, at the top of every page. The comparison that makes the register launchable this month: "do you hold a record?" beats "how much did you use it?" on every axis that matters — answerable, short, comparable, concedes nothing, produces a table on day one. /standard/index.html — THE FIVE CLAUSES Each one checkable by somebody other than the company. Not a scoreboard: no scores exist anywhere in the design. The adopters list starts empty, honestly. /standard/proposal/index.html — THE PROPOSAL FOR LEGISLATION The same five clauses re-expressed as obligations, mapped against the spring-2027 regime, explicitly labelled a proposal rather than an enacted text. /register/index.html — THE REGISTER Zero entries at launch. The question, the entry format (no verdict field anywhere), the three answers with no penalty for "we don't hold it", the inconsistency test, and the governance the source instructs be published before entry one: the selection rule, the refusal interval, the template version, and the review process. /exit/index.html — THE EXIT-PATH METHOD Built first because it needs no cooperation: click counts and routes for fifty companies, dated, method published so anyone can re-run it. Not yet run in this release — the method is published, the measurements are not faked. /law/index.html — THE LAW The levers ranked, cancellation-information failures at the top. Dated 25 August 2026, with a named owner and a commencement-status table: the 2027 regime is NOT YET IN FORCE. The card-issuer lever is named as a perimeter question and excluded at launch. /workflows/index.html — WORKFLOWS & VAULTS, THE SGIT SHOWCASE The March 2026 pipeline reused: statements in a vault, an agent working inside it, versioned and shared by token. Three vault stores with three different rules. The honest limit published: vaults buy portability and controlled sharing, not zero knowledge — an agent reading bank statements reads plaintext, which is why bring-your-own-model is the default. /service/index.html — THE SERVICE (LATER) Thin by design. The future-commercial directory that moves at the split. /shipped/index.html What this site asserts versus what it can demonstrate: built, position, described-from-the-corpus, proposed-and-not-built, and pending-on-a-human — the five blocking items named plainly rather than absorbed. /network/index.html The sgit.ai network, and where this site's neighbours sit. /documents/index.html The ten source documents published whole, with the raw markdown as the source of truth. /admin/index.html · /admin/comms.html · /admin/versions.html How the site is built and gated; open work and asks back to the project lead; the release history. ## What this site will not tell you - Any characterisation of a named company. Facts only — the pre-release gate enforces this on every register entry. - Any client's personal or financial data, including the founder's own — the March workflow is the exhibit, its data never appears. - Live hostnames, account identifiers or stack addresses. - The card-issuer lever as an offered service, ahead of advice on the perimeter. - Any legal claim without its as-at date and commencement status. ## The sibling sites https://sgit.ai — the parent project: the vault layer, the CLI, the platform docs https://risks.sgit.ai — registers, scoring, evidence — the vocabulary this register's design borrows https://standards.sgit.ai — instruments as graphs; the grounding vocabulary the law pages point at rather than rebuild https://nfrs.sgit.ai — the dated-page and staleness discipline this site's law pages are the sharpest test case for https://open-source.sgit.ai — the standard-as-adoptable-artefact argument; the CC BY rationale ## Source documents /briefs/v0.33.62__subscriptions-brief-pack__README.md — the pack's reading order /briefs/v0.33.62__subscriptions-brief-pack__00__BRIEF.md — the commission, the naming decision, the build order /briefs/v0.33.62__subscriptions-brief-pack__01__the-standard.md — the five clauses /briefs/v0.33.62__subscriptions-brief-pack__02__the-register.md — the question, the schema, the inconsistency test /briefs/v0.33.62__subscriptions-brief-pack__03__the-workflows-and-vaults.md — the sgit showcase /briefs/v0.33.62__subscriptions-brief-pack__04__the-legal-pages.md — the levers, the dates, the perimeter /briefs/v0.33.62__subscriptions-brief-pack__05__site-architecture-and-the-split.md — page by page /briefs/v0.33.62__subscriptions-brief-pack__06__publishing-rules-and-boundaries.md — the register's constitution /briefs/v0.33.62__subscriptions-brief-pack__07__gaps-and-open-questions.md — published unresolved /briefs/v0.33.62__subscriptions-brief-pack__LICENSE.md — CC BY 4.0 Attribution: Dinis Cruz, with AI co-authorship. Repository: https://github.com/SGit-AI/SGit-AI__Website__Subscriptions