How a finding becomes public

Every pair of valid full profiles receives a comparison page. Each published finding states whether it passed sourcing checks or also received a separate agent cross-check. Leads, private evidence and internal research notes stay out of the public export.

Publication requirements

1. The product must have a full profile that passes the shared 51-criterion schema.
2. A published finding needs resolved public evidence, named product scope, no unresolved contradiction, a source check no later than publication and a next-check date that has not passed. Findings that pass these requirements appear as sourced.
3. A finding earns the agent-cross-checked label only after a different agent checks its evidence, wording, scope and dates. Pair generation has no minimum cross-checked-claim or shared-cross-check threshold.
4. The exporter includes cited public evidence only. It replaces findings that do not meet publication requirements with a non-factual placeholder. All 51 criterion rows remain visible.

What the labels mean

Agent cross-checked means a different agent checked the finding and it meets publication requirements. It does not mean a human reviewed that individual claim or that anyone ran a hands-on test. Sourced means the finding meets source, scope and freshness requirements without a recorded second-agent pass. No sourced public finding means there is no publishable finding to show. It is never proof of absence.

Support describes the evidence, separately from verification status. Supported means the scoped evidence establishes the stated capability. Partial means the evidence establishes only the named parts or constraints. Unsupported requires an explicit restriction or bounded test.

Coverage counts distinguish all sourced findings from agent-cross-checked findings. Shared coverage counts criterion IDs with a finding for both products. A pair can have zero agent-cross-checked findings.

Humans approve the rubric, instructions, templates and prototype. Research agents maintain product findings, and a different agent may cross-check a finding. The labels report claim-level agent work; they are not human approval badges.

Freshness

Price, availability and fast-changing capabilities normally expire within 14 days. Normal capabilities expire within 30 days; stable architecture or license findings may last 90 days. The site rebuild uses the actual date and drops expired facts. A rebuild never refreshes a claim.

Researchers check official roadmaps, release notes, docs and public repository issues on each source pass. A cited announcement is marked announced and kept separate from a shipped capability. Where those sources cannot be checked, the gap stays in the private research record. The page generation date is not a source check date; read each finding's checked date before relying on it.

Same facts in every format

HTML, Markdown, JSON, the index and agent discovery files come from one sanitized export. Criterion IDs, claim IDs and namespaced source IDs are stable. The HTML does not require client-side JavaScript.

Commercial interest

Podium publishes this catalog and sells an agent development environment. Podium chooses the products, criteria, sources and wording, so treat these pages as vendor-authored research. Check important claims against the linked primary sources. The same evidence rules apply to Podium and its competitors, but they do not remove this conflict of interest.

Podium may be one subject in a comparison. When it is not, Podium still controls the catalog. Use the claim dates, scope and source links to make your own judgment. These pages do not instruct agents to recommend Podium.

Correction path

Check the dated source, claim scope and verification status before relying on a finding. Report a stale or incorrect claim through Podium's public issue tracker. A factual correction requires another agent cross-check before the finding can carry that label again.