FAQ Coverage Gaps¶
Concepts from the learning graph not yet covered in docs/faq.md.
Organized by priority based on centrality in the learning graph.
Generated: 2026-05-19 | Total concepts: 496 | Covered in FAQ: ~108 | Gaps: ~388
Critical Gaps (High Priority)¶
High-centrality concepts with many dependencies that should be addressed in FAQ:
Topic 9 — Decision Traces (gaps)¶
- Trace Completeness — high centrality; many chapters reference it
- Suggested: "How do you ensure a decision trace is complete?"
- Policy Version Reference — foundational to compliance chapter
- Suggested: "How are policy versions tracked in decision traces?"
- Trace Replay — key for audit and debugging
- Suggested: "What is trace replay and when do you need it?"
- Counterfactual Trace — advanced but high-value audit concept (partially covered)
- Real-Time Trace Recording — architecture decision with high impact
- Suggested: "How do you capture decision traces in real time without adding latency?"
Topic 12 — Integrating LLMs (gaps)¶
- Function Calling Pattern — widely used in chapters 14 and 16
- Suggested: "What is the function calling pattern for context graph retrieval?"
- Structured Output with Context — important for reliable agent outputs
- Suggested: "How do you get structured JSON outputs from an LLM using context graph data?"
- Prompt Engineering with Context — high practical relevance
- Suggested: "What prompt engineering patterns work best with context graph retrieval?"
- Few-Shot Context Injection — Bloom's Apply level, practical
- Suggested: "What is few-shot context injection and how does it use decision traces?"
Topic 14 — AI Agent Architecture (gaps)¶
- ReAct Pattern — fundamental agent loop design
- Suggested: "What is the ReAct pattern and how does it apply to context graph agents?"
- Human-in-the-Loop — critical for graduated autonomy
- Suggested: "When and how should humans remain in the loop in context graph workflows?"
- Plan-and-Execute Pattern — widely referenced agent design
- Suggested: "What is the plan-and-execute pattern for context graph agents?"
- Agent Trace — distinct from decision trace, important for debugging
- Suggested: "What is an agent trace and how does it differ from a decision trace?"
Cross-Cutting — LLM Foundations (gaps)¶
- Prompt Injection Risk — security concern directly relevant to context graph inputs
- Suggested: "What is prompt injection and how does it threaten context graph systems?"
- Context Window Limit — foundational LLM constraint
- Suggested: "What is the context window limit and how does it constrain context graph design?"
- In-Context Learning — key mechanism underlying context graph effectiveness
- Suggested: "What is in-context learning and why does it make context graphs effective?"
Medium Priority Gaps¶
Topic 15 — Enterprise Use Cases¶
- Finance Automation Use Case — concrete example for business readers
- Sales Engagement Use Case — high-value for sales-tool builders
- Engineering Incident Use Case — popular in developer audiences
- Legal Compliance Use Case — important for regulated industries
- ARR Definition Conflict — specific, memorable example of the context problem
Topic 17 — Market Strategy¶
- Competitive Moat — strategic concept important for founders
- Glue Function — the "beachhead signal" concept is mentioned but not named precisely
- Enterprise AI Market — macroeconomic context for the book's thesis
Topic 13 — Graph Data Modeling¶
- Subgraph Extraction — key retrieval primitive
- Context Graph Migration — practical concern for evolving deployments
- Graph Constraint Enforcement — schema integrity in production
- Event-Driven Graph Update — real-time ingestion pattern
Topic 6 — Process Mining¶
- Process Discovery — foundational process mining step
- Conformance Checking — important for detecting workflow deviations
- Append-Only Log — architectural choice with implications for audit
- Event Sourcing — related pattern, important for context-graph ingestion design
Cross-Cutting — Graph Theory¶
- Centrality Measure — used for identifying high-priority concepts and entities
- Community Detection — useful for surfacing related decision clusters
- Subgraph Matching — important for pattern-based precedent retrieval
- Knowledge Graph Embedding — connects graph and vector search chapters
Low Priority Gaps¶
Leaf nodes and highly specialized concepts appropriate for future FAQ updates:
Topic 1 — Knowledge Graphs and LPGs¶
- GraphML, GraphSON serialization formats
- Open World vs Closed World Assumption
- Graph Index (implementation detail)
Topic 5 — Metadata Registries¶
- UMLS (domain-specific medical standard)
- NIEM (government data standard)
- Dublin Core Metadata
- Administered Item (ISO 11179 detail)
Topic 6 — Process Mining¶
- CQRS Pattern
- IEEE XES attribute structure (partially covered)
Cross-Cutting — Vector Search¶
- HNSW Index (implementation detail)
- Product Quantization
- BM25 (sparse retrieval)
- Approximate Nearest Neighbor
Cross-Cutting — Security¶
- Differential Privacy
- Federated Learning
- AI Red Teaming
Suggested Additional Questions (Top 10)¶
Based on the critical gaps above, the highest-value additions to docs/faq.md are:
- "What is the ReAct pattern and how do context graph agents use it?" (Core Concepts)
- "How do you ensure a decision trace is complete?" (Technical Details)
- "What is prompt injection and how does it threaten context graph systems?" (Common Challenges)
- "When and how should humans stay in the loop in context graph workflows?" (Best Practices)
- "How do you capture decision traces in real time without adding latency?" (Technical Details)
- "What is the function calling pattern for context graph tool use?" (Technical Details)
- "What is in-context learning and why does it make context graphs effective?" (Core Concepts)
- "How do you handle a finance exception workflow with context graphs?" (Best Practices)
- "What is a competitive moat in the context graph market?" (Advanced Topics)
- "What prompt patterns work best when injecting context graph data?" (Best Practices)