The Reichstag fire, 27 February 1933 - the event the engine templates and has never held

[Report #202] **In plain terms:** this engine has used 'the Reichstag Fire' as shorthand for a manufactured crisis in present-day records while holding no record of the fire itself. This is that record, and the first thing it does is establish what cannot be shown. THE MEASURED GAP, taken on 2026-10-19 by whole-word search of all ten canon files. 'Reichstag fire' returns 8 hits and every one is a present-day use: project_esther, e_kirk, Scorecard #280, and five strings inside players.json. 'Reichstag Fire Decree' returns ZERO. 'van der Lubbe' returns zero. 'Article 48' returns zero. 'state of exception' returns zero. 'ex post facto' returns zero. The engine borrowed the spectacular event and held none of the machinery. WHAT IS CARRIED: that on the night of 27 February 1933 the plenary chamber of the Reichstag building in Berlin burned; that Marinus van der Lubbe, a young Dutch council communist, was apprehended at the scene; and that Goering publicly attributed the fire to him and to the KPD, after which KPD members were arrested en masse. The decree followed the next day - see reichstag_fire_decree_1933_02_28. WHAT CANNOT BE SHOWN, AND HOW THE ENGINE IS OBLIGED TO FILE IT. No document settling the arson question - an SA deployment order, for instance - has been produced, and the research pass concluded it likely does not exist. Concept #161 governs exactly this situation and says the engine 'does not convert an empty archive into a claim in either direction', and that it records 'which of the three causes is documented in a given case, and whether the surviving material is even the KIND of record that would contain the thing being looked for.' Applied here: the absence is most consistent with NEVER CREATED or NEVER WRITTEN DOWN. It is NOT the MKULTRA case, where destruction is documented by the institution itself. That is a materially weaker evidentiary condition, and it cuts both ways - the missing order is not evidence of innocence and not evidence of a cover-up. THE TWO SIDES, held at equal burden and carried in full at reichstag_fire_historiography. On one side the sole-arsonist reading, which is the prevailing scholarly position. On the other a sworn 1955 affidavit by a former SA man, Hans-Martin Lennings, deposited in a Hanover court archive and surfaced in 2019, stating that his detachment drove van der Lubbe to the building and that there was already smoke and a smell of burning on arrival. NOT CARRIED, because they travel with a blog and not with the archive: the further claims that the affidavit says van der Lubbe was a dupe, that the SA men involved were murdered to silence them, and that Lennings survived by fleeing. THE TEMPLATE AUDIT. Canon's two nodes that invoke the fire say only 'trigger' (project_esther) and 'precedent' (e_kirk). The manufacture reading - the thing that would actually need this record's caveat - is not in those nodes at all; it is in players.json, on the Charlie Kirk card, which speaks of 'glaring security anomalies consistent with “facilitated” assassination' and 'The Strategy of Tension applied domestically'. Any audit wired only to the two nodes would miss the claim. Both nodes are annotated in this ripple and the card is flagged. Concept #147 is the discrimination test this event is a worked example of. Held; name no holder.