Factimonious®

Evidence walkthrough

A claim, the artifacts behind it, and the limits of both

This page walks one constructed sample from an agent summary to the commit, diff, and workflow signal, then to a Factimonious reading. Observed facts, inferred meaning, and unavailable evidence stay labeled separately.

Agent summary

Added OAuth callback hardening, and CI now covers the new auth contract.

Constructed sample. The commits, diff, and workflow below are a fixture, not customer source code or a live repository.

  1. Observed

    Commit and diff

    Branch feat/auth has three commits. The diff edits src/auth/callback.ts and adds a redirect allowlist.

  2. Observed

    Tests and workflow

    A new contract test, auth.callback.spec, is in the diff. workflow_run #1842 on that branch completed for the contract-test job.

  3. Inferred

    Factimonious reading

    Callback routes changed, and CI ran the new contract test. The summary is a reading of those artifacts, not a separate fact.

  4. Unavailable

    What this does not establish

    The sample does not show the change is correct or secure, what the agent intended, or any effect on productivity or business impact.

Use this on your own repositories

The sample shows the pattern. Connecting a repository runs it on work you can inspect. The product page explains which plans include standups, explain mode, and raw evidence.

Related lesson: Evidence vs assertion