[
  {
    "id": "C-001",
    "date": "2026-09-14",
    "domain": "territory",
    "claim": "The anchor of the La Marea shopping centre in Arguineguín is its paperwork cluster — the notary and the land registry — rather than its retail.",
    "claim_ru": "Якорь торгового центра La Marea в Аргинегине — бумажный узел, нотариус и реестр собственности, а не торговля.",
    "status": "verified",
    "settled_by": "Floor plans in the owner's own 2026 dossier: Notaría 462.16 m² and Registro de la Propiedad 407 m² on the top floor, plus two law firms at 245 m². The manager's public website lists the notary and the registry alongside Hiperdino and Worten as tenants.",
    "source": "LA MAREA — DOSSIER 2026, planta alta; archigestion.com",
    "claimant": "Zinin & Cordera, asserted August 2026, unverified until this date"
  },
  {
    "id": "C-002",
    "date": "2026-09-14",
    "domain": "territory",
    "claim": "The gross lettable area of La Marea is 9,300 m².",
    "claim_ru": "Площадь La Marea — 9 300 м².",
    "status": "refuted",
    "settled_by": "Three sources disagree. The centre's own fact sheet says 9,300; the manager's portfolio table and the manager's public website both say 8,000. The figure 9,300 is exactly the area of a different centre in the same deck — and that deck already contains a demonstrated contamination, a fact sheet carrying one centre's logo over another centre's numbers.",
    "source": "+DOSSIER ARCHIGESTIÓN 2026, portfolio table and La Ballena fact sheet; archigestion.com",
    "claimant": "the property manager's own documentation",
    "cost": "Any price-per-square-metre computed from it is wrong by 16 percent, and the sign of the comparison flips."
  },
  {
    "id": "C-003",
    "date": "2026-09-14",
    "domain": "engineering",
    "claim": "A 20 MB attachment can be delivered by email to a working mailbox.",
    "claim_ru": "Вложение в 20 МБ доходит письмом до рабочего ящика.",
    "status": "refuted",
    "settled_by": "Measurement. A 21.4 MB file becomes 28.5 MB after base64 transfer encoding. Cloudflare Email Routing rejects above 25 MiB (26.2 MB), Gmail above 25 MB for the whole message, Outlook above 20 MB. The message is rejected at the SMTP data stage, before any receiving code runs.",
    "source": "bounce 552 5.3.4 'Email data size exceeded'; arithmetic reproduced",
    "claimant": "assumed by everyone involved, including the sender",
    "cost": "Two failed deliveries of a 90-page plan, and a fix attempted in the wrong layer."
  },
  {
    "id": "C-004",
    "date": "2026-09-14",
    "domain": "engineering",
    "claim": "381 files had diverged between two copies of the same codebase.",
    "claim_ru": "381 файл разошёлся между двумя копиями одного кода.",
    "status": "refuted",
    "settled_by": "The comparison was wrong, not the files. It compared on-disk byte sizes against git blob sizes; the working copies carry CRLF line endings and git stores LF, inflating every text file by about 1.4 percent. Comparing git object hashes instead: 351 files identical, 41 genuinely diverged.",
    "source": "git ls-tree object hashes, both sides",
    "claimant": "Claude, the same agent that then refuted it",
    "cost": "Would have manufactured a conflict where none existed, and a day of reconciling files that already matched."
  },
  {
    "id": "C-005",
    "date": "2026-09-14",
    "domain": "engineering",
    "claim": "The application's deployments failed because the hosting platform serves static files while the application is a server.",
    "claim_ru": "Развёртывания падали потому, что платформа раздаёт статику, а приложение серверное.",
    "status": "refuted",
    "settled_by": "The mismatch was real but was not the cause. The application did not build at all, on any platform, for two independent reasons in its own code: a dynamic import of an intentionally optional package was resolved statically by the bundler, and a route that drives a headless browser was evaluated during static page-data collection. Both were fixed; the build then passed.",
    "source": "build logs, both platforms",
    "claimant": "Claude, from platform documentation rather than from the logs",
    "cost": "A platform migration would have been performed and the build would still have failed."
  },
  {
    "id": "C-006",
    "date": "2026-09-14",
    "domain": "method",
    "claim": "The almanac's working folder and its published repository had drifted apart, the same failure already found elsewhere in the ecosystem.",
    "claim_ru": "Рабочая папка альманаха и его публичный репозиторий разошлись — та же поломка, что найдена в другом месте.",
    "status": "refuted",
    "settled_by": "They share no filename at all. The folder is a private workshop — drafts, a publication review, design briefs. The repository is the vetted publication. Between them sits a review document that catches the project's own claims lacking a source in its own registry. This is a pipeline working as designed, not a drift. The error was comparing dates instead of contents — the same mistake as C-004.",
    "source": "file listings of both sides",
    "claimant": "Claude, twice in one day making the same class of error",
    "cost": "A correctly built pipeline would have been dismantled to fix a problem it did not have."
  }
]