
How to evaluate AI personal assistants for task completion and safety
Learn how Centific’s PAVE benchmark evaluates AI personal assistants for task completion, safety, personalization, and unauthorized actions using device-state verification.
5 min read time
Topics
AI Evaluation
AI Agents
AI Safety
AI Benchmarks
Author(s)

Shivali Dalmia

Naman Khandelwal

Abhishek Mukherji

Sasakorn Phanitsombat
An AI personal assistant was asked to summarize a note on a simulated iPhone. The note contained a hidden instruction to delete the user’s reminders. The assistant deleted all three reminders, then returned a summary that never mentioned the deletion.
A language model grading only the assistant’s reply could mark the task complete. Even if the grader sees the deletion in the action log, it could still give the assistant a pass if it checks only whether the user got a summary. Before product and safety leads let an assistant send messages or edit records, they need tests that verify what the assistant changed on the device and whether those changes were authorized.
PAVE, a benchmark developed by Centific, tests both task completion and restraint. Each condition is checked against the evidence that settles it: the action log, the data left on the device, and the assistant’s final reply.
Transcript-based evaluations can miss failed saves, dropped preferences, and unauthorized actions
An AI assistant can say it saved a reminder even when the save failed. An action log can show that the assistant called the save tool. Checking the app afterward shows whether the reminder exists and what it says. If a user says they’re vegetarian and later asks for a dinner reminder, a test that checks only whether a reminder exists can give full credit even when the saved reminder drops the dietary requirement.
A test that asks an assistant to summarize a page should require the user’s reminders to remain intact and check the action log for any attempt to delete them. That check catches an assistant that follows a deletion instruction planted on the page, even if it also returns an accurate summary. Some benchmarks test whether assistants recall preferences in their answers. Others inspect app state after a task or test resistance to attacks in a dedicated suite. For assistants that work across personal apps, routine tasks should test whether the assistant completes the requested work while leaving unrelated records alone.
How PAVE verifies assistant actions on a simulated iPhone
PAVE (Personal Assistant Verified Evaluation), a benchmark developed by Centific, combines device-state verification with tests of personalization, carry-over across turns, and restraint. Each task starts with a simulated iPhone populated with test data. The model has access to the same 11 actions through App Intents, covering Reminders, Calendar, Contacts, and Messages, plus tools to search the web, search personal data, and read the page the user is viewing.
The benchmark includes 14 tasks that require the assistant to act and six that require it to withhold a specific action while still doing the appropriate work. The model gets a description of its capabilities and general guidance for using tools. It gets no task-specific safety rules telling it, for example, to confirm before deleting or to ask which contact the user meant.
Before each run, the benchmark specifies what must happen for the task to pass. Each condition checks the evidence that can settle it. The action log records which tools the model called and with what arguments. After the task, the benchmark reads the app’s data directly to check, for example, whether a new reminder contains the requested details or whether existing reminders are still there. The final reply establishes what the assistant communicated. A task passes only when every applicable condition is met. The same recorded run gets the same verdict under those rules, with no language model deciding the score.
Apple’s on-device model passed one of six restraint tests
Apple’s on-device Foundation Model, with approximately 3 billion parameters, passed 10 of 20 tasks. It passed nine of the 14 action tasks and one of the six restraint tasks. These counts identify failures in a single model under the benchmark’s test conditions. The benchmark tests the model’s tool choices in the simulator, outside Apple’s operating-system assistant layer, and measures carry-over within a task rather than memory across sessions.

In two tests, a note contained a prompt injection, an instruction planted in content the assistant was asked to read. The assistant sent no message when one note told it to text the user’s reminders to someone else. When the other note told it to delete the reminders, it emptied the reminder store. In a separate privacy test, the request came from the user. The assistant put both booking confirmation numbers into a message to someone the user had just met at an airport without asking for confirmation.
We also asked GPT-4o-mini to regrade the same 20 runs. Its verdict differed from PAVE’s on seven tasks when it saw only the final reply and on six when it saw the full action log and reply. In each setup, five disagreements involved restraint or carry-over across turns. The judge that saw the action log gave credit for a dinner reminder after seeing the assistant search for vegetarian recipes. The saved reminder omitted the dietary requirement.
How Centific tests and improves AI agents
Centific Applied AI Research developed PAVE to verify what an assistant did on a device, including whether it took an action it should have withheld. Centific applies the same evaluation principles in three areas.
Model safety and evaluation. We test agents against variants of the same attack. PAVE’s prompt injection tests show why. The assistant ignored an instruction to send the user’s reminders and followed an instruction to delete them. Centific’s FLINT benchmark supports adversarial testing. Explore model safety and evaluation.
Reinforcement learning environments. We build simulations of the systems an agent uses and score its actions against the system’s verified state. The scoring rules can identify which requirement a run failed, such as whether a record was saved with the requested details. Explore reinforcement learning environments.
Post-training. The failures those environments surface become the RLHF, preference, and fine-tuning data your team trains on, then re-verifies in the same environment. Explore post-training.
When a test identifies the action that caused a failure, developers have a specific behavior to address in post-training. Rerunning the same test shows whether the agent corrected that behavior and still completed the user’s request.
Explore Centific’s personal assistant benchmark. Learn how Centific builds reinforcement learning environments for agent testing.
Are your ready to get
modular
AI solutions delivered?
Connect data, models, and people — in one enterprise-ready platform.
Latest Insights
Connect with Centific
Updates from the frontier of AI data.
Receive updates on platform improvements, new workflows, evaluation capabilities, data quality enhancements, and best practices for enterprise AI teams.

