Pér
Activity log¶
The Activity log is the record of what Pér has done in your tenant: the recommendations it made, the plan steps that were approved and carried out, and the handful of settings changes that shape how it works.
Pér acts in a production tenant, which makes “what did it do, and on whose say-so” a question somebody eventually asks — usually somebody who was not in the conversation that started it. The Activity log answers this. It is also one of the three things that carry forward into the Learn stage of the customer decision loop, alongside memories and artifacts.
The log belongs to the tenant rather than to you. Everyone who can reach Pér sees the same entries.
What it records¶
The log records work that changed something or retired something, not everything Pér said.
Three kinds of thing reach the Activity log:
Plans and their steps
A plan approved and run, and each step approved and run.
A step that was approved, and a step that was rejected.
A plan reverted before any of its steps ran.
A fresh attempt proposed for a step that failed.
Recommendations
Settings that change how Pér works
An edit to your company context, however it was made.
A memory created, edited, archived or restored.
A change to the word Pér uses for your customers.
Note
Writing an entry is best-effort everywhere except one place: if the log write fails, the work it describes still stands. Reverting a plan is the exception — its entry is written as part of the revert itself, so a plan cannot be abandoned without the log saying so.
Reading an entry¶
Every entry answers three questions: who acted, what happened, and how it turned out.
Who acted. Each entry is marked as Pér acting on its own, Pér acting on an approval somebody gave it, or a person acting directly. The middle mark is the one worth looking for on anything that changed your tenant: it means a person approved the change before it ran.
What happened. A title, and a short account of the work underneath it. A long account is shortened to its first lines, and you can open it.
How it turned out. Most entries carry an outcome — a step that succeeded, a recommendation that was dismissed, a plan that was reverted. Not every entry has one.
Entries are grouped by day, newest first, with today and yesterday named rather than dated and a count beside each day.
What the log does not tell you¶
The log is deliberately narrow, and has three specific edges worth knowing:
It does not always say who. A settings change, a rejected step and a memory change name the person. Everything else records what happened rather than who did it — a step that was approved and run, a recommendation dismissed or kept, a plan reverted, a retry proposed.
A personal memory keeps its title out of it. Maintaining your own memories does not publish them to everyone in the tenant. A memory shared with the tenant is named.
There is nothing to filter or search. It is one list, newest first, and that is all it is.
Important
The Activity log is not a complete audit trail of every change Pér made on your behalf. For a particular change, the conversation it happened in and the plan it belonged to are the fuller record.
Amperity keeps its own, separate activity logs covering everything that happens across the platform. They are a broader record than this one, and they are where to look for work that did not come from Pér.
Opening the Activity log¶
To open the Activity log
Open Settings.
Choose Activity log.
Each entry is marked Agent, Agent (approved) or User — Pér acting on its own, Pér acting on an approval you gave it, and a person acting directly.
If Pér has not done anything in your tenant yet, the page says so rather than showing an empty list.