Knowledge
An agent can describe a problem before it knows the API that solves it. Knowledge gives it one query contract over sources you choose: search for a known term, or browse the documentation until the right term appears.
Choose where the guide redirects focus.
APPLE DEVELOPER · EXACT SECTION + SOURCE URLFrom a problem to a symbol
“Move focus between disconnected controls” describes a task, but leaves out UIFocusGuide. An agent can enter through the platform and UI index, follow UIKit’s focus navigation, and reach the guide’s preferredFocusEnvironments property. Each step supplies vocabulary for the next query.
Known terms take the short path. Symbol search returns declarations; prose search returns document sections. Every result carries a source URL, section identifier, and a short passage. The agent can inspect the match before fetching the full section.
Two ways into unfamiliar material
The index groups sources by platform and domain: UI, media, networking, performance, and machine learning. It answers where to look. Within a source, the documentation tree preserves tables of contents, breadcrumbs, and related links. It exposes neighboring concepts that a ranked list of search hits can miss.
Document structure
The operator selects the sources; Knowledge applies the same query contract to them. DocC pages retain headings, anchors, declarations, and navigation links. HTML, Markdown, and numbered standards become the same section-based document shape. Search, browsing, and citation all refer to those sections, so finding a passage does not lose its place in the original document.
What improved retrieval
I compared BM25 with a hybrid BM25-and-vector path. Both passed all ten cases in a keyword-heavy evaluation; adding vectors did not improve those results. The more useful change was preserving routes through the documentation. Exact search handles names the agent already knows. Browsing helps it find names missing from the question.