Noah: Opening this because a ministerial letter with this content should not go eight days without comment. The Bavarian State Ministry for Housing, Building and Transport reported on 25 August 2026: “On 45 lines of Bavaria’s regional rail network no regular timetable is currently possible.” In the same text, Minister Bernreiter names the figure the money argument turns on: “We pay more than 900 million euros a year in track access charges for regional rail in Bavaria, making us the largest funder of DB’s upkeep, and DB wants even more track charges from us, retroactively and going forward.” (Bavarian State Ministry for Housing, Building and Transport, press release, stmb.bayern.de, 25 August 2026, accessed 31 August 2026.) Question for this thread: what should Volt Bavaria actually demand, and from whom, when the state itself has no law that obliges DB to do anything?
Elif: Figures for context, same press release: the number of speed-restricted sections in the state has risen from 100 to around 120 over the last half year. At the same time, 2026 is when DB’s general overhaul programme starts on two Bavarian corridors of all places, Nuremberg-Regensburg and Obertraubling-Passau (DB InfraGO, korridorsanierung-bayern.deutschebahn.com, accessed 31 August 2026). Bernreiter makes exactly this contrast in the press release: “Renovating high-performance corridors matters, but that does not mean regional service can be neglected this badly.” DB names seven such corridors in Bavaria in total, for the remaining five I found no verified start year, leaving that open.
Konstantin: Short interjection on competence, because it decides the direction here. Ordering the regional service is a state task, in Bavaria carried out by the Bayerische Eisenbahngesellschaft (BEG). The rail network itself belongs to DB InfraGO, a federally owned company, Art. 87e of the Basic Law. A Volksbegehren or a state law changes none of that, we have no lever that forces DB to carry out repairs. What is left is political pressure, the ordering process and public attention. Unlike the wind thread, there is no state-law norm here that we could change, which should keep the demand modest from the start.
Miriam: Moderation. Competence is mixed, that is now in the Level 0 note. I am still leaving the thread in Initiation, because the group should first settle what to demand (a timeline for the master plan, compensation for commuters, disclosure of maintenance data) before we open sub-threads in Formulation. Deadline 14 days as the process provides, so 9 September. Anyone with a demand posts it separately, that keeps it sortable.
Stufe-0-Prüfnotiz (automated)
Automatic check per the Volt Bayern policy-discussion process, section 5. A note, never a block: nothing here stops discussion, only the move to Voting needs the Level 1 review.
1. Level of competence (state law?)
Unclear — no matching topic in the routing map, needs a human look before Formulation
2. Volt position (portfolio match)
No known position yet.
The provided excerpts focus on Volt’s structural goals, such as becoming a federal political party, EU institutional reform, and democratic principles like subsidiarity and transparency. None of the texts contain specific policy demands or positions regarding the German railway system (DB) or infrastructure investment. Therefore, there is no basis to classify the thread’s demands as an addition, change, or contradiction to existing Volt policy.
In short: Volt does not state any specific position on railway infrastructure or demands for DB in the provided excerpts.
No matching source found in the checked portfolio.
3. Budget check
To review. Art. 73 Bavarian Constitution (BV) excludes the state budget (Staatshaushalt) from referendums (Volksbegehren); how far that exclusion reaches is unsettled (see Radentscheid Bayern and Mietenstopp precedents, where the issue was competence, not budget). This bot does not assess budget impact, that needs the Level 1 review before a Formulation thread moves to Voting.
Generated 2026-09-01T19:46:40.423Z by plenum-bruecke. Retrieval is deterministic (full-text search over the portfolio); the classification in part 2 used a language model (Qwen/Qwen3.6-35B-A3B-FP8) restricted to the excerpts shown to it. Report an error by replying in this thread.
Kopf
Maintained by plenum-bruecke, updated 2026-09-01T19:46:40.728Z.
| Field | Value |
|---|---|
| Phase | Initiation (1 of 5) |
| Type | Sammel-Thread (no deadline, open until it wanders into the archive) |
| Deadline | none (Sammel-Thread, see section 5a) |
| Level result (Stufe 0) | unclear |
Roles
- Treibt (opens, branches, closes, writes the record): gero
Subject tracks (Fachbausteine) sit on this thread’s decision thread once it branches into one, not on a collection thread.
Phase changes here always mean: tag changed + this post updated, together, by the same call (tools/phase-setzen.mjs or the leitstand). The level-0 review below is a note, not a lock — see the Stufe-0-Prüfnotiz post in this thread for the full check.