Key concepts
Learn the terms used throughout ScrumPulse, including runs, cycles, actions, dry-run mode, and organization boundaries.
Organization#
An organization is the application’s tenant boundary. The API derives an organization identifier from the verified Clerk session and filters organization-owned records by that identifier.
Clerk provides organization identity and the administrator boundary. ScrumPulse enforces the Admin, Manager, Scrum Master, Product Manager, and read-only Ordinary Member roles at the API. See Roles and permissions before granting or delegating access.
Board integration#
A board integration stores the provider type, base URL, project key, slug, or ID, selected cycles, thresholds, and an encrypted API token. The current dashboard supports Taiga and Jira in its setup and settings screens.
Run#
A run is one execution record. A run can be planned, blocked, executing, completed, or failed. It records the selected cycles, whether it was a dry run, action counts, summaries, and errors.
Cycle#
A cycle is a focused board check or scrum workflow. For example, Cycle A checks hygiene and sprint pulse, while Cycle D prepares blocker and stand-up information. A run can execute one or several cycles.
Action#
An action is a proposed or executed board operation associated with a run. Action logs can record before and after state, approval state, the API result, and whether the action was pending, executed, failed, skipped, or reverted.
Dry-run and live mode#
- Dry run inspects data and records what ScrumPulse would do. It is the default and the only workspace mode available on the Free plan.
- Live mode allows eligible writes when all other safeguards pass. Enabling live mode does not bypass action approvals, confirmation thresholds, or engine-level write gates.
Approval and confirmation#
An approval accepts or rejects a proposed action. A confirmation is an additional run-level guard used when a run crosses the configured confirmation threshold. These controls are related but not interchangeable.
Project scope#
The SaaS integration record identifies a project. The standalone engine can also operate in multi-project mode, but multi-project writes require an explicit allowlist or an explicit allow-all switch.