Artifacts

A job's artifacts are what it keeps from one run to the next: its findings, its working tables, its standing answer. They are the job's only memory. Each run is a fresh conversation with the agent, and a harness agent gets a fresh computer each run, so anything the next run should know has to be saved as an artifact.

The agent saves them through its job tools; you read them on the job's Artifacts tab.

Two kinds

Kind Key looks like Behaves
Living document open-placements, summary, sources One page, rewritten by every run. The job's current answer. Pinned at the top of the tab.
Item placements/acme-AM0000000001 One page per thing found. Items accumulate from run to run and are grouped by the part before the slash, with a count.

The prompt decides the keys. A key that never changes for the same thing — an ISIN, a date, a URL slug — is what lets the next run tell new from already known.

On the Artifacts tab

  • Living documents first, then items by group.
  • A filter box matches keys and titles.
  • Show archived (N) brings archived items back into view, marked Archived.

Opening an artifact shows its page at full width, who wrote the revision on screen — which run, linked, or a person — and a revision menu to open any earlier version. Every save by a run is a revision stamped with that run.

Artifacts are also found by the workspace Search, under their own filter, and every artifact has a link: an agent that mentions one in a report or a message posts a link that opens it.

Archive, not delete

When an item is no longer current — an offer whose window closed and that its source no longer lists — the agent archives it with a short reason. An archived item:

  • moves out of sight behind Show archived;
  • is still known to the job: the next run will not record it again as new;
  • comes back if the agent saves it again.

Agents never delete artifacts. Only a person can, all at once.

Starting from scratch

Reset artifacts in a job's menu deletes everything the job has kept, archived items included. The next run starts with no memory of earlier ones. Use it after you change what a job does, to see how the new instructions work from a clean slate.

  • The dialog says how many artifacts will go, and the button works only once you type the job's name.
  • Runs and their reports stay; links in old reports to deleted artifacts stop opening.
  • A job with a run in progress cannot be reset until the run ends.

What a run changed

Each run lists the artifacts it created and updated — in its row ("Artifacts: 1 created · 2 updated") and on its page, with links. A run that changed nothing shows nothing there.