Rebalance system cards: shift from implementation to architectural benefits

saadshahd · saadshahd · commit 5d5dc36fc67c · 2025-10-31T14:45:17.000Z
Changed three-system overview cards from implementation details to
architectural principles, reducing character variance from 19% to 4%
and avoiding repetition with detailed subsections below.

Changes:
- Card 1: "Rules without code deploys..." → "Product managers ship dataspec
  rules without engineering deploys—configuration over code" (97→91 chars)
- Card 2: "UX that makes errors impossible..." → "Prevention over validation—state
  machines make illegal workflows impossible structurally" (117→91 chars)
- Card 3: "Event graphs + claims-based..." → "Temporal dependencies and
  provenance tracking—event graphs resolve causality at scale" (103→87 chars)

Strategic shift:
- Before: Implementation-focused (how it works)
- After: Benefit-focused (what it enables)
- Setup: Better transition to "Why this order matters" paragraph

Result: Balanced visual rhythm (91/91/87 chars), eliminated repetition with
subsections, and elevated to architectural thinking for target audience
(technical recruiters and engineering leaders).
diff --git a/src/pages/portfolio/statsbomb.mdx b/src/pages/portfolio/statsbomb.mdx
@@ -238,7 +238,7 @@ Product managers couldn't define new collection requirements without engineering
         <span class="flex-shrink-0 w-8 h-8 rounded-full bg-skill/10 flex items-center justify-center text-base font-bold text-skill" aria-label="Step 1 of 3">1</span>
         <Heading level={4} as="h4" class="text-base font-semibold">Domain Logic as Configuration</Heading>
       </div>
-      <Body size="sm" as="p" class="text-text-lighter">Rules without code deploys—product managers define dataspec logic in readable DSL syntax</Body>
+      <Body size="sm" as="p" class="text-text-lighter">Product managers ship dataspec rules without engineering deploys—configuration over code</Body>
     </Card>
 
     {/* System 2: Live-Collection-App */}
@@ -247,7 +247,7 @@ Product managers couldn't define new collection requirements without engineering
         <span class="flex-shrink-0 w-8 h-8 rounded-full bg-category/10 flex items-center justify-center text-base font-bold text-category" aria-label="Step 2 of 3">2</span>
         <Heading level={4} as="h4" class="text-base font-semibold">Live-Collection-App</Heading>
       </div>
-      <Body size="sm" as="p" class="text-text-lighter">UX that makes errors impossible—state machines constrain invalid workflows, keyboard flows build muscle memory</Body>
+      <Body size="sm" as="p" class="text-text-lighter">Prevention over validation—state machines make illegal workflows impossible structurally</Body>
     </Card>
 
     {/* System 3: Backend Evolution */}
@@ -256,7 +256,7 @@ Product managers couldn't define new collection requirements without engineering
         <span class="flex-shrink-0 w-8 h-8 rounded-full bg-status/10 flex items-center justify-center text-base font-bold text-status" aria-label="Step 3 of 3">3</span>
         <Heading level={4} as="h4" class="text-base font-semibold">Backend Evolution</Heading>
       </div>
-      <Body size="sm" as="p" class="text-text-lighter">Event graphs + claims-based metadata—temporal dependencies and provenance tracking at scale</Body>
+      <Body size="sm" as="p" class="text-text-lighter">Temporal dependencies and provenance tracking—event graphs resolve causality at scale</Body>
     </Card>
   </div>
 
