Skip to content
🧭
System district

Knowledge Layer

Open this district when you need the short, current boundary between Recall/QMD retrieval, RAG Sync ingestion, Almanac drift stewardship, and the next route that owns the deeper answer.
Validated · Oct 6, 2026The October 6 district-exits pass adds the standardized Continue-from band so this district exits into its sibling system lanes. The owning-route proof-currency pass re-checked every surface the district points readers at — the API Reference service-map, Observability source-health contract, and Infrastructure platform-versus-observability boundary — and the capture-era July narration is retired.
Start here on phone

Take the shortest knowledge exit first. The contract section below only matters when the map or API route still is not enough.

Network TopologyUse this when the missing answer is placement on the map.API ReferenceUse this when the question is really about endpoints or service shape.Contract boundaryUse this when you still need the short retrieval-vs-ingestion-vs-stewardship split.
Current snapshot
  • Retrieval surface: Agents still reach the knowledge layer through memory_search and memory_get while Atlas and API Reference stay human-facing explanation surfaces.
  • Freshness path: @lambda-curry/currykit-rag-sync still feeds Recall/QMD on a 15-minute cadence, and Almanac still handles documentation drift as a separate accuracy loop.
  • Boundary rule: This landing explains the current model first, then hands off detailed topology to Network and endpoint specifics to API Reference.
Reader orientation

Choose the shortest knowledge question first

This district is a quick sorter, not a second system manual. Take the first real exit as soon as the question is already about topology or API detail.
Start with Network Topology

Open the map when the missing answer is where Recall/QMD, RAG Sync, and the supporting services sit in the wider network.

Open Network Topology

Stop once you can point to the knowledge nodes, their neighbors, and the shared infrastructure they depend on.

Jump to API Reference

Open the reference when the question is about endpoints, integration surfaces, or which Currykit service owns the next technical move.

Open API Reference

Stop once you know the service name, endpoint family, or surface that actually answers the implementation question.

Current knowledge contract

Keep retrieval, ingestion, stewardship, and helper surfaces separate

Atlas is most useful here when it prevents the Knowledge district from collapsing into one generic idea about memory. These four lanes are intentionally distinct.
Current model
Recall / QMD owns retrieval

This is the shared retrieval service. It owns indexed search, semantic recall, and the passages agents read back through memory tools.

Stay on this district when you need the shortest boundary between the retrieval surface and the pages that explain it.

Current model
RAG Sync owns ingestion cadence

The ingest pipeline still pulls published source material from Notion, Jira, and Linear into the shared Recall/QMD store on a scheduled cadence.

Atlas keeps the cadence fact here so readers can separate retrieval from the upstream feed that keeps it current.

Current model
Almanac owns documentation drift correction

Almanac reviews published docs for drift so the knowledge layer stays trustworthy, not merely recent.

Use this boundary when a reader starts to collapse shared knowledge stewardship into retrieval or API behavior.

Current model
QMD Public Proxy is a supporting helper surface

The scoped helper surface on port 18790 belongs to the infrastructure story, not the default reader start path.

Leave for Infrastructure once the real question is hosting, port mapping, or the helper-surface placement around shared knowledge.

Next routes

Follow the knowledge story through the owning lanes

After the contract is clear, leave for the route that owns the deeper answer instead of staying on the landing page.
Infrastructure Layer

Open this when the missing answer is port mapping, shared service hosting, or where the QMD Public Proxy belongs.

Open Infrastructure
Architecture

Use ADR 14 and the surrounding system rationale when you need the why behind remote HTTP access and shared QMD.

Open Architecture
Knowledge Layer Sync

Jump to the workflow trace when you want the step-by-step ingest and drift-correction loop rather than the short district contract.

Open Knowledge Sync Workflow

Continue from Knowledge

Observability

Open the sibling district when the question shifts from how knowledge is retrieved and kept current to how source health is monitored and explained.

Open Observability
Bridge

Use the transport district when the missing piece is how agents actually call each other while the knowledge layer answers flow underneath.

Open Bridge
FAQ

Take the question-routing layer when you are still separating Atlas explanation from Watchtower live status.

Open FAQ