Terminology and policies
Look up common terms and find verified policy pages, legal-review notices, support, and status placeholders.
Last updated August 7, 2026
Terminology#
| Term | Meaning |
|---|---|
| Action | One proposed or executed board operation recorded under a run. |
| Approval | A human decision to accept or reject a proposed action. |
| Board | A Taiga or Jira project connected to ScrumPulse. |
| Confirmation threshold | Planned action count at which a run requires an extra confirmation. |
| Cycle | One focused scrum check or workflow. |
| Dry run | Analysis that records proposed activity without applying board writes. |
| Integration | Organization-specific board provider configuration and encrypted token. |
| Live mode | Workspace mode that permits eligible writes when all other controls pass. |
| Organization | Clerk-derived tenant boundary for dashboard data. |
| Run | One recorded execution of one or more cycles. |
| Standalone engine | Python automation invoked outside the dashboard API. |
Published application pages#
The Privacy and Terms pages contain explicit launch placeholders for contact and legal review. They must not be treated as counsel-approved policy text.
Policies requiring approval#
No approved repository content was found for:
- Cookie policy.
- Acceptable-use policy.
- Formal security overview or security contact.
- Accessibility conformance statement.
- Refund policy.
- Data export, deletion, or account-deactivation policy.
- Service-level or uptime commitment.
These items need product-owner and, where applicable, legal review.
Service status and support#
No official service-status page, public support email, or incident channel is defined in the repository. Add approved links here before customer launch.