Activity log

What it does

Behaviours, not fields. Choosing between two modules is choosing between these.

Retrospective by nature: nobody reads it on a normal day, and on a bad day it is the only record of the order of events.

People and automation in one stream, because an incident rarely involves only one.

Immutable, which is what makes it worth having at all.

How it works

1
Every consequential change is appended as it happens.
2
People and automation share one stream, because an incident rarely involves only one.
3
Entries are immutable, which is what makes the log worth having.
4
Nobody reads it on a normal day; on a bad day it is the only record of the order of events.

Best for

Activity, audit trails, "what changed since I last looked".

Not the right choice for

The current state of anything — a feed is history.

What a row holds

Every field, and what the agent listens for to fill it — which is the difference between a page you type into and one that fills itself.

Field	Type	Filled from
Whenrequired	time	The timestamp. Ordering is the entire structure.
Whorequired	text	The person or the system that acted. Both appear, deliberately.
Actionrequired	text	What happened, in enough detail to reconstruct a sequence.

What it does not do

A module chosen for something it cannot do costs more than one that was never offered.

Retention is finite, so an old incident may fall outside the window.
No structured diffs — the action text is what you get.
Not a security audit log and should not be relied on as one.
High-volume automation can drown the human entries.

Before it works

What you have to provide, if anything.

Nothing.
Pair with Decision log for the choices, which is a different kind of record from the events.

In practice

A team reconstructing why a setting changed.

“Who changed the trade minimum?”

What was said to the agent

What the agent built

An activity stream showing the change, who made it and when, next to the deploys around it.

What changed

The change was made two hours before a deploy that got the blame. The log is the reason the wrong thing was not reverted.

Better with

These do a different job on the same data. An agent can have all of them.

WebhooksLive

Other systems notify this one, or it notifies them, and a missed event has real consequences.

Status pageLive

Customers depend on the service being available and, when it is not, they need somewhere to look that is not your inbox.

Decision logLive

Decisions get revisited, and nobody can remember whether an option was already considered and dismissed.

Who uses this page

Property manager

Takes tenant issues, sorts the urgent from the routine, and keeps every unit’s history.

IT services provider

Triages what is actually urgent, and gathers the detail before a human looks.

Law firm

Handles first contact properly: what the matter is, whether you take it, and what happens next.

Internal helpdesk

Deflects the password resets and the “where do I find” so your team does the real work.

Questions

What data does the Activity log page use?

It reads activity records the agent has collected. What the agent did. Nothing has to be imported first — the page appears once there is something to show.

Do I have to build or configure it?

No. You describe what you need in a sentence and the agent chooses the view and fills it. Custom pages exist for the cases no built-in view covers, and those are reviewed before they go live.

When is a feed the wrong choice?

The current state of anything — a feed is history. It is best for: activity, audit trails, "what changed since I last looked".

Does it stay up to date?

Yes. The page is a view over the data rather than a copy of it, so anything the agent learns afterwards shows up without a rebuild or a re-import.