Final Claim Polishing Checklist

Main goal

Go through every claim note and make sure each one is actually ready for public use, debate prep, and source based reference.

This checklist is for turning the Analytical Research & Sources Archive from a personal Obsidian vault into a polished, shareable, source first resource.

The long term goal is not just to store claims. The goal is to make the archive useful as a product for pro Israel and Jewish advocacy spaces, including organizations such as StandWithUs, CAMERA, HonestReporting, Israel on Campus Coalition, Shurat HaDin, Hasbara Fellowships, campus groups, student advocates, researchers, and related organizations.

This does not mean the archive should become propaganda. It means the archive must be clean enough, careful enough, sourced enough, and legally safe enough that serious people could review it, test it, and maybe use parts of it for education, debate preparation, media response, student advocacy, or source retrieval.

Honest assessment

The archive has real potential because it solves a real problem.

Most people in debate know a few talking points, but they cannot quickly pull:

1. the exact claim
2. the status of the claim
3. the key counterpoints
4. the evidence
5. the primary sources
6. the strongest opposing argument
7. the best debate framing
8. the related claims
9. the exact quote or page number

That is the value of the archive.

But the archive should not be presented as finished or institutional grade until the weak links are fixed. If an organization opens it and finds fake page numbers, weak sources, sloppy wording, overclaims, broken links, or accusations that are not carefully framed, it will look amateur.

The archive has to become boringly reliable.

How to frame the archive

Do not present it as:

The ultimate pro Israel archive

That sounds immature and invites people to attack it.

Frame it as:

A structured secondary research archive for Israel related debate preparation, claim analysis, and source retrieval.

Or:

A claim by claim research index designed to help students, advocates, and researchers quickly locate counterarguments, primary sources, strongest opposing arguments, and source context on common Israel, Jewish, Zionism, antisemitism, terrorism, international law, and media narrative claims.

The archive should be described as a research aid, not a replacement for experts.

Secondary research and source curation

This archive is not original academic research in the sense of discovering new evidence, conducting fieldwork, or publishing peer reviewed scholarship.

It is still legitimate research work if done properly.

The actual value is:

1. source curation
2. claim mapping
3. quote extraction
4. source ranking
5. counterargument synthesis
6. primary source retrieval
7. evidence organization
8. Obsidian linking
9. debate usability
10. fast retrieval under pressure

Call it:

secondary research and source curation

or:

a structured source retrieval and claim analysis archive

Do not undersell it as “not research.” It is research support, source synthesis, and debate infrastructure.

Repo Root Pack reminder

Before any serious public release, update the Repo Root Pack.

Add clear legal and copyright language about:

1. images
2. screenshots
3. maps
4. PDFs
5. court filings
6. copied source excerpts
7. fair use limits
8. attribution
9. source ownership
10. public versus private documents
11. documents received from individuals or organizations
12. whether files may be redistributed or only cited

Important rule:

Do not publish private, restricted, sealed, or permission unclear documents.

If a lawyer, organization, researcher, or private person sends a file, ask:

May this document be cited, quoted, and included in a public research archive, or should it be used only internally?

If permission is unclear, keep it internal and use it only to locate the public version.

Outreach order

Do not start by sending the whole vault to the biggest organizations.

Use a gradual review path.

1. Trusted individual advocates or researchers
2. Small pro Israel student groups
3. Campus activists who actually debate
4. StandWithUs campus or education people
5. CAMERA or HonestReporting for media related sections
6. Shurat HaDin for legal source verification and court document guidance
7. Larger institutional pitch only after a polished beta exists

The first request should not be:

Can you promote this?

The first request should be:

Would someone on your research or education team be willing to review a small sample and tell me what would make it more useful, accurate, and safe for student advocacy?

What to send during early outreach

Do not send the whole vault first.

Send a small polished beta package:

1. README
2. Methods and Standards
3. 10 to 25 best finished claim notes
4. 3 to 5 source spines
5. 1 short demo video
6. 1 short PDF overview
7. clear disclaimer
8. clear permission and copyright note

The sample should include only the strongest notes. Do not lead with half polished claims.

13b. Legal Review Before Public Release

Before any public release, consult a qualified intellectual property or copyright lawyer.

Do not assume the archive is safe to publish publicly based on general research knowledge alone. Several categories inside the archive carry real legal risk that requires professional review.

Images and visual sources

The archive contains images including maps, diagrams, and historical visuals.

Some of these may carry copyright that is not resolved by a Creative Commons label, a watermark disclaimer, or a general fair use assumption.

Specific concerns:

1. Any image sourced from a stock photography service such as Shutterstock requires a verified license that explicitly permits use in a public repository or redistributable archive.
2. A commercial stock license purchased for personal use does not automatically extend to public redistribution in a downloadable archive.
3. Maps with no clear creator, date, or license status should be flagged for review before inclusion in a public release.
4. Screenshots of organizational or government content may carry rights restrictions depending on the original platform’s terms.

Before release, for each image in the archive:

1. Identify the original source.
2. Confirm the license type.
3. Confirm whether the license permits redistribution in this format.
4. If uncertain, remove the image and link to the original source instead.
5. Have the lawyer specifically review stock-licensed images and any image whose copyright status is unclear.

Internal PDFs in Source Spines

Several source spines reference or contain PDF copies of books, academic publications, and institutional reports.

These are not open access documents. They are copyrighted works.

Including full copyrighted PDFs inside a publicly distributed archive creates serious legal exposure, regardless of whether the archive is non-commercial.

Before release:

1. Do not publish any PDF that is a copyrighted book or commercial academic publication.
2. Remove such files from the public repository entirely.
3. Keep them in a private local vault only for internal research use.
4. In public-facing source entries, replace internal PDF links with external links to the publisher, a library catalog, a legal open-access version, or a purchase page.
5. Quoted excerpts may be usable under fair use, but fair use is not automatic and depends on jurisdiction, purpose, and amount copied. Have the lawyer assess any substantive quotation from a commercial work.

Summary rule for legal review

Do not publish the archive publicly before a qualified lawyer has reviewed:
 
1. All stock-licensed images and their redistribution permissions
2. All images with unclear or unverified copyright status
3. All internal PDFs that are full or partial copies of copyrighted books or commercial publications
4. Any other third-party material where redistribution rights are not clearly established

This review is not optional if the archive is being distributed publicly, shared with organizations, or released on GitHub for download.

Public release questions

Before a note is considered ready for public use, ask:

1. Can students read this quickly?
2. Are the sources real?
3. Are the quotes exact?
4. Are the page numbers exact?
5. Are the claims not overreaching?
6. Is the wording careful enough?
7. Is it clean enough to share?
8. Is it legally safe?
9. Can it be updated?
10. Can it be trusted?
11. Would this survive hostile review?
12. Would a serious researcher understand what the evidence proves?
13. Would a debate opponent be able to expose a weak source or fake citation?
14. Is the claim useful without being emotionally sloppy?

1. Status Check

Every claim must have a STATUS section.

Make sure:

1. The status is accurate.
2. The status is not too aggressive.
3. The status does not say “False” when the better answer is “Misleading,” “Disputed,” or “True but incomplete.”
4. The status does not say “Debunked” when the issue is legally, historically, or academically disputed.
5. The status matches the actual evidence.
6. The status does not pretend a complicated debate is simple.

Use careful statuses when needed:

False
Misleading
Disputed
Partially true
True but incomplete
Unproven
Unsupported
Overstated
Legally contested
Historically contested

2. Key Counterpoints Check

For every claim, check if the KEY COUNTERPOINTS are strong enough.

Make sure:

1. Every counterpoint has a clear opening sentence.
2. The opening sentence is bolded.
3. The point is not too short or lazy.
4. The point explains the argument clearly.
5. The point is detailed enough to be useful in debate.
6. The point matches the EVIDENCE section.
7. The point is backed by the PRIMARY SOURCES section.
8. The point does not overclaim beyond what the sources prove.
9. The point does not use slogans instead of evidence.
10. The point separates legal, historical, moral, and factual categories.

Good counterpoints should not just sound strong. They must be source traceable.

3. Evidence Check

For every claim, check the EVIDENCE section.

Make sure:

1. Every evidence bullet supports at least one Key Counterpoint.
2. Every evidence bullet has a source behind it.
3. Evidence is specific, not vague.
4. Evidence does not introduce a major claim that is not sourced later.
5. Evidence does not rely on emotional wording.
6. Evidence explains what happened, who said it, when it happened, and why it matters.
7. Evidence distinguishes between direct proof, supporting context, expert interpretation, and disputed claims.

Bad evidence:

Many sources prove this.

Good evidence:

The court filing cites Exhibit 512 as trial evidence that the PA had a law institutionalizing prisoner payments.

4. Primary Source Check

For every claim, check the PRIMARY SOURCES section.

Make sure:

1. Every source actually supports the Key Counterpoints.
2. The source is not just related, but directly useful.
3. Quotes are real and match the link.
4. Page numbers are added when the source is a PDF.
5. Weak or unnecessary sources are removed.
6. Stronger primary sources are added where needed.
7. A source is not labeled primary unless it is actually primary for that specific claim.
8. Court filings are described accurately.
9. Reports are not treated as primary sources unless the claim is about what that report says.
10. News articles are not used as the strongest source when a law, court filing, government document, treaty text, official report, or original statement is available.
11. Sources are not stacked just to make the note look stronger.
12. The source explanation says exactly what the source proves.

A source can be excellent and still be the wrong source for a specific claim.

5. Quote and Page Check

Every quote must be checked.

Make sure:

1. The quote is real.
2. The quote is copied accurately.
3. The quote is not taken out of context.
4. The quote has a page number if the source is a PDF.
5. The quote is short enough to avoid copyright problems.
6. The quote actually supports the point being made.
7. The quote is not used to prove more than it proves.
8. Ellipses do not change the meaning.
9. Translated quotes are labeled as translations.
10. If a quote cannot be verified, remove it or mark it as needing verification.

Never keep a quote just because it sounds useful.

6. Claim Evidence Source Alignment Check

This is one of the most important checks.

Every claim must have a clean chain:

KEY COUNTERPOINT → EVIDENCE → PRIMARY SOURCE

For each Key Counterpoint, ask:

1. Is this point mentioned in the Evidence section?
2. Is the evidence sourced in the Primary Sources section?
3. Does the source directly prove the evidence?
4. Does the evidence actually prove the counterpoint?
5. Is there any claim in the note that appears without source support?
6. Is there any source listed that does not connect to a specific counterpoint?
7. Is there any primary source that is only decorative?
8. Can someone trace the whole argument without guessing?

If a Key Counterpoint says one thing, the Evidence section must support that same thing, and the Primary Sources section must give a source for it.

No floating claims.

No decorative sources.

No “trust me bro” links.

the brutal rule:

If KCP 1 says something, Evidence must support it.
If Evidence says something, Primary Sources must prove it.
If Primary Sources do not prove it, rewrite or remove the point.

7. Source Tier Labels

Every claim should rank its sources so readers know what to use first.

Use a simple label system.

For internal working notes, this style is okay:

_↑↑↑ best source!_  
*↑↑↑ mid source*  
_↑↑↑ worst source!_ 😭
***↑↑↑ Best source!***  

For public or institutional release, use cleaner labels:

Best source
Useful supporting source
Background source
Weak or context only source

Use labels carefully:

Best source

Use for the strongest, most debate ready, most authoritative source.

Usually this means:

1. primary source
2. official law
3. court filing
4. treaty text
5. government document
6. original speech or statement
7. official statistics
8. original report with direct data

Useful supporting source

Use for sources that support the point but are not the main anchor.

Examples:

1. expert analysis
2. quality secondary report
3. mainstream news article
4. academic article giving context
5. source that explains the primary material

Background source

Use for sources that help understand the topic but should not carry the main argument.

Weak or context only source

Use for sources that are:

1. less direct
2. secondary
3. advocacy heavy
4. outdated
5. mainly useful for leads
6. replaceable later

Each PRIMARY SOURCE should be marked clearly so someone can quickly know which source to send in a debate.

8. Related Claims Check

For every claim, check the RELATED CLAIMS section.

Make sure:

1. Every linked claim is a real claim file in the vault.
2. No folders, categories, or fake titles are linked.
3. The related claims actually connect to the argument.
4. The tightest and most useful related claims are prioritized.
5. There are not too many related claims.
6. The related claims help the reader move logically through the archive.
7. The related claims do not create random cross links just for graph view.

Use fewer, stronger links.

Bad related claims:

10 random files because they are about Israel

Good related claims:

2 to 4 notes that directly support, contrast, or extend the claim

9. Notes Section Check

The NOTES section should not just summarize the claim.

It should explain:

1. the framing trick
2. the misleading word or phrase
3. the category swap
4. the burden of proof
5. the best debate move
6. the cleanest one line rebuttal
7. what the opponent is likely trying to do
8. what not to overclaim
9. what evidence to lead with
10. what concession is safe to make
11. what distinction matters most
12. further clarification of spesific KCP/Evidence/SP if needed. for example, in Israel enforces an illegal occupation in the notes there is that:
    • On Counterpoint 2 (No prior Palestinian sovereignty): This is the weakest standalone claim in the document. Occupation under international law does not require displacing a prior sovereign state, it can apply to territories as well. So technically, the absence of Palestinian sovereignty does not by itself defeat the occupation argument. However, the claim still carries tactical value as a supporting argument: it removes a layer of the opponent’s framing, reinforces the “disputed territory” framing over “occupied Palestinian territory,” and strengthens the overall case when used alongside the other counterpoints rather than on its own.

The NOTES section should help someone actually use the note in a real conversation.

It should answer:

How do I communicate this clearly under pressure?

10. Strongest Counterarguments Check

Every note should include the strongest opposing argument worth knowing.

Make sure:

1. The opposing argument is not a strawman.
2. It is stated fairly.
3. It includes the strongest version of the other side.
4. It explains why the other side finds the argument persuasive.
5. It does not accidentally concede more than the evidence requires.
6. The response to the counterargument is clear.
7. The note distinguishes between the weak version and strong version of the opposing claim.

This section increases credibility. It shows the archive is not just slogans.

11. Overclaim Check

For every claim, ask:

1. Does the note claim more than the source proves?
2. Does it turn one example into a universal claim?
3. Does it confuse allegation with proof?
4. Does it confuse legal finding with opinion?
5. Does it treat an advocacy report as a court judgment?
6. Does it treat a court filing as a final court finding?
7. Does it treat an expert opinion as settled law?
8. Does it use “always,” “never,” “proves,” or “debunks” too casually?
9. Does it collapse a disputed issue into a simplistic answer?

If the evidence is limited, say exactly what it proves and what it does not prove.

12. Legal Safety Check

This matters for public release.

Check for:

1. defamation risk
2. copyright risk
3. image copyright risk
4. privacy issues
5. sealed or restricted court records
6. private emails or private files
7. claims about named people
8. accusations of terrorism, extremism, fraud, rape, murder, or criminal conduct
9. overconfident legal conclusions
10. documents received from private people or organizations
11. files that may be public to read but not safe to redistribute

For legal or criminal claims, write with precision.

Use:

alleged
reported
court filed
convicted
designated
accused
according to
the filing states
the report concludes

Do not use:

obviously guilty
terrorist linked
criminal
proven forever

unless the source directly supports that wording.

13. Copyright and Image Check

For every image, screenshot, map, chart, PDF, or document excerpt, check:

1. Who owns it?
2. Where did it come from?
3. Is it public domain?
4. Is it under a license?
5. Is it fair use?
6. Is attribution included?
7. Is the image necessary?
8. Could a link or citation replace it?
9. Is it safe to include in a public repository?
10. Does the Repo Root Pack explain the archive image policy?

If uncertain, do not publish the image directly. Link to the original source instead.

14. Duplicate Claim Check

Look for claims that are basically the same argument with different wording.

If two claims overlap too much:

1. Merge them.
2. Keep the stronger title.
3. Move useful sources or counterpoints into the stronger note.
4. Delete or archive the weaker duplicate.
5. Add a redirect note only if needed.
6. Make sure related claims still work after merging.

Do not keep duplicates just because they make the archive look bigger.

Bigger is not better. Cleaner is better.

15. Readability Check

Every note should be readable quickly.

Check:

1. Are sentences too long?
2. Are paragraphs too dense?
3. Can the main point be understood in 20 seconds?
4. Can a debater find the best source fast?
5. Are the strongest points near the top?
6. Are source titles clear?
7. Are notes scannable?
8. Are highlights used sparingly?
9. Does the note avoid unnecessary drama?
10. Is the wording natural and direct?

A good note should work both for slow research and fast debate use.

16. Public Beta Standard

Before showing the archive to an organization, prepare a small beta.

Minimum beta:

1. 25 polished claim notes
2. 5 source spines
3. README
4. Methods and Standards
5. Repo Root Pack legal and copyright notes
6. short video demo
7. short PDF overview
8. clear disclaimer
9. no fake citations
10. no permission unclear documents
11. no unfinished source sections
12. no obvious formatting mess

Do not send 400 half polished notes.

Send 25 strong notes that make the project look serious.

17. Final Standard

A finished claim should have:

1. clear claim
2. accurate status
3. strong Key Counterpoints
4. Evidence that matches those counterpoints
5. Primary Sources that directly support the argument
6. exact quotes
7. page numbers where needed
8. source tier labels
9. useful Related Claims
10. a tactical NOTES section
11. strongest counterarguments
12. no fake links
13. no weak filler
14. no unsourced overclaims
15. no private or restricted documents published without permission
16. careful wording for sensitive accusations
17. clear distinction between what is proven, what is alleged, and what is disputed
18. clean formatting
19. fast debate usability
20. public safety

Priority

Do not add more claims unless something important is missing.

The main job now is:

polishing
tightening
verifying
source checking
quote checking
page checking
legal safety checking
making every existing claim reliable

The archive should not win by having the most notes.

It should win by being the most traceable, usable, and trustworthy.