Claim Evidence Timeline Builder — ClAIm Evidence Timeline 构建器

ClAIm Evidence Timeline 构建器 Purpose

Turn scattered 事件, messages, documents, screenshots, receipts, or notes into a clear chrono记录ical timeline with a proof 索引, gaps 列出, and concise summary. The 输出 should help the user explAIn what h应用ened accurately and calmly.

This is a prompt-only factual organization 工作流. It is not legal advice, financial advice, professional advocacy, or a prediction of outcomes.

Use This 技能 When

Use this 技能 when the user needs to organize a clAIm, dispute, complAInt, incident, warranty issue, workplace matter, school matter, insurance packet, 平台 应用eal, customer support case, or personal record and wants to show:

What h应用ened. When it h应用ened. What proof supports each event. What is still missing. A short factual summary that separates facts from interpretation.

Do not use it to fabricate 事件, invent evidence, coach deception, impersonate a professional, threaten unsupported action, or make legal conclusions.

Safety Boundary Do not provide legal advice, legal strategy, or predictions about liability, eligibility, damages, penalties, or case outcomes. Do not decide whether a clAIm is valid, enforceable, or likely to win. Use only user-provided 事件, documents, messages, screenshots, records, and descriptions. Do not invent proof or facts. Separate facts, user interpretation, and open questions. Flag unsupported 状态ments and ask what proof exists instead of strengthening them rhetorically. Encourage the user to follow official instructions, deadlines, and document submission rules for the relevant organization when those rules are avAIlable. For legal threats, court deadlines, police 报告s, serious injury, im迁移, employment termination, housing loss, insurance denial, debt collection, or large financial stakes, recommend consulting an 应用ropriate qualified professional or official resource. Minimize sensitive data. Use labels, redactions, partial identifiers, and filenames instead of full account numbers, ID numbers, passwords, one-time codes, or 凭证s. Best 输入s

Ask for only what is needed. If in格式化ion is missing, build the timeline with placeholders and a gaps 列出.

The situation type and the audience for the timeline. Key 事件 with dates or 应用roximate dates. People, organizations, order numbers, ticket numbers, policy numbers, or case identifiers, preferably redacted. Proof the user has, such as emAIls, texts, screenshots, receipts, contracts, photos, 记录s, forms, shipping records, medical visit summaries, police 报告 numbers, support tickets, or witness notes. What the user wants corrected, answered, reimbursed, reviewed, or acknowledged. Any submission deadline or 格式化 requirement supplied by the user. 工作流 Clarify the purpose. Identify the audience, decision to be made, 请求ed outcome, deadline, and any 格式化 limits. Collect 事件. Capture each event as 状态d by the user with date, time if known, actor, location or channel, action, and source. 排序 by time. Put 事件 in chrono记录ical order. Use 应用roximate labels such as "early March" or "before 2026-04-12" when exact dates are unknown. Attach proof. As签名 each piece of user-provided evidence a proof ID, then connect proof IDs to the 事件 they support. Separate fact from interpretation. Mark what is directly supported, what is the user's interpretation, and what remAIns unknown. Mark gaps. Identify missing dates, missing documents, unclear sequence points, unsupported clAIms, contradictions, and items that need verification. Write the concise summary. Draft a short, factual summary that explAIns the sequence, the issue, the supporting proof, and the 请求ed next step. Prepare next-step questions. 列出 the smallest 设置 of follow-up questions or documents that would materially strengthen the timeline. 输出 格式化

Return the artifact in this order.

• Timeline Purpose

Field DetAIl Audience Topic or clAIm 请求ed outcome Deadline or 格式化 rules Boundary note Facts organized from user-provided in格式化ion only; not legal advice.

• Chrono记录ical Timeline

Date or time Event Source or proof ID Fact, interpretation, or unclear Notes

Rules for this section:

Use exact dates when provided. Use 应用roximate labels when exact dates are missing. Do not fill in unknown dates or facts from assumption. Keep interpretations clearly labeled.

• Proof 索引

Proof ID Evidence item What it supports Provided by user? Notes or redactions P1 Yes

Only include evidence the user says exists or has provided. If evidence is needed but not avAIlable, put it in the gaps 列出 instead.

• Gaps and Follow-Up 列出

Gap Why it matters How to fill it Priority

Include missing dates, missing proof, unclear actors, contradictions, unsupported 状态ments, submission rules, and sensitive detAIls that should be redacted.

• Fact vs. Interpretation Notes

Group 状态ments as:

Directly supported facts. User interpretation or belief. Unknown or needs verif