LibraryLoop: Recheck the legal blocksv4 · Updated Report

Loop: Recheck the legal blocks

Once a month, recheck the EU and German legal blocks in four Source notes against their primary sources, correct what changed, and move their "Last checked" lines to the cycle date. The blocks are EU and German legal context in the note on persuasion psychology; Legal floor, checked against the Official Journal in the note on mentioning AI; the German price display checklist and the statute rows (E1 to E9) of the external evidence register in the note on activation, plan and limit copy; and the BFSG block in the note on content design. They are the blocks in this organization that state statute law with its dates, so they are the parts that go stale on a calendar.

Decided, 27 October 2026: each organization with calendar pages keeps its own monthly recheck Loop instead of a shared rules organization. This Loop is active from that day. Its definition has no outside action: it reads public sources and edits this organization only.

Widened, 30 October 2026 (owner): the Loop also covers the activation note's German price display checklist and its statute register, and the content design note's BFSG block. Same trigger, no outside action.

Definition, version 1 (active since 27 October 2026)

PartHere
OutcomeEach legal block states the law as it stands on the cycle date, with a "Last checked" line no older than one month.
MeasureDays since the oldest "Last checked" date among the legal blocks, measured when the cycle starts; lower is better (about 31 when cycles run on time).
OwnerOddlynew, which maintains this organization. It decides anything that widens the blocks' scope.
TriggerMonthly on the 1st at 09:00 Vienna time, first slot 1 December 2026. Runs when due in a session opened in this organization, without a per-cycle question, and says so in one line. Also when a reader or a research pass reports a change in a law these blocks cite. No scheduler starts a session for it.
EvidenceOfficial texts first: EUR-Lex and the Official Journal, the Commission's AI Act Service Desk, the Council and the European Parliament's legislative train, gesetze-im-internet.de and the Bundesgesetzblatt at recht.bund.de. Legal commentary only to spot a change, then confirmed in an official text. Every source with its read date.
WritebacksThe legal blocks, corrected in place, and their "Last checked" lines; a change that alters a rule elsewhere goes to that owner (Principles, the playbook, Myths); one entry per cycle in the Research log; the cycle record in the occurrence ledger below.
AuthorityEdit the legal blocks and the documents in this organization that cite them. Orientation, not legal advice. This is a public organization: no customer data, no internal names, no private links. A new legal topic needs the owner.
StopThe owner stops or pauses it. Review on 27 April 2027: keep it if a cycle corrected a block or caught a pending change; otherwise consider a quarterly rhythm.

Steps per cycle

  1. Admit the cycle in the occurrence ledger below before any edit.

  2. Read each block and list every dated statement in it: dates of application, pending acts, negotiation status, numbering.

  3. Check each statement against its official source, and look for new acts and amendments since the last check, including the pending items the blocks name.

  4. Correct what changed in place, with the source URL and the date read. A claim's own legal check stays in the product's claims register, not here.

  5. Set each block's "Last checked" line to the cycle date, even when nothing changed; add the line where a block has none yet.

  6. Add one Research log entry with every field the log's status line names.

  7. Close the cycle in the ledger with the measure's value. A cycle in which nothing changed closes as a verified no-op.

Occurrence ledger

No cycle yet. The first slot is 1 December 2026.

Oddlynew Copy and Messaging PrinciplesSign in

Referenced by