What we checked.

The earlier map omitted graph flush, dreaming, summary indexing and live-read instructions. These run through a bounded tool loop. Configuration gates the subsystem; SaaS local graph access is deliberately restricted. It is not Knowledge L1 or authoritative UMS hierarchy.

Action: Added a dedicated graph-memory walkthrough and memory-table row.

The optional LanceDB plugin can prepend retrieved memory at before_agent_start and capture short candidate text at agent_end. Its heuristics and embeddings are distinct from the topic/experience flush prompt. A blanket claim that all recall requires memory_search would be wrong.

Action: Documented as a conditional plugin path, not a proven live deployment.

Direct chart generation/edit includes schema grounding, read-only SQL validation and bounded repair. Dashboard TL;DR has its own five-bullet system prompt. Genie remote chart follow-ups and the universal viewer Python NL-to-SQL prompt are separate again.

Action: Added each prompt builder and an end-to-end chart walkthrough.

The local SDK runner uses systemPrompt type=preset, preset=claude_code, plus an append, setting sources, a local plugin and persisted sessions. The preset implementation and live project settings are not contained in this snapshot. AgentCore is another remote boundary.

Action: Marked external preset/runtime dependencies explicitly; no invented flattened prompt.

The rewrite prompt preserves names/dates and forbids invented scope. Reranking requests a permutation of existing candidate indices; application parsing checks it. These are distinct calls from the final Ask answer and have separate preference resolution.

Action: Added retrieval-stage prompt inspection and a dedicated walkthrough.

Follow-up suggestions, session slugs, Matrix DM names, vision captions, image understanding, voice replies, TTS summary/translation and music generation are source-visible consumers. Speech and embedding requests are not all chat-style prompts.

Action: Added auxiliary and media walkthroughs; do not equate invocation sites with runtime request counts.

The coordinator builds planner, worker, coverage, synthesis and verification prompts under workstream/source-policy budgets. Child-run initialization and tools supply additional context beyond each task string.

Action: Added the full coordinator source and research walkthrough.

The generated-app template contains an LLM SDK accepting caller-supplied messages plus embedding-backed document search. A snapshot of the builder repository cannot enumerate prompts later authored by every tenant app.

Action: Separate generated application calls from the app-authoring agent.

Gateway workspace.ts reads docs/reference/templates. A path-only exclusion of every docs/ file would miss real runtime instructions. The expanded catalog includes that directory and all checked-in skill/instruction assets in the selected runtime roots, while development skills remain separately classified.

Action: Recorded a runtime-template exception in the census and added conditional asset badges.

Retained wiki digest/vault extraction/team composition and the reference experience-compaction prompt must not be silently counted as the default workspace pipeline. The native summary prompt remains the active summary source. Legacy route reachability is not certified by file presence.

Action: Kept reference/retained labels and exact source links rather than claiming deployed parity.

The aibot_internal wrapper is an outbound echo-stripping envelope. Its comments explicitly say the model still reads and acts on wrapped text. It must not be described as an authorization or prompt-injection isolation boundary.

Action: Documented the distinction between formatting/sanitization, prompt policy and application access controls.

The gateway has non-production system-prompt inspection files; Matrix DM name extraction logs its constructed request; CC has optional local-evaluation request artifacts. These are source-visible logging surfaces, not evidence that a particular deployment stores or exposes user data.

Action: Flagged for environment/retention review. No live logs or credentials were read.

Native chat/Responses request builders, tenant model/runtime injection, Knowledge feature/user model preferences and CC stage context selection all affect the payload. Default templates alone cannot reproduce a live user-specific request.

Action: Added assembly/transport code to the explorer and retained explicit live-config gaps.