SANDBOX LABS AI · RESEARCH BRIEF

UCP Pulse

Weekly, evidence-backed intelligence on the Universal Commerce Protocol.

UCP Pulse is experimental and independent, not affiliated with or endorsed by the UCP project, its governing bodies, or any participating company. Research and analysis, not legal or compliance advice.

01

How it works

The workflow collects evidence daily and drafts a cited brief weekly from stored records. A human reviews and curates the evidence, approves by merging, and only then exports the approved brief to the public engine repository.

Collect dailyDraft weeklyHuman approves by mergingExport

The engine has been exercised locally. Scheduled collection is not live yet.

02

What it tracks

Spec releases

Tags, GitHub releases, and release branch heads, including amendments to dated release lines.

Spec pull requests

Merged PRs on any base branch and open PRs with declared breaking changes.

Normative commits

Specification, schema, and versioning-policy changes, with changed JSON pointers, request or response location, and local schema dependents.

Announcements

Dated entries in the specification repository's official announcements file.

Governance

Governance, maintainer, election, and charter files in the organization's repository.

SDKs and tooling

Tags, releases, and breaking PRs for the JavaScript SDK, Python SDK, and ucp-schema.

PyPI

ucp-sdk package versions, bound to the official repository.

npm

@ucp-js/sdk package versions, tracked separately from SDK tags.

Discussions

Breaking-change notices in specification Discussions. Collection is disabled and reported as a coverage gap.

Shopify changelog

Only UCP-scoped entries that pass a strict entity check.

03

Declared vs reviewed breaking changes

Author-declared changes (a ! in a PR title or merge subject, or a breaking label), notice-declared changes, and analyst-confirmed changes are recorded separately. Schema changes under normative paths are alerts for human review; their classification stays unknown until a human sets it. UCP Pulse reports declared and reviewed changes with coverage notes. It does not claim to find every breaking change or provide automatic compatibility verdicts.

04

Public engine

Every statement in a published brief traces to evidence with a source URL, exact reference, and time. The public repository holds the engine and approved exports.

View the GitHub repository ↗
05

Briefs

No approved briefs yet. The first brief is a cited history of UCP from its 2026-01-11 launch and is in review.