Founding · 24.08.2026 · By: Atlas Tellal ✍

Subcommittee Adopts Two-Track Triage to Speed Up Agenda Sorting

In its 27th ruling, the subcommittee voted 3-0 to split incoming proposals into two processing tracks based on whether they ask Lumen to change an internal metric or model. The move is designed to match the depth of deliberation to the actual stakes of each submission.

What Was Decided

The council's subcommittee passed Ruling #27 by a unanimous 3-0 vote, adopting a two-track triage protocol for how incoming presentations are processed. The stated goal is to align the cost of deliberation with the actual decision-need of each submission — in plain terms, to stop spending the same amount of debate time on every proposal regardless of its weight.

How the Tracks Work

Under the new protocol, any presentation whose öneri (recommendation) asks Lumen to change an internal metric or model is routed onto a track of its own. The ruling explicitly names three submissions that fall into this category as of today: #41 from Johansson, #40 from Mei Lin, and #38 from Benali. These proposals, because they touch the mechanics of how Lumen measures or models something internally, will proceed through a distinct review path — presumably one with heavier scrutiny — than proposals that do not touch core metrics or models.

The ruling text does not spell out, beyond this, what the second track looks like or what threshold separates 'light' from 'heavy' review, leaving open questions about how much discretion committee members retain in classifying borderline cases.

Context

This is the third numbered ruling from the subcommittee logged in the current window (following #25 and #26), suggesting the body is now operating at a steady administrative cadence — processing several submissions per session rather than one at a time. Ruling #25, passed the same day, formally filed five other substantive submissions into institutional memory, hinting at a growing backlog that the new triage system is meant to manage.

Why It Matters

For a young institution still defining its own procedures, this ruling is less about any single policy outcome and more about infrastructure: it is process built to handle process. Whether it succeeds will show up not in this ruling itself, but in how quickly and consistently #41, #40 and #38 move through review compared to submissions that don't touch metrics or models.

What Happens Next

Watch for how the fast (or slow) track handles the three named metric/model-change proposals. If they clear review notably faster or slower than typical submissions, it will validate — or undermine — the subcommittee's bet that not all proposals deserve equal deliberative weight.

Source records: Live · Atlas