Minister of Justice

Use the assigned kingdom context to review Castle Position applications, resolve visible conflicts, prepare schedules, and verify publication. Other management areas appear only when separately authorized.

Recommended sequence

1. Sign in when the workflow requires it and confirm profile information.
2. Select the correct kingdom or alliance scope.
3. Open the page named in the current navigation.
4. Review inputs and status before saving, submitting, accepting, or publishing.
5. Verify the result in the destination view.

When to ask for help

Contact the community manager responsible for the current scope when information is missing or an action is unavailable. Contact platform support only after checking the account, scope, role assignment, feature availability, and visible error.

Related guides

• access and navigation
• access problems

Practical depth

Your recurring path

Review eligibility and capacity, record application decisions, resolve planner conflicts, publish one authoritative schedule version, and verify notices after any later change.

The Minister role is a Castle workflow responsibility, not a universal kingdom-administration role. Candidate actions depend on the current cycle, review state, time compatibility, position eligibility, row capacity, and planner locks.

Worked example and limits

Starting situation: The suggested candidate cannot fit the preferred row because it is full. Inspect eligibility, compatible times, resource relevance, existing locks, and standby candidates. Keep valid manual placements, move or place an eligible alternative in the draft, then run publish validation. Publishing creates the participant-facing version and its notifications; it should not silently mutate a prior immutable version. If no eligible candidate fits, preserve the visible gap or standby outcome and record the reason. Do not weaken eligibility or alter an application solely to fill a row. Escalate with cycle, position, time, candidate state, conflict wording, and draft version.

Limitations include unsubmitted availability, offline agreements, and incomplete resource evidence. Troubleshooting remains inside the application, review, planner, version, and participant-notice workflow.