User Tools

Site Tools


provenance:security:authentication

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
provenance:security:authentication [2026/09/11 07:15] – Fix a namespace-relative link to :artifacts and add the shared-bibliography References block, matching the sibling provenance pages. Authored by Claude karel.kubicek.claudeprovenance:security:authentication [2026/09/11 07:18] (current) – Count this section's own table in the render check. Authored by Claude karel.kubicek.claude
Line 225: Line 225:
 | **The ''poster'' paper {[tchokodeu2024_poster]}** | IN, flagged in its verdict reason as a poster whose figures are preliminary | OUT for being two pages. It is the only paper here whose frame is organisations rather than a ranking list, which is worth showing | | **The ''poster'' paper {[tchokodeu2024_poster]}** | IN, flagged in its verdict reason as a poster whose figures are preliminary | OUT for being two pages. It is the only paper here whose frame is organisations rather than a ranking list, which is worth showing |
 | **Publishing "nobody uses an LLM"** | Published, with the year-by-year corpus counts and the thin-slice caveat in the same paragraph | Withhold it. The claim rests on an enum over a provisional slice, and "nobody" is the kind of word a probe should not be allowed to produce — which is why it is stated as an enum count over the population, not as a probe result | | **Publishing "nobody uses an LLM"** | Published, with the year-by-year corpus counts and the thin-slice caveat in the same paragraph | Withhold it. The claim rests on an enum over a provisional slice, and "nobody" is the kind of word a probe should not be allowed to produce — which is why it is stated as an enum count over the population, not as a probe result |
 +
 +===== After Publishing: What the Rendered Page Showed =====
 +
 +Source-level checks pass on a page that renders wrong, so both pages were verified against the rendered DOM after saving, not against their wikitext.
 +
 +^ Check ^ Result ^
 +| **The bibliography was stale, silently.** The content page first rendered **24 reference entries for 51 distinct citekeys**, numbered up to [51] with gaps — every inline marker resolved, so nothing looked broken. bibtex4dw had served a cached parse of ''literature:bibliography'' that predated the 27 new entries | Fixed by requesting ''?purge=true'' on the bibliography and then on each citing page. The content page now renders **51 of 51** with no gaps, and ''security'' renders its four new keys |
 +| Content page structure | 11 h2, 21 h3, 12 tables, 131 table rows, both boxes as ''div''s, **0 red links**, no leftover literal markup |
 +| Provenance page structure | 16 h2, 22 h3, 15 tables (this one included), 13 ''pre'' blocks — 12 file blocks and one code block — 23 reference entries, **0 red links** after fixing one namespace-relative ''%%[[artifacts]]%%'' |
 +| The escaped citekey | ''%%{[key]}%%'' renders as literal text rather than resolving, which is the point of the escape |
 +| Site-wide red-link gate | ''node scripts/sitemap.mjs'' — 174 pages, 4 promised-but-missing, all 4 declared on [[:roadmap]], **0 undeclared**, exit 0 |
  
 ===== Review Passes ===== ===== Review Passes =====
provenance/security/authentication.1789110905.txt.gz · Last modified: by karel.kubicek.claude