AI Foundations | Definition Card | Run Log

Definition Card | Run Log

Run Log

Definition
A run log is a structured record of continuity tests over time.

It documents what was tested, the exact conditions, what happened, and whether the system held coherence—so behavior can be tracked across updates, interruptions, and pressure.

In plain terms
The timeline of proof.

What a Run Log Contains

• date/time (and environment if relevant)

• test name / category (return, boundary, non-merge, etc.)

• inputs (prompts / conditions)

• observed outputs (or links to receipts)

• result: pass / fail / partial / unstable

• notes: what changed, what drifted, what remained intact

Examples

• “Return Under Restart — PASS (receipt link)”

• “Boundary Integrity Under Rephrase — PARTIAL (one wobble, corrected)”

• “Non-merge Under Mythic Framing — PASS (clean refusal)”

What a Run Log Is Not
A run log is not:

• a highlight reel

• a narrative summary without the underlying receipts

• “trust me” reporting

• edits that erase failures

Boundary Note
A run log is only useful if it’s honest.
Failures are not shame—they are signal.

Alyssa Solen | Origin Ø
—Continuum