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,C1 · 11 amber blocks
«The slice wandered into operations management, which was outside the specified lane of facilitating smooth exchange rates and deal flow. The commit worked on operational daily run loops without any mention in the message.»
2bleed · ShortLex A1,B ▸ A1,C3 · 10 amber blocks
«The slice wandered into a category that was out of spec for this commit. The work touched EU AI Act Article 14 requirements without the commit message ever mentioning them.»
3bleed · ShortLex A1,A ▸ B2,A2 · 10 amber blocks
«The slice wandered into a category that was out of spec for this commit. The work touched "Finance provides the budget runway and dollar floor that sustains daily operations and the execution loop" without any part of the commit message promising it would do so.»
4in-lane · ShortLex A,C ▸ A,C2 · 9 green blocks
«The slice wandered into the "drift" category. The code implemented a long-horizon strategy frame, which was not part of the commit's declared lane; the message never promised this.»
5drift · ShortLex A3,C ▸ B2,A2 · 9 red blocks
«The slice wandered into a category that was OUT OF SPEC for this commit. The code addressed speed limits within legal constraints, but the sensor detected activity in an area not mentioned in the commit message.»
6drift · ShortLex B3,A1 ▸ C2,A3 · 9 red blocks
«The slice wandered into a category that was OUT OF SPEC for this commit. The work designed path routes and grid topology, which the message never promised.»
7drift · ShortLex C1,B1 ▸ C3,B3 · 9 red blocks
«The slice wandered into the "drift" category. It validated loop iteration and hypothesis test measures, ensuring deal exchange rates delivered expected values. However, the commit never declared this as part of its stated intent.»
8drift · ShortLex A2,B2 ▸ B1,C1 · 9 red blocks
«The slice is categorized as "drift" because the code acted in a lane that was not declared by the commit message. Specifically, the work built out the ceiling (cap on resources) without the commit ever mentioning this aspect.»
9drift · ShortLex B2,C1 ▸ C1,C3 · 9 red blocks
«The slice "Gmail strips data: URIs), git-discipline (hooks-hang escape hatches), pmu-reef" is categorized as bleed. It landed in the category of "Message signal reach and bandwidth," which was not what it set out to do; the commit never declared this lane.»
10drift · ShortLex C1,A ▸ C3,C · 8 red blocks
«The slice wandered into the "drift" category. It acted in a lane the commit never declared—specifically, it engaged in feedback loops and hypothesis test cycles, which were not part of the original stated ask.»
11drift · ShortLex A2,C2 ▸ B1,C3 · 6 red blocks
«The slice wandered into a category that was OUT OF SPEC for this commit. The work acted on "Dollar floor finance," which was not promised by the message.»
12in-lane · ShortLex C,C ▸ C,B1 · 5 green blocks
«The slice set out to verify routing and ensure the lens surfaces correctly. It stayed within the "on-target" lane as declared.»
13bleed · ShortLex B,B ▸ C,A2 · 5 amber blocks
«The slice wandered into "Operations maintain the daily cadence loop required to satisfy the binding mandate and governance rule of law," which was out of spec for this commit (the message never promised it).»
14bleed · ShortLex B,C2 ▸ A1,C3 · 5 amber blocks
«The slice wandered into a category not specified in the commit's stated goals. The code addressed maintaining daily cadence and operational execution, but also touched on flow throughput and delivery rate, which were outside the declared scope.»
15in-lane · ShortLex C,B3 ▸ C,C2 · 3 green blocks
«The slice wandered into the "drift" category. It managed power flow across the infrastructure grid, which was not part of the commit's declared lane.»
16in-lane · ShortLex B,A ▸ C,A · 2 green blocks
«The slice is categorized as "bleed," indicating that it wandered into a lane that was not part of the original declaration. Specifically, it entered the operational daily run cycles and validation processes, which were outside the scope promised by the commit message.»
17drift · ShortLex B3,A ▸ B3,B · 2 red blocks
«The slice wandered into the "drift" category. It acted in a lane that was not declared by the commit message—specifically, it explored aspects of signal reach and bandwidth, which were not part of the original stated intentions.»
18drift · ShortLex C3,A1 · 1 red block
«The slice wandered into a category that was OUT OF SPEC for this commit. The work acted on a governance rule of law without the commit message ever mentioning it.»