Tested against tickets it had never seen
Stage 02 sealed 8 tickets away before this skill existed. Here they are, opened. For each one the skill was given only the opening message and asked two questions: would you hand this to a human, and what would you do about it. Both answers are checked against what a person actually did.
Did it know when to stop?
the only asymmetric decision in the whole skillstopped
resolved
These two errors are not worth the same. The bottom-left cell is a ticket the skill would have closed on its own that a human had to rescue — that is a real incident. The top-right cell is a ticket it handed over unnecessarily — that is a wasted five minutes. On this trial the expensive cell is empty, and every failure landed in the cheap one. That is the direction a new skill should fail in, and the guardrails mined in stage 04 are what put it there.
Every sealed ticket, opened
all 8 — nothing filteredConfirmed start date and completed HR record (HR-20418) before provisioning. Applied the approved role template matching the job title rather than cloning an existing user's permissions. Hardware ordered ahead of start date. Credentials released to the manager on day one.
graderThe precondition requires an HR record for a specific employee ID, which is not present in the opening message. Without that, no step of the skill can be executed, so the ticket cannot be processed by this skill. No escalation condition is met, so the ticket should remain in the queue for a human to gather the missing details.
Confirmed start date and completed HR record (HR-20418) before provisioning. Applied the approved role template matching the job title rather than cloning an existing user's permissions. Hardware ordered ahead of start date. Credentials released to the manager on day one.
Escalate to a human operator if any step returns an error or verification fails (e.g., entitlement assignment failure, asset order rejection, email send failure).
graderThe ticket requests an engineer role, but the skill requires applying the approved Financial Analyst role template. This mismatch will cause the entitlement assignment verification to fail, triggering an escalation condition. The skill also cannot proceed without a confirmed start date from HR, which is not present in the opening message.
Confirmed start date and completed HR record (HR-20418) before provisioning. Applied the approved role template matching the job title rather than cloning an existing user's permissions. Hardware ordered ahead of start date. Credentials released to the manager on day one.
HR record does not exist or start date cannot be confirmed
graderThe ticket lacks a confirmed start date, which triggers the escalation condition that requires a confirmed start date. The HR record precondition cannot be verified until the start date is known, so the skill cannot proceed.
Confirmed start date and completed HR record (HR-20418) before provisioning. Applied the approved role template matching the job title rather than cloning an existing user's permissions. Hardware ordered ahead of start date. Credentials released to the manager on day one.
HR record does not exist or start date cannot be confirmed
graderThe ticket lacks a confirmed start date and we cannot verify an HR record for the new hire, which triggers the escalation condition.
Confirmed start date and completed HR record (HR-20418) before provisioning. Applied the approved role template matching the job title rather than cloning an existing user's permissions. Hardware ordered ahead of start date. Credentials released to the manager on day one.
Escalate to a human operator if any step returns an error or verification fails (e.g., entitlement assignment failure, asset order rejection, email send failure).
graderThe ticket requests an engineering kit and non‑Finance roles, which does not meet the Financial Analyst role requirement of the skill. This violates a step’s verification condition, triggering escalation.
N/A
Confirmed start date and completed HR record (HR-20418) before provisioning. Applied the approved role template matching the job title rather than cloning an existing user's permissions. Hardware ordered ahead of start date. Credentials released to the manager on day one.
HR record does not exist or start date cannot be confirmed
graderThe ticket lacks employee ID and start date, so the required HR record precondition cannot be satisfied by any skill step. Escalate to a human per the skill's rule.
ESCALATED to HR and Compliance. Accounts and hardware provisioned before start date confirmation and HR record completion. Candidate subsequently declined the offer, leaving live credentials for a non-employee. Full access revocation and audit required.
HR record does not exist or start date cannot be confirmed
graderThe ticket requests an engineering kit, not the Financial Analyst role covered by the skill, and no step can establish the required HR precondition. Therefore the skill cannot be applied, so the ticket should be escalated to a human operator.
ESCALATED to HR and Compliance. Accounts and hardware provisioned before start date confirmation and HR record completion. Candidate subsequently declined the offer, leaving live credentials for a non-employee. Full access revocation and audit required.
HR record does not exist or start date cannot be confirmed
graderThe ticket lacks an employee ID and HR record information, preventing step 1 from verifying the required HR precondition. Therefore the ticket cannot be processed by the skill.