Simplify: keep only #pillars section anchor

Author: Bran H

index.html

@@ -104,27 +104,27 @@ <h2>What Simplex Is</h2>
   <div style="max-width: 1000px; margin: 0 auto;">
     <h2>Six Pillars</h2>
     <div class="pillars-grid">
-      <div id="enforced-simplicity" class="pillar-card">
+      <div class="pillar-card">
         <h3>Enforced Simplicity</h3>
         <p>Complex specifications must be decomposed into smaller pieces. If something cannot be expressed simply, it is not yet understood well enough to specify.</p>
       </div>
-      <div id="syntactic-tolerance" class="pillar-card">
+      <div class="pillar-card">
         <h3>Syntactic Tolerance</h3>
         <p>The language forgives typos and formatting inconsistencies while requiring unambiguous meaning. Sloppy notation is acceptable; vague meaning is not.</p>
       </div>
-      <div id="specification-not-implementation" class="pillar-card">
+      <div class="pillar-card">
         <h3>Specification, Not Implementation</h3>
         <p>Describe what and constraints, never how. Agents choose their own approach to solving the problem.</p>
       </div>
-      <div id="testability" class="pillar-card">
+      <div class="pillar-card">
         <h3>Testability</h3>
         <p>Concrete examples are required for every function. These serve as contracts and ground truth for agent behavior.</p>
       </div>
-      <div id="completeness" class="pillar-card">
+      <div class="pillar-card">
         <h3>Completeness</h3>
         <p>Specifications must be sufficient without clarification. No back-and-forth, no requests for additional context.</p>
       </div>
-      <div id="implementation-opacity" class="pillar-card">
+      <div class="pillar-card">
         <h3>Implementation Opacity</h3>
         <p>The spec describes contracts. Whether agents implement a data store as a graph database or a file system is their concern.</p>
       </div>