What this site ships, and what it only asserts
This site's own rule is record, never verdict. Applied to itself: what follows is a table, not a tone of voice, of what is actually built versus argued versus waiting on a human being who is not this site's author.
Every claim on this site, by status
| Status | What it means | Where it applies |
|---|---|---|
| Built | Exists and runs. | The pipeline, auto-tagging, the pre-release gate, the ten source documents published whole. |
| Position | An argued stance, not a measurement. Defensible, falsifiable, nobody has tested it against outcomes yet. | The five clauses · the inconsistency test · BYOM-first · the register's transition-by-re-point design. |
| Method published, not yet run | The procedure exists; no measurement has been taken under it. | The exit-path measurement — zero of the target fifty companies measured. |
| Pending on a human | Named because naming it is the discipline the whole site teaches. See below. | The five items blocking the register's first entry. |
| Absent by design | Deliberately not built or published, and stated as such. | Register entries · the adopters list · pricing under /service/. |
What is actually built, on this site
- The pipeline. Validate, then tag, then deploy, on every push to the release branch. Validation also runs on pull requests. How it works.
- Auto-increment tagging from a single version file, with the release commit's subject required to agree with it, the next-minor rule enforced, and historical tags backfilled from commit subjects.
- This site's own constitution as a CI check. A register entry carrying a verdict word from a published blocklist fails the build — the source's own instruction, enforced rather than remembered.
- The agent surface: llms.txt, llms-full.txt, the front page's markdown twin, a sitemap, and the brief pack fetchable as raw markdown at constructed URLs.
- Chrome from one definition. Nav, footer and the version badge are written once and stamped across every page.
Pending on a human — blocking the register's first entry
A founder-led register with an unpublished selection rule is a founder's grievances, which is the exact criticism this pack names as arriving first. So the register ships this release with its question, its schema, its governance requirements, and zero entries. Five items, none of which this site can complete on its own:
- B1 — Solicitor review of the publishing rule and the first entry, before either goes live. Review costs less before than after.
- B2 — The selection rule, published: who gets asked, and why.
- B3 — The refusal interval, published: the stated gap between the two asks that defines a refusal.
- B4 — The question template, versioned, so an entry can quote it by version.
- B5 — The authority-capture workflow, so a representative access request carries evidence of authority rather than an assumption.
Tracked with status on the comms board. None of them is quietly dropped or worked around.
Proposed, and not built
- The exit-path measurement, for any company. The method is published; the run has not happened.
- A documented, repeatable procedure for the inconsistency test. Reading marketing carefully enough to be sure is slow, and it is not yet written up.
- A method for archiving a sign-up flow retrospectively. Named as an open item.
- The register's own reader-facing markdown twins, beyond the front page.
- The parsers, the per-provider extraction workspaces described on /workflows/ — none exist yet; contributors add them as they build them.
What is deliberately not published
- Any client's personal or financial data, including the founder's own — the March pipeline ran on his statements; the workflow is publishable, the statements never.
- Any characterisation of a named company. The register publishes replies verbatim and nothing else; this is enforced by CI, not left to editorial care.
- The card-issuer lever, as an offered service, ahead of advice on the regulated-claims perimeter.
- Any legal page without its as-at date and commencement status.
- Pricing, the percentage model, and the decline-rate dashboard — reserved for /service/ once there is a service to publish figures for.
Licensing
All content on this site is CC BY 4.0, consistent with the network. The register data lives in its own vault, also CC BY — the re-pointable asset for a future move to a neutral domain or non-profit. Company replies quoted in future register entries will be quotation for reporting: verbatim, attributed, dated. Code in this repository is Apache-2.0.