Skip to content

docs(roadmap): add Phase 8 — Analysis Depth, renumber language expansion to Phase 7#706

Merged
carlos-alm merged 3 commits intomainfrom
docs/roadmap-phase7-analysis-depth
Mar 30, 2026
Merged

docs(roadmap): add Phase 8 — Analysis Depth, renumber language expansion to Phase 7#706
carlos-alm merged 3 commits intomainfrom
docs/roadmap-phase7-analysis-depth

Conversation

@carlos-alm
Copy link
Copy Markdown
Contributor

@carlos-alm carlos-alm commented Mar 30, 2026

Summary

  • Add detailed Analysis Depth phase (type-aware resolution, points-to analysis, reaching definitions) targeting ≥70% caller coverage
  • Renumber: language expansion (already underway) becomes Phase 7, analysis depth becomes Phase 8
  • Update diagram, sub-phase numbers (7.1–7.5 for language batches, 8.1–8.7 for analysis depth), rationale paragraphs, and all cross-references

Test plan

  • Verify sub-phase numbering is sequential and consistent
  • Verify no stale Phase 7/8 cross-references remain

Insert new Phase 7 between Phase 6 (Native Analysis Acceleration) and
the former Phase 7 (now Phase 8 — Expanded Language Support). All
subsequent phases renumbered 7→8 through 13→14 with cross-references
updated throughout.

Phase 7 targets raising caller coverage from 29% to ≥70% for TS/JS
projects via seven sub-phases: TypeScript-native type resolution
(ts.createProgram), inter-procedural type propagation, field-based
points-to analysis (ACG/Jelly-inspired), barrel file resolution,
enhanced dynamic dispatch (CHA+RTA), precision/recall CI gates, and
reaching definition analysis (PDG foundation).

Only optional runtime dependency: `typescript` for sub-phase 7.1.
All other sub-phases use existing tree-sitter infrastructure.

Motivated by the architecture audit (v3.4.0) which identified 29%
caller coverage as the single highest-impact limitation. Research
grounded in Joern CPG, Jelly, ACG (99% precision/91% recall), and
the TS compiler API.
@claude
Copy link
Copy Markdown

claude bot commented Mar 30, 2026

Claude finished @carlos-alm's task —— View job


PR Review Complete ✅

Reviewing PR #706: docs(roadmap): add Phase 7 — Analysis Depth

Todo List:

  • Phase 1: Root Cause Analysis - Understand the problem being solved
  • Phase 2: Configuration Change Detection - Check for high-risk changes
  • Phase 3: Test Integrity - Look for weakened assertions or removed tests
  • Phase 4: Code Quality - Assess documentation quality and consistency
  • Phase 5: Backlog Compliance - Grade against zero-dep, foundation-aligned, problem-fit criteria
  • Final Assessment - Provide comprehensive review with rating and recommendation

Root Cause Analysis

Problem Being Solved: Architecture audit (v3.4.0) identified 29% caller coverage as the single highest-impact limitation, hindering all downstream features.

Why This Approach: Well-justified "depth over breadth" strategy. Fixing resolution accuracy for existing languages (29% → ≥70% coverage) before expanding language support (11 → 34) ensures every language benefits from the improved pipeline.

Risk Assessment: Very low risk. Documentation-only change with strong research foundation and systematic implementation plan.

Backlog Compliance

  • Zero-dep: ✓ — Only typescript as optional runtime dependency for sub-phase 7.1, lazy-loaded when analyzing .ts/.tsx projects. All other 6 sub-phases use existing tree-sitter infrastructure.
  • Foundation-aligned: ✓ — Fully aligned with all core principles:
    • P1 (always-current): Improves graph accuracy without affecting rebuild speed
    • P4 (zero-cost core): TypeScript integration is optional enhancement
    • P5 (embeddable-first): Pure analysis improvements, no API changes
    • P8 (agent-focused): Directly addresses "AI agents waste tokens" core problem
  • Problem-fit: 5/5 — Directly addresses the core problem from README: "AI coding assistants waste tokens re-orienting in large codebases, hallucinate dependencies, and miss blast radius." 29%→70% caller coverage directly reduces hallucinated dependencies.
  • Breaking: No — Purely additive documentation change, no behavior modifications
  • Tier: Tier 1 (zero-dep ✓ + foundation-aligned ✓)

Critical Concerns

None identified. This is a well-researched, systematically planned documentation enhancement.

Documentation Quality Assessment

  • Systematic renumbering: All phases correctly updated (7→8 through 13→14)
  • Cross-reference consistency: Overview table, dependency graph, verification strategy all updated
  • Technical rigor: 7 sub-phases with specific techniques, expected coverage gains, and research citations
  • Research grounding: Proper academic references (Joern CPG, Jelly, ACG achieving 99% precision/91% recall)
  • Dependency transparency: TypeScript dependency clearly documented as optional, lazy-loaded

Final Recommendation

  • Rating: ⭐⭐⭐⭐☆ (4/5)
  • Action: APPROVE
  • Reasoning: High-quality documentation of well-researched technical strategy addressing the project's highest-impact limitation. Excellent technical depth, proper research foundation, and systematic implementation plan. Only deduction is this being documentation rather than implementation, but the planning quality is exceptional.

This sets up Phase 7 for successful implementation with clear technical direction and measurable success criteria.

@greptile-apps
Copy link
Copy Markdown
Contributor

greptile-apps bot commented Mar 30, 2026

Greptile Summary

This PR inserts a new Phase 7 — Analysis Depth between Phase 6 (Native Analysis Acceleration) and the former Phase 7 (now Phase 8 — Expanded Language Support), then mechanically renumbers all downstream phases (7→8 through 13→14) with full cross-reference updates throughout the document.

Key changes:

  • New Phase 7 with 7 well-specified sub-phases (7.1–7.7) targeting ≥70% caller coverage for TypeScript/JavaScript, up from 29%
  • All subsequent phase headers, overview table rows, dependency graph lines, Depends on: annotations, and scope-note forward-references updated consistently
  • The verification strategy table (rows 7–14) was also corrected — the original table had the wrong verification criteria mapped to the wrong phase numbers; the new table correctly aligns each criterion to its phase
  • One pre-existing cross-reference that was incorrect in the original document (13.3 Depends on 11.1 (GitHub Action) where 11.1 was Natural Language Queries, not the GitHub Action) is incidentally fixed to 13.1 in the new numbering

Confidence Score: 5/5

Safe to merge — documentation-only change with consistent renumbering and well-reasoned new phase content

All phase numbers, anchor links, Depends on annotations, overview table, dependency graph, and verification table are updated consistently. The new Phase 7 content is internally coherent and well-referenced. No logic, code, or schema changes are included. The PR incidentally fixes a pre-existing incorrect cross-reference in section 13.3 and repairs a scrambled verification strategy table.

No files require special attention

Important Files Changed

Filename Overview
docs/roadmap/ROADMAP.md Inserts Phase 7 (Analysis Depth) with 7 well-specified sub-phases, renumbers Phases 7–13 → 8–14, updates all cross-references and dependency graph; also fixes a previously scrambled verification strategy table

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    P1[Phase 1: Rust Core] --> P2[Phase 2: Advanced Analysis]
    P2 --> P3[Phase 3: Developer Experience]
    P3 --> P4[Phase 4: Resolution Accuracy]
    P4 --> P5[Phase 5: TypeScript Migration]
    P5 --> P6[Phase 6: Native Analysis Acceleration]
    P6 --> P7[Phase 7: Analysis Depth NEW]
    P7 --> P8[Phase 8: Expanded Language Support]
    P6 --> P9[Phase 9: Runtime and Extensibility]
    P6 --> P10[Phase 10: Quality Security and Tech Debt]
    P6 --> P11[Phase 11: Intelligent Embeddings]
    P11 --> P12[Phase 12: Natural Language Queries]
    P6 --> P13[Phase 13: GitHub Integration and CI]
    P11 -->|risk_score, side_effects| P13
    P1 & P2 & P3 & P4 & P5 & P6 & P7 & P8 & P9 & P10 & P11 & P12 & P13 --> P14[Phase 14: Advanced Features]
Loading

Reviews (1): Last reviewed commit: "docs(roadmap): add Phase 7 — Analysis De..." | Re-trigger Greptile

…s depth

Language expansion (now Phase 7) is already underway; analysis depth
(now Phase 8) benefits more languages when it lands after breadth.
Swapped sections, renumbered sub-phases, and updated cross-references.
@carlos-alm carlos-alm changed the title docs(roadmap): add Phase 7 — Analysis Depth docs(roadmap): add Phase 8 — Analysis Depth, renumber language expansion to Phase 7 Mar 30, 2026
@carlos-alm carlos-alm merged commit 6a8d148 into main Mar 30, 2026
11 of 12 checks passed
@carlos-alm carlos-alm deleted the docs/roadmap-phase7-analysis-depth branch March 30, 2026 10:55
@github-actions github-actions bot locked and limited conversation to collaborators Mar 30, 2026
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant