Factimonious®

Product

Questions the repository can help you answer

Factimonious turns repository activity into standups, retros, and organization views. Each answer stays attached to the commits, diffs, tests, and workflows it used. A reading is not the same thing as the artifact it cites.

Product

See Factimonious in action

Daily standup summary with yesterday, today, blockers, and evidence tabs

Evidence-grounded standups

Capabilities

One question, one evidence trail

Evidence-grounded standups

What changed?

Inputs
Commits, diffs, and pull requests from a connected repository.
Output
A short standup of what landed in the period you asked about.
Evidence trail
Cited commits and pull requests. On Free, the standup is a summary. Raw evidence views start on Pro.
Plans
Free and above. Free includes the summary; Pro adds raw evidence.
Use case
A developer checks yesterday’s agent work before describing it to the team.

Open the sample walkthrough · Reviewing AI-Generated Code

Retros

What meaningful activity occurred?

Inputs
Repository activity across the retrospective window: commits, pull requests, tests, and workflows.
Output
A retrospective of activity that showed up in the repository, compressed without dropping the citations.
Evidence trail
The same artifacts the standup cites, grouped over a longer window.
Plans
Pro and above.
Use case
A tech lead prepares a weekly retro from what merged, instead of from memory or PR blurbs.

Open the sample walkthrough · Code Churn

Explain mode

Why did Factimonious reach this conclusion?

Inputs
The narrative Factimonious produced and the repository artifacts attached to it.
Output
A trace from the conclusion back to the cited evidence.
Evidence trail
Raw evidence and detailed output you can inspect beside the reading. The reading stays labeled as interpretation.
Plans
Pro and above.
Use case
A reviewer asks why a summary mentioned auth changes and opens the cited diff instead of trusting the sentence.

Open the sample walkthrough · Evidence Chains

Trends and organization views

What matters across repositories?

Inputs
Analysis runs across the repositories and history window your plan includes.
Output
Trends, comparisons, and rollups of activity you can trace back to those runs.
Evidence trail
Aggregates built from the same run history. They do not add facts the underlying repositories did not contain.
Plans
Ultra and above for trends and rollups. Teams adds collaboration across seats. Enterprise adds configurable governance and retention.
Use case
An engineering manager looks across repositories for where activity concentrated, then opens a run to see the evidence.

Open the sample walkthrough · Deployment Frequency

Limits

Observable facts are not the interpretation

Repository evidence can show what changed in the artifacts you connected. It cannot, by itself, prove intent, correctness, productivity, or business impact.

  • Observed

    Commits, diffs, tests, workflow results, and other artifacts the connected repository actually contains.

  • Inferred

    Standups, retros, and explain-mode readings. They compress activity and should stay traceable to the artifacts.

  • Unavailable

    Correctness, security, author intent, and business impact unless some other evidence establishes them.

Start with one repository

Free includes evidence-grounded standups. Compare plans when you need explain mode, trends, or an organization evaluation.