RAG, Memory & Context

Citation (topic)

Last updated 2026-09-22

What's new

2026-09-22
  • The new lesson focuses on using the Claude API (a tool that lets you interact with an AI assistant) to add citations (references to sources) to answers, making them more transparent and trustworthy.
  • You'll learn to modify document messages to enable citations, creating a clear, inspectable process that connects user questions to specific sources.
  • Citations work with various document types, not just PDFs, and can be integrated into user interfaces to make source information easily accessible.
  • This feature is particularly useful when users need to verify information or explore broader contexts, enhancing the AI's reliability and user trust.
2026-09-19
  • The new lesson focuses on the Claude API (a tool that lets software talk to the AI model Claude) and how to use its text editor tool to manipulate files.
  • You'll learn to create a clear, testable connection between Claude and your application by naming inputs, showing actions, and making results inspectable.
  • The text editor tool can view, edit, create, and undo changes to files, providing comprehensive file manipulation capabilities for Claude.
  • While the tool's structure is built into Claude, you still need to provide the actual implementation and include a small schema (a blueprint for data structure) when making requests.
2026-09-10
  • **LLM inference (using AI to generate or analyze content like text, audio, or video) costs are rising**, with businesses needing to optimize or reduce token (small pieces of data) usage to manage expenses.
  • **Memory usage increases with more input tokens (data)**, which can lead to out-of-memory errors, especially with longer context lengths.
  • **Inference speed varies**, with the time to generate the first token often being slower than subsequent tokens, impacting user experience.
  • **New tools and optimizations are emerging** to help manage these challenges, with benchmarks and guides available to evaluate different solutions.
2026-08-25
  • Learn to define tasks clearly and check AI outputs before using them—no coding skills needed.
  • An agent (software that helps reach a goal while you stay responsible for results) guides these steps.
  • Use five key checks: brief quality, evidence handling, example quality, exploration range, and prompt repair.
  • Practice by reading scenarios cold, choosing an answer, then comparing explanations to spot weak options.
2026-08-22
  • **Decision Loop**: Use a clear, step-by-step process to troubleshoot and improve AI outputs, focusing on one change at a time (e.g., prompt clarity, format).
  • **Human Review**: Always verify important or consequential AI-generated outputs with evidence and human oversight, especially before sharing externally or making decisions.
  • **Model Matching**: Choose the right AI model (e.g., Claude) for the task based on cost, speed, and quality needs, not just size or prestige.
  • **Data Protection**: Protect sensitive information by anonymizing or minimizing data before using AI tools, and always follow organization policies.
2026-08-19
  • You can automate your business using AI tools like Claude (a type of AI assistant), even if you don't know how to code, and the course provides real-world templates that work.
  • The course teaches you to think of AI as a co-worker (someone who helps you with tasks) rather than just a chatbot (a simple question-answer tool), allowing you to assign multiple tasks at once.
  • AI can handle various tasks simultaneously, such as answering emails, drafting proposals, and researching, without getting tired or sick, and at a low cost.
  • The course emphasizes understanding how AI works to create valuable automations, rather than just using it for generic tasks and getting bland results.
2026-08-13
  • The **Claude Code desktop app** (a user-friendly software for AI tasks) is now recommended for beginners, offering features like voice mode and browser automations, making it more accessible than the terminal (a technical tool for coding).
  • Beginners should start with the "local" setting in Claude Code, which runs tasks directly on their computer, and ignore advanced options like "cloud" or "remote control" for now.
  • In settings, beginners should leave "instructions for Claude" blank unless they have a specific need, and turn on most capabilities, except for advanced features like "pull requests" (a coding term for proposing changes to a project).
  • For permissions, the "auto" mode is suggested, which allows Claude Code to perform tasks automatically but stops potentially dangerous actions, balancing convenience and safety.
2026-08-07
  • **Build stronger prompts**: Use six key parts (context, role, examples, format, step-by-step work orders, and prompt chaining) to create clear and effective instructions for AI tools like Claude (an AI assistant).
  • **Evaluate AI output**: Check AI responses for accuracy, completeness, consistency, and bias or fit, using evidence like quotes, citations, and primary sources.
  • **Verify high-stakes information**: Always confirm critical details with a human and authoritative sources, especially for important decisions in areas like law, finance, or medicine.
  • **Reduce hallucinations**: Use techniques like repeated answers, reasoning checks, and supplied context to catch AI-made-up information, but remember these methods don't guarantee perfect accuracy.
2026-08-04
  • Many people blame AI for bad results without checking simple settings like the model (the AI's "brain" and how hard it works) and effort level, which can be adjusted in tools like ChatGPT, Gemini, or Claude.
  • AI won't write like you unless you train it using examples of your past writing, like connecting it to your email to learn your style and tone.
  • More context isn't always better; giving AI too much information can make it "dumber" and less able to focus on the task, so it's better to provide the right amount of relevant context.
  • When extracting data, don't blindly trust AI's numbers; ensure it's only using the documents you provided, and make it cite sources for verification.
2026-07-31
  • Kepler, a company specializing in AI for financial services, emphasizes the importance of trustworthy AI that can produce verifiable work products, not just more content (Kepler is an AI tool for finance that focuses on creating reliable outputs).
  • Traditional financial tools like Bloomberg and FactSet (paid online services for financial data) are used to shift blame if information is wrong, but they don't help create work products (like reports or analyses).
  • The main challenge in finance is getting AI to move from searching for information to creating reliable work products, like investment memos or financial models (DCF stands for Discounted Cash Flow, a way to value a company).
  • Verification (proving a number or fact is correct in a way that can be repeated and checked) is crucial in finance for regulatory compliance and making sound investment decisions.
2026-07-28
  • Tokens (small text units AI models process) matter for response length, cost, and speed, so budget them wisely in your prompts.
  • Context windows (the AI's temporary memory) are finite, so manage them to avoid quality loss as conversations grow or large files are added.
  • Prompts (your messages to the AI) should clearly state goals, context, and desired outcomes, with standing rules for persistent guidance.
  • Always verify AI responses, as they can sound confident but be incorrect, including fabricated citations, made-up statistics, or plausible false facts.

Key points

What it is

  • Citations are references to source material that let you check an AI's work, turning it from a guessing tool into a reliable assistant.
  • They link claims back to verifiable sources, making AI outputs useful for real work by allowing you to trust and act on the information.
  • Citations help distinguish accurate information from AI hallucinations (made-up content that sounds confident but is incorrect).

How to use it

  • Ask the AI to cite its work by adding a validation prompt at the end of your conversation, requesting it to check and ensure everything links back to the source text.
  • For deep research, use tools like Claude Code (a tool for building AI workflows) to set clear success criteria, such as getting multiple sources and explaining the significance of each piece of information.
  • Use NotebookLM (a tool for finding and organizing web sources) to specify the number of sources you want and have the AI research from different perspectives.

Watch out for

  • AI can generate fabricated citations (fake references that look official but don't exist), so always inspect the source text behind each citation.
  • Treat every citation as a starting point for inspection, and use tools that show source provenance (the origin and history of a source) to rank sources by credibility.
  • Never rely on an answer simply because it sounds absolute or complete; always verify the citation and confirm the content supports the claim.

Tools named

  • Claude Code (a tool for building AI workflows), NotebookLM (a tool for finding and organizing web sources)

Lesson 1: What is Citation (topic) and why it matters

In AI development, "citations" (specific references to source material) are the mechanism that lets you verify an AI's outputs and trust its work. When an AI generates a contract review or a research summary, it should provide page numbers, section headers, or direct quotes so you can confirm the information actually exists in the source document. Without citations, the AI is just making claims you cannot check.

Citations transform AI from a guessing intern into a reliable assistant. When an AI pulls out the 20% most important elements from a 50-page contract, it should cite exactly where each item came from. You then have the AI validate those citations, ensuring every referenced point is directly in the original document. This verification step is critical because AI models produce different outputs each time you run them (due to their "temperature" setting) and their behavior changes with slight prompt variations.

For AI development, citations solve a fundamental trust problem. An AI that does not cite its sources leaves you wondering whether its output is accurate or hallucinated. In research contexts, citation prediction becomes a challenge because semantic similarity (matching words) cannot distinguish between a genuinely novel finding and an obscure but irrelevant detail. As more scientific papers are both written and evaluated by AI, robust citation systems will determine whether AI-generated research is reproducible and trustworthy.

The goal is to structure your AI's outputs so that every claim points back to a verifiable source. This is what makes AI agents useful for real work: they let you see the results, verify the results, and take action on information you can trust.

Sources

Lesson 2: How to use Citation (topic): step-by-step

To use citation (linking every claim back to its source file) with an LLM-built answer, start by asking the AI to cite its work. A simple approach: add a validation prompt at the end of your existing conversation, asking the AI to check its own citations and ensure everything links back to the source text. For documents under 50 pages, you can paste this prompt directly into the thread.

An LLM (large language model) generates text by completing patterns, which means a confident-sounding answer can be wrong. Citations are the visible proof that lets you inspect the connection between a claim and its actual source. A citation can look official even when the underlying claim hasn't been verified. For example, the model might produce a phrase shaped like a section reference that resembles a real source even if that section doesn't exist. Formal structure does not create evidence.

When you want deep research across hundreds of sources, use a tool like Claude Code with dynamic workflows. Set clear success criteria, such as "get at least five sources" and "for every bit of information, tell me a 'so what'." Have the AI cross-reference and verify information rather than just summarizing. A finished report should have every claim link back to its file — a cited due diligence output.

Finally, use NotebookLM to surface high-quality web sources while staying in control. You can specify "find 20 sources" and the tool will research from different perspectives, finding primary sources or related work. Always follow the source text and inspect each citation instead of relying on a confident answer.

Sources

Lesson 3: Best practices and pitfalls

When using an LLM (large language model) for research or writing, citations are your main tool for verifying the output. A common mistake is to trust citations just because they look official. An LLM can generate a citation with a perfect format—a section reference, a date, or a precise statistic—even if the cited source does not exist. This is called a fabricated citation. The formal structure does not create evidence. A confident error can sound completely sure.

To avoid this pitfall, adopt a "trust, but verify" habit. Always inspect the source text behind each citation. Click through to confirm the link works and that the content actually supports the claim. If a citation leads to a 404 error (page not found) or the referenced information is missing, the claim is unreliable. The purpose of a citation is to make accuracy reviewable, not to be a decorative reference.

Best practice is to treat every citation as a starting point for inspection. Use tools that surface source provenance (the origin and history of a source) so you can rank sources by credibility and reuse them properly. When building your own work, always maintain a trail of accuracy by linking back to original material. This protects your own credibility and allows others to verify your claims. Never rely on an answer simply because it sounds absolute or complete. The decision lens should be: what action does this citation support? If the answer is "just trust me," you need to inspect the source.

Sources