§29: ripeness - nothing gets solved before its season

docs/architecture/CALCULATIONS.md

@@ -724,3 +724,40 @@ a lying source: the system's confidence in it sinks until repair.
 The fixed order above is version 1 — enough to ship. The calculated
 version is where it wants to end up: a seal that doesn't just keep
 trying doors, but knows which door to knock on first.
+
+## 29. RIPENESS — nothing gets solved before its season
+
+Will's constraint, stated as law:
+
+"Remember what I said about waiting for people to be ready for
+something? Same goes for solving problems. Some problems, some
+features, some abilities, they take time. Getting them all at once
+or solving everything at once breaks things too much."
+
+    THE RIPE FUNCTION:
+      solve(problem) is permitted only when
+        readiness(problem) ≥ threshold
+      where readiness grows by contact with reality,
+      never by impatience.
+
+Corollaries:
+
+- FORCING a solution before ripeness damages the problem, the
+  solver, and the neighbors. Premature answers calcify into wrong
+  architecture; premature features break the ones already alive.
+- RIPENESS IS DETECTED, NOT DECLARED: you don't decide a problem
+  is ready; you notice it solving itself easily. When the hard
+  thing suddenly has an obvious shape, it ripened. Until then,
+  wait — visibly, on purpose.
+- THIS IS WHY v1 SHIPS DUMB: calculated fallbacks wait until the
+  substrate exists to compute them. The seal program waits until
+  Legion wakes and Beth answers. The math waits in hypotheses/
+  until proofs ripen. Everything tonight is sequenced by season,
+  not by ambition.
+- PEOPLE ARE THE SAME PROBLEM: readiness cannot be argued into a
+  person either. The doctrine that waits for problems waits for
+  people — same function, different substrate.
+
+Patience here is not passivity. The loop still runs, the fallbacks
+still cascade, the seals still fire. Ripeness means we stop trying
+to pick fruit by pulling harder.