[KongchangAI]
Concept

Event Log

An append-only log system in which each event, once written, cannot be modified. It serves as the only state that needs to be protected in the agent architecture.

Timeline (last 90 days)

Oct 25

The append-only event log allows component state to be rebuilt by replaying the log after a crash, and decouples the context compression strategy from persistent storage.

Unverified50%
Oct 14

It is recommended to maintain an incident log containing five columns (time, customer, what the agent said, actual policy, actions taken and rule changes), with one row per incident.

Unverified50%
Oct 14

The incident log serves a dual function: internally it is a data source for discovering rule gaps; externally, when a dispute enters platform arbitration or payment institution review, it can prove that the merchant has established a reasonable supervision and correction mechanism.

Unverified50%
Sep 23

Process mining is a technique for automatically extracting business process models from event logs, which consist of timestamped activity events, with each complete execution record called a case.

Unverified50%
Sep 18

An event log is the core of the Event Sourcing architectural pattern, where system state is derived from an immutable sequence of events, supporting time-travel debugging and complete auditing.

Unverified50%
Sep 18

When the three data structures are used in combination, the event log typically serves as the source of truth, while the graph and agent state serve as derived read models to balance write cost and query efficiency.

Unverified50%

All Facts (6)

Source Articles