ReasoningAsserted

ReasoningAsserted is the standard tier-one assert event for automated pre-bind material at the commitment boundary. It freezes what informed an automated bind — inputs, runner, output summary, policy — before the commit event references it by event id. Facts stay in the event log; there is no external evidence blob.

Shape (schemaVersion: 1)

captureForce: assert — forward without bind. The following commit supplies accountability.

Commit pairing

Every automated commit references the assert:

reasoningAssertRef: { eventId: "ReasoningAsserted:evt-…" }

Long agent runs may emit a chain of ReasoningAsserted events; the commit references the terminal assert.

Human path

Human review uses a different assert — HumanReviewAsserted (reviewerId, reviewDurationSeconds, materialShown, conclusion). Human-in-the-loop commits may reference both reasoningAssertRef and humanReviewAssertRef.

Infrastructure

Assert events may publish to a separate topic or stream from domain commits (reasoning-assertions vs domain topics) for retention, access control, or volume — without leaving the event model. Join by event id.

Failure modes

Skipping ReasoningAsserted and inlining scores on the commit recreates inference-as-fact. Storing assert payloads outside tier one as blobs breaks the four capture modes discipline.