Learn
Policies and instructions
Choose admission and processing behavior without mixing their responsibilities.
v0.1.0-dev.2Intermediateusecase_forge
Open source reference ↗Policies and instructions
UseCase Forge separates input instructions from processing instructions. Input instructions decide whether and when intent enters. Processing instructions decide how admitted executions coexist.
Input instructions
| Instruction | Responsibility |
|---|---|
| Debounce | Delay admission until rapid input settles. |
| Throttle | Restrict how frequently input advances. |
| Rate limit | Limit accepted executions inside a time window. |
| Conflict policy | Decide what happens when related intent is already waiting for admission. |
Processing instructions
| Policy | Responsibility |
|---|---|
concurrent | Allow related executions to overlap. |
sequential | Run related executions one at a time. |
coexist | Keep the existing execution and admit another under the defined grouping rules. |
restart | Request cancellation of existing related work and start the new execution. |
rejectNew | Preserve existing work and reject the new execution. |
Resolution hierarchy
Instructions are resolved from explicit command-registration overrides, UseCase-level configuration, and documented defaults. Configuration is captured for an entry; changing later configuration must not retroactively alter already admitted work.