Live Demo: Doc ↔ Code Explorer

Every doc-to-code relationship below comes from IntentWeave analyzing its own repository — the same evidence that would show up on the “Documentation & Source” chapter of your own Insights Book. No LLM, no manual tagging: CARI grounds doc mentions (headings, bold terms, code identifiers) to real exported symbols via AST + IDF scoring, entirely from the SQLite index.

6 docs 10 source files 1,054 annotations live self-analysis · 2026-07-10

Documentation

• Layered Graph Architecture docs/LAYERED-GRAPH-ARCHITECTURE.md 6 files
• Phase D Spec docs/PHASE-D-SPEC.md 6 files
• Copilot Instructions .github/copilot-instructions.md 6 files
• Changelog CHANGELOG.md 6 files
• README README.md 6 files
• Library API docs/LIBRARY-API.md 6 files

Grounded source files

• facade.ts packages/index/src/facade.ts
  testCoverageterminologyInconsistencytodos
  ↑ 6 docs
• types.ts packages/index/src/types.ts
  driftCountentityIddrift
  ↑ 6 docs
• types.ts packages/core/src/weave/types.ts
  kinddeprecatedconfidence
  ↑ 6 docs
• index.ts packages/core/src/types/index.ts
  EntityReviewStatusannotations
  ↑ 6 docs
• tcg.ts packages/core/src/types/tcg.ts
  severityedgesfilePath
  ↑ 6 docs
• types.ts packages/core/src/transcripts/types.ts
  filefilespaths
  ↑ 6 docs
• indexBuild.ts packages/cli/src/commands/indexBuild.ts
  layerIndicesFromScopebuildPrescriptiveReportDatarebuildFtsIndexes
  ↑ 5 docs
• plugin.ts packages/core/src/plugin.ts
  persistdependenciesprovider
  ↑ 5 docs
• prescriptiveReport.ts packages/index/src/export/prescriptiveReport.ts
  InsightsCallGraphPrescriptiveViolationPrescriptiveCariOverlay
  ↑ 4 docs
• writer.ts packages/index/src/writer.ts
  buildIndexresolveTargetFilewriteCoOccurrences
  ↑ 4 docs

Evidence

Click a doc or source file to see the grounded relationship — the same evidence CARI writes into every Insights Book.

How This Works

1. iw index build parses every source file with tree-sitter and extracts exported symbols (functions, classes, types, interfaces) into the symbols table.
2. Every Markdown doc is scanned for headings, bold spans, code spans, and identifier-like body text. Each mention is matched against the symbol dictionary and written to the annotations table with a confidence score (IDF-penalized so common words like file or date don’t dominate).
3. iw index annotations-for <doc> and cari_annotations_for (MCP) surface this exact relationship — the panel above is just those two queries, aggregated and rendered.

# Reproduce this locally, on your own repo
iw index build
iw index annotations-for docs/ARCHITECTURE.md --min-confidence 0.7

Try it against your own docs — the grounding confidence, the symbol list, and the reverse “referenced by N docs” view are all live, computed in under a second, with zero API calls.