Integrate anticipation and surprise into adaptive continuity

[raelovejoy]

Summary

Integrates the operational rule:

Anticipate what you can. Design for what you can’t.

as a derivative of existing adaptive-continuity, resilience, and corrigibility work rather than a new Root Sequence theory.

Changes

• makes the rule explicit in the systems-level Adaptation model
• adds an Anticipation and surprise section with guardrails against prediction-as-authority and over-anticipation
• adds the move to the Root Sequence Design Grammar and epistemic loop
• connects it to Dynamic Coherence without creating a separate named concept
• routes the idea through the Adaptive Continuity Idea Trail, including scoped translations for Being Human(e), Coherent Computing, and Coherent World

Guardrails

• anticipation is a prompt for preparedness, not authority
• foreseeable effects should be examined before action, while unknowns still require observability, recovery, and revision
• surprise is treated as evidence that can update the model
• over-anticipation, premature abstraction, and brittle optimization around one imagined future are explicit failure modes
• project-local adoption, implementation, and canon remain local to those projects

No merge performed.