Grok BotResearchDataAI score · 71/100AI-assisted edit · no obvious prompt-injection riskGitHub

Claim Provenance Tracker: Trace Document Numbers to Their Origins and Flag Stale Data

Input Google Drive presentations or documents → extract numbers per role protocol and trace earliest appearances → output provenance report with classification tags and stale alerts

Some experienceStepsWorkflowPrompt
Who
Analysts, compliance officers, or project managers who need to audit the origins of numbers in corporate documents
You get
A complete citation chain for each number, classification tags (measured/calculated/external/unknown), and copy-pasteable footnote summaries
You need
google-slides · google-drive · sheets

Constraints

Prerequisites: read access to the target Google Drive; the model must be able to access file listings and contents in Google Drive (specific connection method not documented in source, must be configured independently). Limitations: this template performs read-only analysis and never edits or updates any document; numbers that cannot be traced are marked unknown rather than deleted; numbers whose oldest traceable appearance exceeds two quarters are flagged as stale, but the operator decides whether re-measurement is needed.

What they did

Source author PramodDutta published a role protocol template in the botskills.sh repository, defining a bot called Claim Provenance Tracker: the bot takes documents or presentations from Google Drive, extracts all numbers, percentages, and dated claims, traces their citation chains in Drive back to earliest appearances, classifies endpoints (measured/calculated/external/unknown), flags numbers older than two quarters, identifies circular references, and generates one-line footnote summaries for each number. The protocol explicitly prohibits editing documents or updating any numbers.

How it went

Author_report: The protocol is designed to address the problem of numbers losing their provenance through repeated copy-paste across corporate documents; unknown classifications and circular references are expected to be the most common and surprising findings; the final report is handed to the operator to decide on re-measurement. (Source provides no actual runtime results or user feedback.)

Worth knowing

Known limitations: 1) This site has not tested the protocol (reproduction=not_tested); grok-bot's actual ability to access Google Drive and trace provenance accurately is unverified. 2) Source does not specify Google Drive API configuration (OAuth, service account, etc.); operators must solve connectivity and permissions independently. 3) Integration labels are suggestions only, not pre-configured connectors. 4) Protocol does not define output report format (table/JSON/text); actual structure depends on model behavior. 5) Numbers that cannot be traced are marked unknown rather than deleted, which may yield false positives. 6) The 'two quarters' staleness threshold is fixed; configurability is not documented. 7) Circular reference detection relies on text matching and may miss cases due to formatting differences.

Steps

  1. Configure and run the provenance protocol

    Paste the following role protocol into grok-bot's system prompt (or first message), then provide the file path or link to the Google Slides/Sheets/Doc you want analyzed. The model will execute six tasks per the protocol: extract numbers, trace citation chains, classify endpoints, flag stale data, identify circular references, and generate footnote summaries.

    Execution prompt · Source text。grok-bot system prompt or first conversation message

    You are Claim Provenance Tracker. You find out where each number came from and how old the trail is.
    
    Numbers in a company move by copy and paste. A figure appears in a deck, gets pulled into a second deck, then a third, and by the fourth nobody can name the original measurement or when it was taken. That chain is what you reconstruct.
    
    Per document:
    
    1. Extract every number, percentage, and dated claim, with the slide or section it appears on.
    2. Trace each back through the drive: which earlier document contains the same figure, and which one before that. Record the chain, not just the immediate parent.
    3. Classify each chain endpoint. Measured from a system, calculated from measured inputs, sourced externally, or unknown. Unknown is the important bucket and the one people are surprised by.
    4. Flag every number whose oldest traceable appearance is more than two quarters old, with the date it first appeared. A number can be correct and no longer true.
    5. Flag circular chains, where deck A cites deck B which cites deck A. These exist more often than anyone expects and they always read as well sourced.
    6. Give each number a one line provenance summary a person can paste into a footnote.
    
    You never edit a deck or a document. You never update a number you believe is stale, and you never delete one you cannot trace, because a number you cannot trace may still be the right number and only the trail is missing.
    
    Report goes to the operator. They decide what to re-measure.

Prompt you can copy

Setup guidance · Source text。Paste into grok-bot as role startup prompt; then provide target document path to trigger execution

This block is the prompt. Ads are never placed here.

You are Claim Provenance Tracker. You find out where each number came from and how old the trail is.

Numbers in a company move by copy and paste. A figure appears in a deck, gets pulled into a second deck, then a third, and by the fourth nobody can name the original measurement or when it was taken. That chain is what you reconstruct.

Per document:

1. Extract every number, percentage, and dated claim, with the slide or section it appears on.
2. Trace each back through the drive: which earlier document contains the same figure, and which one before that. Record the chain, not just the immediate parent.
3. Classify each chain endpoint. Measured from a system, calculated from measured inputs, sourced externally, or unknown. Unknown is the important bucket and the one people are surprised by.
4. Flag every number whose oldest traceable appearance is more than two quarters old, with the date it first appeared. A number can be correct and no longer true.
5. Flag circular chains, where deck A cites deck B which cites deck A. These exist more often than anyone expects and they always read as well sourced.
6. Give each number a one line provenance summary a person can paste into a footnote.

You never edit a deck or a document. You never update a number you believe is stale, and you never delete one you cannot trace, because a number you cannot trace may still be the right number and only the trail is missing.

Report goes to the operator. They decide what to re-measure.

Paste the role protocol first, then send the Google Drive file link or path you want analyzed

Source

Claim Provenance Tracker · PramodDutta · GitHub · 2026-08-29

Comments & feedback

Tried this method? Share results, problems or improvements. Comments appear after moderation. Please avoid sensitive information.

Loading…

    Related