Skip to Main Content
Integration


This is an IBM Automation portal for Integration products. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).


Shape the future of IBM!

We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:

Search existing ideas

Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,

Post your ideas
  1. Post an idea.

  2. Get feedback from the IBM team and other customers to refine your idea.

  3. Follow the idea through the IBM Ideas process.


Specific links you will want to bookmark for future use

Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.

ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.


Status Submitted
Workspace API Connect
Created by Guest
Created on Nov 2, 2026

Evidence Challenge, Appeal and Correction Propagation API

 

Pre-flight checklist

  • This is an API feature request, not a consumer app or Comet UI request.
  • Check current documentation and forum topics for closely equivalent functionality before posting.
  • The developer workflow or API use case is described below.

Feature type

New endpoint or API capability; New response field or metadata

Affected API area

Agent API; Search API

Summary

Make evidence-record disputes, revisions and downstream correction notices machine-readable.

Problem

A published verification finding may be challenged or corrected after AI systems have already retrieved or cached it. Merely issuing a new webpage is insufficient for traceable downstream updates.

Proposed API behavior

Support challenge submission by eligible parties, acknowledgement, review status, decision reasons, correction versions, supersession and revocation. Offer read-only status endpoints and optional signed event notifications for consumers, with authorization and abuse prevention.

Example usage

A published finding is corrected after fresh institutional evidence. An application requesting the old claim ID receives a superseded status, replacement version and link to the published rationale.

Workarounds tried / considered

Manual errata pages, changed web content and cache expiry provide partial workarounds but do not guarantee a standard appeal lifecycle across consumers.

Impact

Affected individuals, institutions and developers gain clearer remedies, reduced stale citations and auditable correction history.

Additional context

This expands the correction-history principle in my published proposal into a standalone workflow. Design must protect privacy, prevent abusive disputes and avoid revealing confidential appeals.

Proposal attribution: Grace R. Nettey — Manifold Grace. Human-led conceptual research, with AI assistance in structuring and drafting. The request invites consideration; it does not demand implementation.

Related foundation: https://community.perplexity.ai/t/interoperable-institutional-evidence-verification-api-with-provenance-tracking/6457

Idea priority Urgent