/claims

Condition report.

Nothing here asks to be believed. Clone it and check.

Every claim on this site, including the ones we cut. One row per claim: the sentence, the source, the day we last checked it, and how strong the proof is. Every number on a website is a claim about today, so the date is when we checked, not when somebody wrote it.

The struck rows at the bottom were on our GitHub profile until we built this site. They did not survive it.

claims · sources · dates · last full pass 2026-08-14

The site itself

The site's own claims and their verifications
Seam stampClaimVerification
Zero external requestsOpen the network log; it is this site alone.
Zero cookiesThere is no consent banner because there is nothing to consent to.
Shell: 12.8 KB gzippedgzip -9 over the shipped shell files, measured at this build. The previous shell published 32.2 KB; this is a different shell, so the number is measured again rather than restated.
Every count is a file count from a public repositoryClone and count.

The catalogue, counted

Every figure below is read from products.json, which is generated from the repositories themselves — a number on this page is a number in a repo. Beside each figure, the command or file that reproduces it.

The catalogue's counts, licences and states, from products.json
Seam stampClaimVerification
№01 inter.faceruns today · MIT
10 check groups — grep -c '^== ' <check.sh output>
22 assertions — grep -c 'ok:' <check.sh output>
9 routing-table counts verified against wc -l — check.sh: 'all 9 routing-table counts match wc -l'
14 cross-file pointers resolved — check.sh: 'all 14 cross-file section pointers resolve'
№02 chaptersbackend only · MIT
14 agent tools over MCP — grep -c 'server.registerTool(' over *.ts
243 tests green in public CI — run 30161196101, 2026-07-25: 113 client + 130 server
№03 webcrabruns today · MIT
9 loops — ls loops/*.md (10) minus 1 declared in PIPELINE.md as 'a mode rather than a loop': 09-rerun.md
9 worker agents — ls agents/*.md
4 human gates — gate table rows in PIPELINE.md: A, B1, B2, C
9 deploy targets — ls deploy/*.md, excluding README
№04 portfolio.meruns today · MIT
9 loops — ls loops/*.md (10) minus 1 declared in PIPELINE.md as 'a mode rather than a loop': 09-rerun.md
8 worker agents — ls agents/*.md
4 human gates — gate table rows in PIPELINE.md: A, B1, B2, C
9 deploy targets — ls deploy/*.md, excluding README
№05 git-a-profileruns today · MIT
5 loops — ls loops/*.md (5) minus 0 declared in PIPELINE.md as 'a mode rather than a loop'
3 worker agents — ls agents/*.md
№06 systemcicyread only · no licence — all rights reserved
9 loops — ls loops/*.md (10) minus 1 declared in PIPELINE.md as 'a mode rather than a loop': 09-extend.md
9 worker agents — ls agents/*.md
5 human gates — gate table rows in PIPELINE.md: A, B, C, D, E
№07 vectoryresearch only · MIT
12 architecture diagrams — ls diagrams/
№08 yildizimnot public · closed source
Nothing about it is public, so nothing here is counted. The frame below is empty on purpose.

The proof ranks

1
Measured, dated, and reproducible by a stranger. You can run it
2
You can go and see it. A file, a licence, a log
3
A named third party said it, and we link to them saying it
4
Real, and you cannot check it from outside. Hedged wherever it appears
5
Asserted, with nothing behind it. Nothing on this site is rank 5. Rank 5 is the bottom of this page, struck

Rank 1 — run it yourself

Measured, dated, and reproducible by a stranger
Seam stampClaimVerification
ALL CHECKS PASS on a fresh clone · 10 check groups, 22 assertionsinter.face/scripts/check.sh, run against a fresh --depth 1 clone.
where: home fold · /pipelines/inter.face · checked 2026-08-14
and the caveat, printed in the same row: the script checks line counts, structure, JSON validity and every relative link. It does not check whether a sentence is truethe script’s own source, 120 lines, no dependencies beyond coreutils and jq.
where: same · checked 2026-08-14
243 tests pass on every commit, 113 client and 130 server, against a real Postgres container, on public CIrun 30161196101, 2026-07-25: 113 client + 130 server. GitHub Actions, branch dev, workflow ci.yml: public repository, public log, timestamped by GitHub.
where: home panel 02 · /tools/chapters · checked 2026-07-25
14 agent tools in the Chapters servergrep -c 'server.registerTool(' over *.ts → 14.
where: home panel 02 · /tools/chapters · checked 2026-07-25
12 architecture diagrams, and no buildls diagrams/ → 12, and there is no src/.
where: home panel 07 · /tools/vectory · checked 2026-07-20
Every dot in the catalogue is one file counted in a public repositoryls in each repository named on its own row, and the build guard that asserts every drawn point against its printed count and fails the deploy when they disagree.
where: home, the whole catalogue · checked 2026-08-14
The same campaign costs $0.06 or $32.25 depending on which model runs it, priced from a table labelled “as of 2024”node utils/cost-estimator.js estimate 5 5 5, reproduced exactly from a fresh clone, zero dependencies.
where: /pipelines/website-pitch-pipeline · checked 2026-08-14 · price data 2024

Rank 2 — go and see it

A file, a licence, a log. You can go and look
Seam stampClaimVerification
Six of the eight in the catalogue are MITthe LICENSE file in each repository, linked per row.
where: home catalogue · /hosted · checked 2026-08-14
systemcicy has no licence file, so all rights are reserved and you may not use itgh api repos/PIIIX-org/systemcicy/contents/LICENSE → 404, and the README has no licence section.
where: home panel 06 · /hosted · checked 2026-08-14
Notes are plain markdown files on disk, in Google’s Open Knowledge Formatchapters/README.md, and the Open Knowledge Format specification, which is public and somebody else’s.
where: /tools/chapters · checked 2026-07-25
Embeddings are computed on the instance, so note content is not sent anywhere to be indexed. We have not published a test that proves it. This is what the code is built to do, read from a dated design document in a public repositorychapters/README.md and docs/2026-07-17-tech-stack-decision.md.
where: /tools/chapters · checked 2026-07-25
Chapters has live-preview markdown editing and a search overlay, built and tested, and you cannot use it, because nothing is deployed84 files in client/src, 113 client tests green in the run above. No deployment exists in any repository in the organisation.
where: home panel 02 · /tools/chapters · checked 2026-07-25
Two people have ever contributed to these repositoriesthe contributor list on each public repository. Public and linkable.
where: /about · /hosted · checked 2026-08-14
Nobody outside the organisation has ever contributedsame as c12.
where: /about · checked 2026-08-14

Rank 3 — somebody else said it

A named third party said it, and we link to them saying it
Seam stampClaimVerification
Lovable raised $330M in December 2025TechCrunch, 2025-12-18, and Lovable’s own Series B post.
where: /tools/vectory · checked 2026-08-14 · claim dated 2025-12-18
Anthropic ships a code-powered prototyping tool on its flagship model, and it is conversational rather than a drag-and-drop canvasAnthropic’s own announcement page.
where: /tools/vectory · checked 2026-08-14
Onlook is Apache-2.0 and covers canvas editing and code generation for Reactthe repository’s own licence and description.
where: /tools/vectory · checked 2026-08-14

Rank 4 — real, and you cannot check it

True, unverifiable from outside, and hedged everywhere it appears
Seam stampClaimVerification
Eight of the ten people on the developers team have never opened a pull request. The team roster is not public; the pull requests aregh api orgs/PIIIX-org/teams/developers/members, cross-checked against public pull-request authorship.
where: /about · checked 2026-08-14
Three of the six roles named in CONTRIBUTING.md have no GitHub team behind themgh api orgs/PIIIX-org/teamsdevelopers, managers, reviewers. The other three do not exist.
where: /about · checked 2026-08-14

What did not survive

A claims page listing only the claims that survived is an advertisement. These sat on our GitHub profile, in our READMEs, or in this site’s own design documents. We removed each one for the reason printed beside it. Two are still live on the GitHub profile as this ships, which is a job on a list and not an excuse.

Struck. Every row was a claim we made, and none of them survived being checked
Struck marker the claim, as written why it is struck
strucks01 “Yildizim shipped and running today, inside Chapters”Searching the whole Chapters repository finds the name in three markdown documents and zero times in client/src or server/src. There is no deployment anywhere in the organisation. It described a specification.
where it was: the GitHub organisation profile · checked 2026-08-14
strucks02 “Zero axe violations”It is a rule the pipeline enforces on the work it builds. No axe report exists in any repository. We have never measured a PIIIX product against it. We publish this site’s own axe result in this row when we measure it, or the row stays as it is.
where it was: an aspirational rule inside our own pipeline markdown · checked 2026-08-14
strucks03 “A pull request doesn’t merge without a passing CLA check”The check runs on every pull request. The branch it merges into has no protection, so nothing is required, and the allowlist exempts the only person who merges anything. True version: every pull request runs a CLA check.
where it was: the GitHub organisation profile · checked 2026-08-14
strucks04 “Built by our team and contributors who earn it”It has never happened. Two people have contributed and both are members of the organisation.
where it was: the GitHub organisation profile · checked 2026-08-14
strucks05 “~17.6k GitHub stars” (about a competitor)It is 26,482. The same document tells the reader to re-verify anything load-bearing before acting on it. We did not.
where it was: our own research document, dated 2026-07-07 · checked 2026-08-14
strucks06 “5,983 lines across eleven reference files”The eleven files total 5,493. It is one of the few numbers our own checking script does not guard, which is how it survived.
where it was: inter.face/README.md · checked 2026-08-14
strucks07 “6,600 lines of refusal” · “72 techniques” · “48 styles” · “30 styles”No counting rule reproduces any of them. They stay off the site until a rule is written down and the script enforces it. Unresolved, and named rather than quietly dropped.
where it was: four READMEs · checked 2026-08-14
strucks08 “4,691 characters”Five definitions were tried and the closest came to 4,669. The thing the number described is verified; the figure was not. Struck during the build that produced this page.
where it was: this site’s own design document, about its own fallback page · checked 2026-08-14
strucks09 “0.27s” · a duration for how long the checking script takesIt is a fact about the machine it ran on, not about yours. This site publishes no duration for anything, and this struck row is the only place the figure appears. Your own run supplies the number, which was the argument in the first place.
where it was: this site’s own design comp, printed twice, in its most load-bearing block · checked 2026-08-14
strucks10 “Each of six roles is backed by a GitHub team”Three teams exist: developers, managers, reviewers. Designer, Docs/Content and Community/Support have none.
where it was: CONTRIBUTING.md, repeated on the organisation profile · checked 2026-08-14
strucks11 “Open-source, AI-native tools”, unqualifiedSix of the eight in the catalogue are MIT, one has no licence at all, and one is closed. The word needed a scope and did not have one.
where it was: the GitHub organisation description · checked 2026-08-14
strucks12 “37 pull requests, all merged” and “60fps at 371,355 notes”Both are true and neither is checkable: the repository is private, the frame-rate reading has no published hardware, and the note count is a synthetic scale mode rather than anyone’s real notes. A number you cannot check is worth nothing on a page like this one.
where it was: yildizim/README.md, about the closed product · checked 2026-08-14

When each of these gets checked again

A number stops being true without anybody editing it. This is the list of what rots, how fast, and who is supposed to notice. Taha Mahmoodi owns every row, because there is nobody else.

The re-check schedule. Owner: Taha Mahmoodi. Last full pass: 14 August 2026
whatre-checked
c02 243 passing testsevery release, and before this site is redeployed
c01 ALL CHECKS PASSevery release
c03 14 agent toolsevery Chapters release
c06 the cost estimator’s $0.06 – $32.25quarterly at the least. Model prices move constantly and the table inside it is already two years old
c14c16 anything about another companyevery six months. A comparison against a two-year-old version of somebody’s product is a false claim even if it was true when it was written
c07, c08 licenceswhenever a repository is added, and when systemcicy gets a licence file
shipping status on every catalogue rowevery time a slice merges. This is the claim most likely to rot into a lie, and it is the one that already did once. See s01
star, fork and contributor countsonly if they are ever published here. They are not
c12, c13, c17, c18 who is herewhenever somebody new commits

Last full pass: 2026-08-14. Owner: Taha Mahmoodi.

If a row here is wrong

Write to {{contact_email}}. The correction goes into this table with the date it was made, next to the sentence it replaces. It does not go quietly into the sentence.