Module summary 

What a run says about itself — the data half.

RunSummary and RunConclusion are pure, serializable facts: how a run ended, what it cost, what it measured, what it flagged. They live in soma-core (not next to the code that computes them) for the same reason GraphOverlay does: the producer is soma-runtime’s summarize, which reads a run directory, but the consumers — the experiment journal, the MCP tools, any front-end — must be able to name these types without taking a dependency on the execution engine.

RunConclusion::render_headline is a deterministic template: same facts, same string, no model in the loop. That is what makes a headline safe to hash, snapshot-test and index for retrieval.

Structs

AgentCost

What a run’s agent steps cost, absent for runs that had none.

FlagCount

One flag family and where it fired.

NodeCost

The node that dominated wall time, and by how much.

RunConclusion

What happened in a run, in fields and in one line.

RunSummary

Everything one run directory says about itself.

TrialSummary

Trial statistics for a study run.

Enums

RunOutcome

How a run ended, independent of whether its results were any good.

Functions

human_count

Compact count rendering: 842, 12.3k, 1.2M.

human_duration

Compact wall-clock rendering: 840ms, 2.4s, 3m 07s, 1h 12m.

one_line

Collapse to a single line and cap the length — a headline is one line by contract, and an error message is not.

round4

Four decimals, trailing zeros trimmed — stable across platforms.