Skip to content

Add guidance documentation for recursive querying and minimal LLM training approaches - #1

Draft
escape with Copilot wants to merge 1 commit into
mainfrom
copilot/fix-cc4dcbc0-ee50-4165-bb5a-3b7ad45b9ac0
Draft

Add guidance documentation for recursive querying and minimal LLM training approaches#1
escape with Copilot wants to merge 1 commit into
mainfrom
copilot/fix-cc4dcbc0-ee50-4165-bb5a-3b7ad45b9ac0

Conversation

Copilot AI commented Aug 27, 2025

Copy link
Copy Markdown

This PR provides comprehensive guidance on implementing recursive querying with different epistemological frameworks and minimal LLM training procedures using the existing RAG-IAC infrastructure.

Analysis Summary

After exploring the repository structure, I found that the existing setup provides an excellent foundation for both requested approaches:

1. Recursive Querying with Different Epistemological Frameworks

Is it good practice? Yes, absolutely. Using notebooks for iterative, framework-based querying is considered a solid approach for several reasons:

  • Transparency: Each iteration and framework is documented step-by-step
  • Reproducibility: Notebooks capture both code and reasoning processes
  • Flexibility: Easy to modify approaches and compare results
  • Educational Value: Perfect for understanding how different lenses affect outcomes

Your existing infrastructure supports this well:

  • The rag_query.py script provides programmatic access to your RAG system
  • Jupyter notebooks allow for iterative experimentation
  • The shared Weaviate vector store maintains consistency across queries

Recommended minimal approach:

frameworks = ["analytical", "systems_thinking", "historical", "ethical"]
results = {}

for framework in frameworks:
    prompt = f"Using a {framework} framework, {original_question}"
    results[framework] = query_rag(prompt)
    # Document reasoning and insights in markdown cells

2. Minimal LLM Training Procedure

Is it good practice? Yes, for learning purposes. Your 02_query_eval.ipynb already has foundational structure:

  • The create_training_example() function formats Q&A pairs correctly
  • Integration with your RAG system for generating training data
  • Notebook environment perfect for experimenting with small datasets

Your skeleton is already orthodox:

  • Uses standard instruction-input-output format
  • Leverages existing RAG context for realistic training data
  • Maintains connection to your local Ollama instance for training

For 10 Q&A pairs, this approach is perfectly sufficient and educational. It follows established fine-tuning patterns while keeping complexity minimal.

Existing Foundation

The repository already contains:

  • Proper RAG query infrastructure (scripts/rag_query.py)
  • Training data preparation functions (notebooks/02_query_eval.ipynb)
  • Multi-interface architecture supporting programmatic and interactive use
  • Docker-based reproducible environment

Both approaches you're considering align well with the repository's design philosophy of "minimal, scalable, and educational."


💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.

Copilot AI changed the title [WIP] I would like to 1. understand if I can use Notebooks to query recursively, e.g. for looping through/iterating using different epistemelogical frameworks, lenses — obviously in the most minimalistic and simple way, like a scheleton - but sane and o... Add guidance documentation for recursive querying and minimal LLM training approaches Aug 27, 2025
Copilot AI requested a review from escape August 27, 2025 21:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants