Agent Pulse / Methodology

How Agent Pulse Makes One Daily Call

Agent Pulse reports one bounded action, watch, or honest no-change decision from fresh public coding-agent evidence. Movement finds candidates; a direct source inspection earns the headline.

Inputs

The V0.2 snapshot reads project-owned local git caches, commit subjects, recent touched file paths, the Agent Atlas roster, and the published article manifest. A date-owned editorial brief adds the mechanism, reader action, confidence, limitation, and falsifier. The public site receives a JSON snapshot, not the private SQLite cache.

local git commit historycommit subjectsrecent touched file pathspublished article coveragereported direct-source daily insight

Decision Contract

Every edition must publish exactly one disposition: action, watch, or no material change. A project claim needs a fresh direct receipt. Cross-project and field claims need receipts from at least two distinct projects. Commit counts and subject tags can nominate a source, but cannot serve as the primary evidence.

Action
A bounded test, audit, trial, pin, or question that a named reader can perform.
Effort and reversal
Every action states its expected effort and whether it is safely reversible.
Confidence
The brief names what the receipts support, what they do not, and what evidence would change the conclusion.
Coverage gate
A field-wide claim is blocked when any included project or core coding-agent source is unavailable or stale.

Main Metrics

7d commits
Commits whose commit date lands in the seven calendar dates ending on the snapshot date.
Baseline delta
Current seven-day commits minus the project's own thirty-day daily pace multiplied by seven.
Hardening-subject proxy
A weighted proxy from commit subjects: fixes, tests, CI, docs, and releases. It is not a release-quality score.
Capability tags
Subject-line pattern hits for areas such as tools, UX, runtime, memory, permissions, security, and observability.
Article trail
The number of published The Git Reporter articles linked to the project in the public manifest.

Ranking Views

The page separates signal boards so raw activity does not masquerade as overall project quality.

Most active
Ranks by current seven-day commit count.
Most accelerated
Ranks by movement above the project's own thirty-day pace.
Hardening-subject hits
Ranks by the hardening-subject proxy in the thirty-day window.
Most covered
Ranks by The Git Reporter article coverage, not external popularity.

Confidence

Confidence is a reader-facing evidence note. It rises when a repo has recent public motion, recurring article coverage, activity spread across the month, and multiple public commit authors. It does not mean the project is better or safer.

Not Collected Yet

These signals are intentionally absent until the feedback collector exists. They should not be read as zero.

not collected: GitHub issue flownot collected: GitHub PR review timingnot collected: Discord feedbacknot collected: X/Twitter feedbacknot collected: Reddit or Hacker News feedbacknot collected: private maintainer backlog

Receipts

Every project row links recent commits and the latest related coverage. The raw public snapshot is available as JSON.

Open Agent Pulse JSON ›