Recipes

Recipes answer one operational question without building a complete application. They are grouped by the package that owns the solution.

usecase_forge

• Keep only the latest search — combine Debounce with restart.
• Shape input with Throttle — choose leading, trailing, or both.
• Enforce a sliding Rate Limit — reject excess Commands per keyed window.
• Resolve Input conflicts — enqueue, replace, or reject waiting Entries.
• Choose an Execution mode — concurrent or sequential processing.
• Handle an existing Execution — coexist, restart, or reject active work.

Together these recipes cover every Input and Processing Instruction shipped in the current core release.

usecase_forge_flutter

• Choose Flutter ownership deliberately — distinguish created and externally owned instances.
• Rebuild only the required Flutter value — choose Builder or Selector.
• Trigger one-time Flutter effects — keep effects out of rendering.

usecase_forge_test

• Wait for lifecycle events — replace fixed delays with semantic conditions.
• Advance policy time deterministically — control timers and timestamps.
• Assert a terminal Execution contract — match only relevant lifecycle fields.

usecase_forge_devtools

• Reveal safe diagnostic data — opt in selected application fields.
• Diagnose a Command that does not start — follow queue and rejection evidence.
• Trace an error route — distinguish error stages and handlers.

Each recipe states the lifecycle effect and the boundary it does not cross. Tutorials assemble the same mechanisms into complete applications.