da63980a · zzmq.dev@gmail.com/zz
Commit
da63980a470347e8b3724b4ba861c6c746b7cba0
Reframe Cascade as a scale phenomenon, not a Lane type A cascade is ordinary work decomposition fanning out to many dependents at once (the SSL-vulnerability case), using the same ASK-driven mechanism as any other related Lane. Dropped the dependency_cascade trigger kind entirely; trigger stays manual with a descriptive reason. Added a new "Cascade policy" section sketching what a Maintainer would need to control at that scale (concurrency, priority, a separate budget line) as an open, not-yet-designed area, with a matching tentative cascade: block in the policy.yaml example. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Troy Howard <thoward37@gmail.com> -- 2026-10-07T10:31:40.000Z