JournalEvent

This page is generated from the code and must not be edited by hand.

One structured entry in the development build’s run journal.

The founding brief asked for full activity logging at every stage, so that when part of the pipeline misbehaves nobody has to read the whole pipeline to find out where. This is that, written as structured rows rather than free text, because every question actually asked of such a log is a query: which stage was slow, what happened to this particular file, why did the reuse rate drop between these two runs.

Exhaustive by default in the development build and switchable off for the stable release, where it becomes one module and one table to delete.

Fields

Field	Type	Required	If left out
detail	text	no	"{}"
duration_ns	whole number or null	no	null
elapsed_ns	whole number	yes
entry_id	text or null	no	null
event	text	yes
journal_id	text	yes
occurred_at	text	yes
relative_path	text or null	no	null
run_id	text	yes
schema_version	text	no	"1.23"
sequence	whole number	yes
stage	text	yes
worker	text	no	""