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

Reading room · influences.sgit.ai

On this page

Reading room / influences.sgit.ai · raw text · live ↗

From influences.sgit.ai, the page as fetched on 2026-09-25 · open the live page ↗Everything on this sheet is the source site's own text; the newsroom's chrome is outside it.

Karl Popper & falsifiability

Source: https://influences.sgit.ai/register/popper/index.html↗ · markdown twin of the entry page.

An influence on Dinis Cruz — one of 25 entries in his register.

The shortest entry with the longest reach. Popper may be the influence that explains the shape of all the others' entries — including the trace table you are reading them in.

Block 1 — The anchor

The Logic of Scientific Discovery — Karl Popper — 1959

First published in German as Logik der Forschung (1934). The anchor is the demarcation criterion rather than the whole philosophy of science.

Linked, never rehosted.

Block 2 — In his own words

The reason this entry is short and load-bearing at once: it is not a topic in the estate, it is the format of the estate's outputs. A Wardley map is a claim about where a component sits, refutable by pointing at it. A risk in the risks register is a claim with a named acceptor and a named mitigation, refutable by checking whether the mitigation exists. A trace row on this site is a claim that a pattern appears at a path at a version, refutable by opening the file.

Those three formats were not designed together and they have the same shape. That is either convergence or a single inherited habit, and Popper is the most economical explanation.

The uncomfortable corollary is the one this site has to live with: an influence claim is barely falsifiable. You cannot open a file and check whether a talk caused a design decision. The trace table is the best available substitute — it makes the consequence checkable even when the causation is not — and the disclosure page ↗ states the limit rather than letting the format imply more rigour than it has.

Block 3 — The principle

A claim earns its status by being refutable. If nothing could show it to be wrong, it is not saying anything.

Block 4 — The trace table

Pattern from the anchorWhere the estate implements itVersionStatus
A claim must be refutable to be worth makingWardley mapping as practised here — a map is a claim about position and movement, refutable by pointing at a misplaced component—implemented
State the conditions under which you would be wrongThe risks register's falsifiable-statement discipline — an accepted risk with a named acceptor and a named mitigation—implemented
The demarcation applied to inspiration itselfThis site's trace tables. An influence entry is written so that it can be checked against the repositories and found wrong—implemented
Publishing the refutations, not only the claimsPartial. The gaps are published as build specs and the absent rows are kept, but no claim on this network has yet been retracted in public—partial
A test that could falsify an influence claim itselfNowhere, and probably nowhere possible. See the resonance above—absent

Three of these rows point at sibling sites rather than at code, because that is honestly where this influence lands: it shaped the format of the artefacts, not a feature. The fourth row points at this page, which is either the strongest evidence in the table or the weakest, depending on how generously you read it.

Block 5 — The gaps, as build specs

G1 — Nothing on this network has ever been publicly retracted

Every site here publishes its gaps and its open questions, which is the cheap half of the discipline. The expensive half is withdrawing a claim that turned out to be wrong, in public, with the date. A build spec: a standing /shipped/ row type for this was wrong, here is what replaced it, used the first time something qualifies. A register that only ever adds is not practising the principle it cites.

G2 — The counter-influence entry does not exist

The most Popperian thing this site could publish is an influence that was rejected — something widely assumed to have shaped the work and did not, or was outgrown. It needs Dinis Cruz rather than a build, and it is Q4 ↗ in the briefing queue. Until one exists, the register can only confirm.

Block 6 — The checklist

Block 7 — The wider library

The corpus evidence

Path in the corpusWhat it carries
(corpus-wide, ~7 files)falsifiability as an explicit standard, most visibly in the maps-as-claims framing and the risks register's discipline

CC BY 4.0 — Dinis Cruz, with AI co-authorship (Claude, Anthropic). The anchor work belongs to its author and is linked, not licensed here.