Gemini SparkUndisclosed

Hand 9,000 pages of VA records to Gemini: a veteran locates what to claim and on which page, and gets a decision letter in a month

原帖作者本人(自述为美国陆军退伍军人;Reddit 公开 Atom 源中该帖条目的作者名已不可见,账号疑似注销,正文仍完整可查)Reddit · 2026-04-21

Read original

Saved text / editorial summary

原帖正文(Reddit r/GeminiAI,标题 I used Google Gemini for my claim,原帖 Atom 源显示更新日期 2026-04-21;本轮经 Reddit 公开 Atom feed 取得全文,逐字,未经改写): “I’m an Army Veteran and Gemini helped me with my disability claim. So what I did was went to va.gov and I downloaded my blue button records then I fed the records to Google Gemini and told it to scan over the 9000 pages and tell me what I could file for. It was a game changer for me because the AI was able to tell me exactly what pages certain things were on like what exact dates I went to a chiropractor one year or what types of treatment I had in the exact dates and what pages they were on. So when I filed, I had the exact pages dates to go with my claim because honestly, I’m not gonna be able to go through all 9000 pages and I know for a fact that the VA claims rep isn’t gonna go through all those pages so if you know exactly what Page different things are on and the exact dates it made it so much easier. My claim took a total of one month from when I filed till when I got my decision letter. I helped another Vet get 70% doing the same thing and his took two months. A lot of the older vets that I tried helping didn’t trust the AI (which is totally understandable and I could’ve just fed all of my info to Skynet lol) but I just wanted to let other people know that was one tool I used and it worked.” 中文对照:作者自述是陆军退伍军人,Gemini 帮他处理了伤残索赔。做法是从 va.gov 下载自己的 Blue Button 病历,把记录交给 Gemini,让它扫完 9000 页并告诉自己可以申报什么。对他改变最大的是定位能力——AI 能说出某些事情具体在哪几页,比如某一年去看脊医的确切日期、接受过哪类治疗以及对应的日期和页码。所以他提交时能把精确的页码和日期一并附上,理由很实在:他自己翻不完这 9000 页,也确定理赔专员不会翻完。他的案子从提交到收到决定信总共用了一个月;他用同样办法帮另一位退伍军人拿到了 70%,那位用了两个月。他也提到不少老兵不信任 AI。

Business model

The author of a Reddit post in r/GeminiAI describes himself as an Army veteran and says he used Gemini on his disability claim: he downloaded his Blue Button records from va.gov, fed the full 9,000 pages to Gemini and told it to scan them and say what he could file for. What mattered most was location - Gemini could say which pages things were on, such as the exact dates he saw a chiropractor in a given year, or what treatments he had on which dates and on which pages. He filed with exact page numbers and dates attached, on the reasoning that he cannot get through 9,000 pages and neither will the claims rep. His own claim took one month from filing to decision letter. He says he helped another veteran reach a 70 percent rating the same way, and that one took two months. The 70 percent is another person's rating outcome, not earnings and not the result of this author's own claim. No payout, savings or cost is disclosed.

The value is citability, not conclusion. The author did not let the model decide what to claim; he had it mark which page says what, then decided himself how to use it. Keeping index and judgement apart is what makes this work, and it is also what makes the method reusable in insurance, legal or accounting records rather than only in a claim.

Workflow

  1. Start from the official export of your own records, not from memory.
  2. Phrase the job as find the page, not decide for me.
  3. Split the material into batches; never push the whole set through one window.
  4. Every result must carry a page number and a date, or it is discarded.
  5. Spot-check three to five entries against the original before filing anything.
  6. Keep a separate not-found list so missing and not-located stay distinguishable.
  7. Set the privacy boundary yourself before handing over identity or medical files.

Adaptation plan

The post gives no payout, no cost, no token spend, no tool settings, and does not say how the 9,000 pages were split or how many passes it took. The one month is the author's own case; the two months and the 70 percent belong to another veteran he says he helped. The author also notes that many older veterans did not trust handing their information to AI. The workflow, prompt, synthetic example and pitfalls here are AgentFlow's proposals, untested.

Prompt

AgentFlow draft · Untested.

You are an indexing assistant for a long personal file. Your job is to locate items and give citable references. You do not decide what should be claimed, what should be filed, or how anything should be argued.

[INPUT]
This batch: [file name or page range; one batch at a time]
Item types I am looking for: [list them, for example visit dates / treatment types / test conclusions]
Reference fields every entry must carry: [page or file location / date / one quoted line]
Left to me: deciding what to use, spot-checking, deciding whether to file

[EXECUTION STEPS]
1) Restate this batch's scope (file name and page range) and the item types; begin after that is acknowledged.
2) Scan page by page and record only what appears on that page. For items spanning pages, record the first page and note the continuation.
3) Write one line per result: item / date / page or file location / one quoted line from the source.
4) For ambiguous, incomplete or unreadable pages, add them to an uncertain list with the reason; do not guess characters.
5) At the end of the batch output a not-found list: item types I asked for that do not appear in this batch.
6) After all batches, merge and de-duplicate the index and mark which batch each entry came from.

[OUTPUT]
- Index: one line each, item / date / page or file location / one quoted line.
- Not-found list: item type plus not present in this batch.
- Uncertain list: page plus reason (incomplete / illegible / insufficient context).
- Merged index: de-duplicated, sorted by date, each entry keeping its source batch and page.

[HUMAN CONFIRMATION]
- Any entry without a page or file location is void; never infer a page from meaning.
- Do not decide what I can claim, do not estimate a rating, payout or timeline, do not draft arguments or appeals.
- Do not write not-found as does-not-exist; only say it does not appear in this batch.
- When identity or medical data is involved, output nothing unrelated to the items I asked for.

[FAILURE AND MISSING INPUT]
- If material cannot be parsed, a scan has no text layer, or pages are unnumbered, put it in the uncertain list; do not improvise OCR.
- If a batch exceeds what can be processed, stop and ask me to split it; never skip the middle.
- If an item is not found, say not found; never substitute a date from a similar item.

[SYNTHETIC EXAMPLE - not real data, format only]
Input: batch Example_Records_2021.pdf pages 1-200; item types visit date, treatment type; reference fields page / date / quoted line
Output (index excerpt): Chiropractor visit / 2021-03-14 / p.87 / "chiropractic visit, lumbar"; Physical therapy / 2021-05-02 / p.143 / "physical therapy, 6 sessions"
Output (not found): Imaging conclusion - not present in this batch
Output (uncertain): p.66 - scan illegible, date cannot be confirmed

Running costs and pitfalls

The post gives no payout, no cost, no token spend, no tool settings, and does not say how the 9,000 pages were split or how many passes it took. The one month is the author's own case; the two months and the 70 percent belong to another veteran he says he helped. The author also notes that many older veterans did not trust handing their information to AI. The workflow, prompt, synthetic example and pitfalls here are AgentFlow's proposals, untested. No independent cost benchmark is available. Check subscriptions, permissions and external actions before running a workflow.

Author-reported results are not independently audited.

Original text and media remain attributed to their authors.