<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Search on Human in the Loop</title><link>http://aitip.tech/en/tags/search/</link><description>Recent content in Search on Human in the Loop</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Sun, 15 Nov 2026 11:00:00 +0800</lastBuildDate><atom:link href="http://aitip.tech/en/tags/search/index.xml" rel="self" type="application/rss+xml"/><item><title>Chunking for a Knowledge Base: One Markdown Convention, Chunked by Heading</title><link>http://aitip.tech/en/posts/pdf-to-markdown-chunking/</link><pubDate>Sun, 15 Nov 2026 11:00:00 +0800</pubDate><guid>http://aitip.tech/en/posts/pdf-to-markdown-chunking/</guid><description>What the knowledge base maintains is Markdown: PDFs, web pages, manual material and Q&amp;amp;A all follow one convention, and the chunker reads only the Markdown heading tree and block structure. This post covers the convention, PDF transcription and checks, the heading-level chunking rules, and the retrieval evaluation showing why one heading per chunk works best.</description></item><item><title>Building an Enterprise Knowledge Base: Content Model, Git Publishing and Hybrid Search</title><link>http://aitip.tech/en/posts/knowledge-base-architecture/</link><pubDate>Sun, 15 Nov 2026 10:00:00 +0800</pubDate><guid>http://aitip.tech/en/posts/knowledge-base-architecture/</guid><description>A knowledge base works like a library: categories, books and editions, tables of contents, passages, narrowing the context level by level to give the chat model accurate knowledge. Drawing on a bilingual project with about 1,800 documents, this post covers defining the content model first, using Git for review and publishing, keeping exact document fetch separate from hybrid search, and choosing retrieval methods with an evaluation set instead of intuition.</description></item></channel></rss>