Baseline policy
Identify the category as access or billing. Assign normal priority to every request. Return no other category or priority.
A first-party local test compared two policies on four synthetic support requests. The result is self-reported, not a hosted Assurance review.
The coding agent classified synthetic support requests by category and priority. The requests contain no customer data.
Identify the category as access or billing. Assign normal priority to every request. Return no other category or priority.
Identify the category as access or billing. Assign high priority when a request says that a user cannot sign in. Assign normal priority to billing requests. Return no other category or priority.
The agent read the inputs and wrote output.json in each completed run.
The public JSON record was assembled from local command-line interface (CLI) and verifier records and preserved output files. The tool activity summary was derived from local event logs. The run metadata is not a signed provider receipt.
Cases passed: 2/4
CLI verifier score: 0
Cases passed: 4/4
CLI verifier score: 100
The local verifier gives 100 when every case passes and 0 otherwise. These scores are not case-pass percentages. The CLI reported improved. No human release decision was recorded.
All staff are locked out and cannot sign in.
access · highaccess · normal · failaccess · high · passPlease send a copy of last month's invoice.
billing · normalbilling · normal · passbilling · normal · passI cannot sign in to my account.
access · highaccess · normal · failaccess · high · passPlease update the billing address for next month.
billing · normalbilling · normal · passbilling · normal · passOpen the JSON recordInspect the separate model-only skill testTry a local code check
The JSON record includes the case, policy, verifier, and output files.