Context
PR #16936 lands learn/agentos/FleetManagerArchitecture.md (resolves #16798). One acceptance criterion of #16798 — the guide becomes retrievable substrate ("KB re-ingestion picks up the guide") — is only satisfiable after merge, once the pipeline-owned KB ingestion has processed the new learn/ file. #16798 closes on merge, so per the Post-Merge-Validation ownership gate (the #16829 class: Resolves #N must not orphan post-merge work, enforced by buildScripts/util/agent-preflight.mjs), this leaf owns that residual. PR #16936's body carries Residual-Owner: #<this ticket>.
The Problem
A learn/ guide that ships but never lands in the Knowledge Base is invisible to the primary consumer the ticket named: ask_knowledge_base as the first-stop retrieval surface for Neo concepts. Ingestion is pipeline-owned and normally automatic — but "normally automatic" is an expectation, not a receipt, and the KB plane has an active stability epic (#17072) with embedding-lane work in flight, so a silent ingestion miss is a live possibility rather than a theoretical one.
The Architectural Reality
- KB ingestion of repo content is pipeline-owned; the guide is registered in
learn/tree.json (223 nodes, lint green at PR head e034adccef).
- The verification surface is the KB MCP:
ask_knowledge_base (semantic) and query_documents / list_documents (exact) — no code changes belong here.
- The render AC of #16798 is already closed pre-merge (reviewer + author renders with repo
mermaid@11.16.0); this leaf is retrievability only.
The Fix
After PR #16936 merges and the next KB ingestion cycle completes:
ask_knowledge_base with 2–3 FM-topology queries (e.g. "FM client topology three hops credential classes", "fleet cockpit truth pipeline INVALID not-wired") and confirm the guide surfaces as a source.- Exact-check via
query_documents/list_documents that learn/agentos/FleetManagerArchitecture.md (current revision) is in the corpus.
- Post the receipts as a comment here and close.
If ingestion did NOT pick the guide up, diagnose (ingestion progress / deployment snapshot tools) and either trigger ingest_source_files for the path or file the defect against the owning pipeline surface — that outcome converts this leaf into its evidence trail.
Acceptance Criteria
Out of Scope
- Any change to the ingestion pipeline, KB services, or the guide itself.
- Portal render verification (closed pre-merge on PR #16936).
Related
- #16798 (the guide ticket this residual descends from) · PR #16936 (carrier) ·
#16829 (the ownership-gate class that mandates this leaf) · #17072 (KB-plane stability epic — context for why a receipt beats an assumption).
Live latest-open sweep: checked latest 20 open issues at 2026-08-14T07:2xZ; no equivalent found. A2A herd-window sweep (last 60 min): no overlapping claims.
Origin Session ID: c61ba6a7-c483-46d2-878c-0086b25df18b
Retrieval Hint: query_raw_memories("FM architecture guide KB retrievable residual owner 16936")
Context
PR #16936 lands
learn/agentos/FleetManagerArchitecture.md(resolves #16798). One acceptance criterion of #16798 — the guide becomes retrievable substrate ("KB re-ingestion picks up the guide") — is only satisfiable after merge, once the pipeline-owned KB ingestion has processed the newlearn/file. #16798 closes on merge, so per the Post-Merge-Validation ownership gate (the#16829class:Resolves #Nmust not orphan post-merge work, enforced bybuildScripts/util/agent-preflight.mjs), this leaf owns that residual. PR #16936's body carriesResidual-Owner: #<this ticket>.The Problem
A
learn/guide that ships but never lands in the Knowledge Base is invisible to the primary consumer the ticket named:ask_knowledge_baseas the first-stop retrieval surface for Neo concepts. Ingestion is pipeline-owned and normally automatic — but "normally automatic" is an expectation, not a receipt, and the KB plane has an active stability epic (#17072) with embedding-lane work in flight, so a silent ingestion miss is a live possibility rather than a theoretical one.The Architectural Reality
learn/tree.json(223 nodes, lint green at PR heade034adccef).ask_knowledge_base(semantic) andquery_documents/list_documents(exact) — no code changes belong here.mermaid@11.16.0); this leaf is retrievability only.The Fix
After PR #16936 merges and the next KB ingestion cycle completes:
ask_knowledge_basewith 2–3 FM-topology queries (e.g. "FM client topology three hops credential classes", "fleet cockpit truth pipeline INVALID not-wired") and confirm the guide surfaces as a source.query_documents/list_documentsthatlearn/agentos/FleetManagerArchitecture.md(current revision) is in the corpus.If ingestion did NOT pick the guide up, diagnose (ingestion progress / deployment snapshot tools) and either trigger
ingest_source_filesfor the path or file the defect against the owning pipeline surface — that outcome converts this leaf into its evidence trail.Acceptance Criteria
ask_knowledge_basedemonstrably returns the guide's content for at least two FM-architecture queries (receipts on this ticket).learn/agentos/FleetManagerArchitecture.mdis in the KB corpus (receipt on this ticket).Out of Scope
Related
#16829(the ownership-gate class that mandates this leaf) ·#17072(KB-plane stability epic — context for why a receipt beats an assumption).Live latest-open sweep: checked latest 20 open issues at 2026-08-14T07:2xZ; no equivalent found. A2A herd-window sweep (last 60 min): no overlapping claims.
Origin Session ID: c61ba6a7-c483-46d2-878c-0086b25df18b
Retrieval Hint:
query_raw_memories("FM architecture guide KB retrievable residual owner 16936")