the shape the off-lane % describes — each cluster ringed in its own colour, numbered, located on the 144-anchor lattice
1drift · ShortLex A,A1 ▸ C,A3 · 9 red blocks
«The work published 191e4212b did not match the commit's declared lane. The commit stated "chore(commit-page): publish," but the work expanded into tactical leverage, which was not part of the original ask.»
2drift · ShortLex A1,A2 ▸ A3,B1 · 9 red blocks
«The work positioned targets for the quarterly goal, which was not part of the commit to publish 191e4212b. This wandered into the "Position targets for the quarterly goal" lane without being declared.»
3drift · ShortLex A3,B2 ▸ B2,C1 · 9 red blocks
«The work published 191e4212b without any stated ask text, while the commit declared "chore(commit-page): publish 191e4212b". This slice wandered into the "Measured velocity beats determine how fast the message signal can reach the intended broadcast channel bandwidth" lane, which was not specified in the commit.»
4drift · ShortLex A,C1 ▸ C,C3 · 9 red blocks
«The work published 191e4212b did not match the commit's declared lane. The commit stated "chore(commit-page): publish," but the work ventured into tactics by providing a maneuver choice and timing for testing a hypothesis, which was outside the specified chore scope.»
5drift · ShortLex A2,A ▸ B1,C · 9 red blocks
«The work published 191e4212b, which was supposed to fund the dollar floor for expensive tactics. Instead, it wandered into capital budgets that support high-leverage maneuver choices.»
6drift · ShortLex C1,A ▸ C3,C · 9 red blocks
«The work published 191e44212, which was not part of the commit's declared ask. This wandered into the "Feedback loops and hypothesis test cycles" lane, though the commit only intended to stay in the "chore(commit-page)" lane.»
7drift · ShortLex A1,C1 ▸ A3,C3 · 8 red blocks
«The work published 191e44212 did not match the commit's declared lane. The commit stated "chore(commit-page): publish," but the change instead wandered into defining quarterly goal targets, which is out of spec for a commit-page update.»
8drift · ShortLex B3,A1 ▸ C2,A3 · 8 red blocks
«The work published 191e4212b focused on path routes and grid topology design, which is part of "Path routes and grid topology are designed to facilitate the quarterly goal and target position. Power flows where the grid lets it." However, this commit never declared any changes in these areas; it was meant to be a chore related to publishing code.»
9drift · ShortLex B2,A ▸ B3,C · 5 red blocks
«The work published 191e4212b without any stated-ask text in the commit message. This slice wandered into the "Reach of a signal and the message bandwidth provide the channel for tactical maneuver choices" lane, which was not specified by the commit.»
10drift · ShortLex C2,A3 ▸ C3,B2 · 4 red blocks
«The work published 191e44212 without an accompanying commit message, which was supposed to be a chore related to publishing. This slice wandered into the Continuous pipeline flow throughput and delivery rate lane, but this was out of spec for the named category.»
11bleed · ShortLex A,A ▸ B,B · 3 amber blocks
«The slice published 191e4212b without an accompanying message, wandering into "Tactics" territory when the commit was explicitly about "chore(commit-page)." This work did not match the declared lane.»
12in-lane · ShortLex A,A · 1 green block
«The lattice we build today is what next year's underwriter inherits. This commit aimed to publish a specific code change (191e4212b), and that’s precisely what it did.»
13drift · ShortLex B1,C3 · 1 red block
«The work published 191e4212b did not match the commit's declared lane; instead of staying within the "chore(commit-page)" category, it wandered into the "Rapid tempo beats determine the flow throughput and how fast work crosses the finish line" lane. This was out of spec for this commit.»
14drift · ShortLex B2,A2 · 1 red block
«The slice adjusted negotiation rates to meet the quarterly goal and target position, which is part of "Negotiation rates for a deal are adjusted to meet the quarterly goal and target position." However, this work also involved updating the system's cell coordinate, a task not mentioned in the commit message "chore(commit-page): publish 191e4212b."»