Submission boundaries

Submission boundaries explain where RoleWorth stops, asks for review, or hands the task back to you. The product should never make unsupported application action look complete.

The boundary checks four things before any submission-adjacent action can continue:

1. The feature is enabled. 2. Your plan allows the action. 3. You confirmed this specific action. 4. The Application Kit attached to the action is approved.

If any check fails, RoleWorth explains what stopped and what to do next: configure the feature, upgrade the plan, confirm the action, approve the kit, or complete the application manually.

Manual-review hosts include Workday, LinkedIn, iCIMS, SmartRecruiters, login-required boards, captcha-protected flows, and any custom or non-standard form without fixture proof. The product should not pretend it submitted; it should stop, preserve the kit, and hand the application back to you to complete by hand.

What this is not: this is not 'apply to everything overnight'. The boundary exists because final application actions have real downside: wrong applications sent under your name, host policy issues, rate-limiting, and no audit trail. The review-first design keeps the user in control.