the shape the off-lane % describes — each cluster ringed in its own colour, numbered, located on the 144-anchor lattice
1bleed · ShortLex B,A3 ▸ A1,B1 · 6 amber blocks
«R3 — Format clarity (board meeting): The slice focused on ensuring velocity beats and speed requirements are met in daily operations. This wandered into R2 — Six needs, reader's perspective, which was out of spec for this commit as the message never promised addressing reader needs.»
2bleed · ShortLex A3,B ▸ B1,A1 · 6 amber blocks
«Tactics Speed as the lens on Operations. Latency is the price of a missed beat.
This slice focused on optimizing operations through speed tactics and highlighted latency issues. However, it wandered into the "Six needs, reader's perspective" category by implicitly addressing user experience and expectations, which was out of spec for this commit.»
3bleed · ShortLex C,B ▸ A1,A1 · 4 amber blocks
«R6 — Research links + contact. This slice focused on adding a connector intent file and clarifying scanner details but wandered into discussing legal mandates and operational governance, which was not promised in the commit message.»
4bleed · ShortLex C,B3 ▸ A1,C3 · 4 amber blocks
«R3 — Format clarity (board meeting): The slice focused on format clarity for board meetings but wandered into compliance governance articles, which mandate binding rules for iterative feedback loops and hypothesis tests. This was out of spec for the commit.»
5bleed · ShortLex A3,A3 ▸ B1,B1 · 4 amber blocks
«R1 — WHY-belief opens on the information hazard. The slice did not set out to address any specific lane but instead highlighted a critical issue about latency impacting parallel processes. This wandered into the R1 category, discussing why certain behaviors are risky.»
6in-lane · ShortLex B,B ▸ B,A1 · 3 green blocks
«Tactics determine the timing and beat required to run the daily operations cadence and execution loop.
The slice focused on operational tactics, staying within the declared category of "Tactics determine the timing and beat required to run the daily operations cadence and execution loop."»
7bleed · ShortLex A3,C2 ▸ B1,C3 · 3 amber blocks
«Rapid tempo beats determine the flow throughput and how fast work crosses the finish line. Latency is the price of a missed beat.
This slice wandered into "Rapid tempo beats" but the commit message never promised it would address this category. The work touched on performance metrics, which was not part of the original stated-ask.»
8bleed · ShortLex C3,C ▸ C3,A1 · 2 amber blocks
«R3 — Format clarity (board meeting): The slice focused on legal mandates but did not align with the format clarity expected for board meetings. This included details about flow rate and delivery throughput under binding legal rules.»
9bleed · ShortLex C3,A3 ▸ C3,B1 · 2 amber blocks
«Continuous pipeline flow throughput and delivery rate were measured by the speed and tempo of the beat. This slice wandered into "Format clarity (board meeting)"—the commit did not promise to address format clarity but instead focused on metrics.»
10in-lane · ShortLex B,B2 · 1 green block
«R3 — Format clarity (board meeting): The slice focused on specific tactical maneuvers and their timing, which aligns with format clarity for board meetings. However, this content wandered into R1 — WHY-belief opens on the information hazard, discussing the rationale behind these maneuvers in detail, which was not promised by the commit message.»
11in-lane · ShortLex B,C1 · 1 green block
«Leverage in tactics determines the timing of power flow through the infrastructure grid and route topology.
This slice did not have any stated-ask text related to "Leverage in tactics" or its effects. The work touched this category without the commit message ever mentioning it.»
12in-lane · ShortLex A1,B · 1 green block
«R1 — WHY-belief opens on the information hazard. This slice did not set out to address any stated-ask related to governance rules or legal permissibility; instead, it wandered into discussing the broader implications of information hazards, which is outside the spec's intended lane.»
13in-lane · ShortLex A1,C3 · 1 green block
«R1 — WHY-belief opens on the information hazard. This slice addressed compliance mandates and EU AI Act Article 14 requirements but did not mention human-on-the-loop oversight explicitly in the commit message. The work touched on a category that was out of spec for this commit.»
14in-lane · ShortLex B2,B · 1 green block
«R3 — Format clarity (board meeting): The slice focused on exchange rates and deal terms, which is relevant to format clarity for board meetings. However, this content was not explicitly promised in the commit message.»