| # | Phase | Cycle | Trigger | Action | Rationale | Priority | Copy |
|---|---|---|---|---|---|---|---|
| {{ step.id }} | {{ step.phase }} | {{ step.cycle === null ? '—' : step.cycle }} | {{ step.trigger }} | {{ step.action }} | {{ step.rationale }} | {{ step.priority }} |
| Priority | Action | Why now | Checkpoint | Phase | Copy |
|---|---|---|---|---|---|
| {{ row.priority }} | {{ row.action }} | {{ row.reason }} | {{ row.checkpoint }} | {{ row.phase }} | |
| No adherence guidance available. | |||||
Stimulus Control Steps Planner helps you work faster by turning raw inputs into a clear result package.
In practice, it turns constraints into an actionable plan so you can make decisions without rebuilding the logic by hand each time.
Use it when you need repeatable output from the same logic, whether you are doing a quick check, preparing a report, or comparing multiple scenarios side by side.
Typical workflow: enter the minimum required fields, run once for a baseline, then adjust one assumption at a time to see how the output changes.
This output is informational and does not replace professional evaluation, diagnosis, or treatment.
Start with a plain baseline run before exploring advanced controls. That gives you an anchor result and makes later changes easier to interpret.
In day-to-day use, most people cycle through three moves: set core inputs, compare outcomes, and export a clean snapshot for records or collaboration. The goal is not just getting a number, but understanding what changed and why.
The processing path is deterministic for the same inputs: values are normalized, validated, and then transformed into recommended steps, checkpoints, and rationale. Invalid entries are constrained or flagged before result rendering.
The workflow runs locally in your browser for normal calculations and formatting.
Inputs and results stay in the browser session unless you choose to copy or download exports.
| Field | Type | Role |
|---|---|---|
| Main sleep pattern | Input | Used in computation or validation |
| Awake-in-bed threshold | Input | Used in computation or validation |
| Fixed wake time | Input | Used in computation or validation |
| Calm fallback activity | Input | Used in computation or validation |
| Clock-view policy | Input | Used in computation or validation |
| Intensity profile | Input | Used in computation or validation |
| # | Output | Shown in the results panel |
| Phase | Output | Shown in the results panel |
| Cycle | Output | Shown in the results panel |
| Trigger | Output | Shown in the results panel |
| Action | Output | Shown in the results panel |
| Rationale | Output | Shown in the results panel |
Detected export paths include CSV, JSON, DOCX outputs. Chart tabs are included for visual comparison.
Use this sequence for predictable runs and cleaner comparisons.
After one complete pass, keep the same baseline and change only one variable per rerun.
Read the top summary first, then open detailed rows to confirm how each input contributed to the final output.
When values sit near thresholds, small input edits can flip interpretation labels. Treat boundary results as prompts for a second run rather than final answers.
Inputs and results stay in the browser session unless you choose to copy or download exports. The workflow runs locally in your browser for normal calculations and formatting.
Accuracy depends on input quality and model assumptions. Treat the output as decision support, not guaranteed truth.
Input handling follows the on-page fields, and outputs are presented as recommended steps, checkpoints, and rationale.
Yes for core use, because no mandatory remote API call was detected for the main workflow.
No paywall controls are declared in this package. Review site-wide terms for broader usage policy.
Repeat the run with one changed assumption at a time, then compare outputs before making a decision.