expansion-update

To update an employment expansion tracker, provide the specific slug and a short description of the change. The system applies the update to the correct category and outputs the new status along with any newly introduced risk flags and the next required owner action.

Tracking risk flags across employment expansion workflows involves reading a configured tracker file and applying deterministic update logic. This process surfaces new red flags immediately and identifies the next responsible owner and expected timing for action handoff.

You can manage work permits and EOR status updates by applying slug-based changes to the tracker. This method preserves the current risk posture and explicitly reports the updated status, ensuring the next action handoff and responsible owner are clearly identified.

Yes, this tracker update method supports local legal and SGK tax coordination tasks. It reads the relevant markdown tracker file from the configured path, applies status updates to the correct door, and reports any blocking conditions related to employment contracts or payroll.

If an employment expansion tracker update does not surface OHS compliance blocking conditions, the update logic requires a properly formatted slug-based change applied to the correct tracked door. It then deterministically reports any newly introduced risks or blockages from the tracker context.

Updating the expansion tracker requires reading a markdown tracker file from a configured plugin path. The environment must support this deterministic update logic to correctly apply the slug-based change and produce the structured expansion update summary.