docs: remove competitive sections from FOUNDATION.md

[carlos-alm]

Summary

• Remove Competitive Position and Landscape License Overview sections from FOUNDATION.md — these don't belong in the project foundation document

[claude]

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

---

Reviewing PR: Remove competitive sections from FOUNDATION.md

Todo List:

• Read FOUNDATION.md to understand the changes
• Analyze removed content and rationale
• Conduct 5-phase review process
• Evaluate backlog compliance
• Provide structured feedback and rating

---

Root Cause Analysis

Problem Being Solved: Improper content organization — competitive analysis and license overview belonged in dedicated documentation files (generated/competitive/), not in the project foundation document.

Why This Approach: FOUNDATION.md should focus on core principles and architectural decisions. The removed content was reference material better suited for the generated/competitive/ directory where it already exists in COMPETITIVE_ANALYSIS.md.

Risk Assessment: MINIMAL — This is pure documentation reorganization with no functional impact.

Backlog Compliance

• Zero-dep: ✓ — Documentation-only change, no runtime dependencies
• Foundation-aligned: ✓ — Actually improves foundation document clarity by removing content that doesn't belong
• Problem-fit: 3 — Documentation organization improves maintainability but doesn't directly address core "AI agents getting lost in codebases" problem
• Breaking: No — No functional changes, purely organizational
• Tier: 1

Critical Concerns

None. This is an excellent example of proper content organization.

The removed sections were:

1. Competitive Position (21 lines) — Detailed competitive ranking analysis
2. Landscape License Overview (20 lines) — License breakdown across 22 competitor tools

Both sections exist in more complete form in generated/competitive/COMPETITIVE_ANALYSIS.md where they belong. The foundation document is now focused purely on architectural principles and design decisions.

Technical Review

• Content accuracy: Verified removed content exists in proper location (generated/competitive/COMPETITIVE_ANALYSIS.md)
• Document structure: Foundation document flow improved — now ends cleanly with "What We Build vs. What We Don't"
• References: All internal references preserved (e.g., link to COMPETITIVE_ANALYSIS.md in removed section was self-referential)
• Formatting: Clean removal with proper section break preservation

Final Recommendation

• Rating: ⭐⭐⭐⭐☆ (4/5)
• Action: APPROVE
• Reasoning: Clean documentation reorganization that improves foundation document focus. The competitive analysis content belongs in generated/competitive/ where it can be updated independently. This strengthens the foundation document by keeping it focused on architectural principles rather than market positioning.

Minor note: Only reason this isn't 5/5 is that it's purely organizational — excellent execution of a straightforward cleanup task.

---

[greptile-apps]

Greptile Summary

This PR removes two externally-focused sections — Competitive Position (ranking table, differentiation matrix) and Landscape License Overview (per-project license breakdown) — from FOUNDATION.md, leaving only the core-principles and build-scope content that the document is designed to capture. The closing revisit note is trimmed to drop the now-irrelevant competitive-landscape trigger.\n\n- The removed content is non-trivial and time-sensitive (e.g. "#7 out of 22 as of February 2026") — keeping it in a foundation doc risks it going stale and misleading contributors.\n- Competitive analysis material is better housed in generated/competitive/COMPETITIVE_ANALYSIS.md (already referenced in the removed section) rather than in a principles document.\n- The remaining document is self-consistent: Principles 4 and 8 still reference competitors in passing for motivational context, but no dedicated competitive tracking sections remain.\n- No code, configuration, or test files are affected.

Confidence Score: 5/5

Safe to merge — documentation-only change with no functional, configuration, or code impact.

Single-file docs-only PR that removes content which was already identified as out-of-scope for a foundation document. The remaining document is internally consistent, no references to the removed sections are left dangling, and the closing sentence update correctly reflects the stripped content. Zero risk of regression.

No files require special attention.

Important Files Changed

Filename	Overview
FOUNDATION.md	Removes "Competitive Position" and "Landscape License Overview" sections; trims the closing revisit note accordingly — clean, focused documentation change with no functional impact.

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A[FOUNDATION.md] --> B[Why Codegraph Exists]
    A --> C[Core Principles 1-8]
    A --> D[What We Build vs. What We Don't]
    A --> E[Closing Note]

    B:::kept
    C:::kept
    D:::kept
    E:::kept

    A -.->|removed| F[~~Competitive Position~~]
    A -.->|removed| G[~~Landscape License Overview~~]

    F:::removed
    G:::removed

    classDef kept fill:#d4edda,stroke:#28a745,color:#155724
    classDef removed fill:#f8d7da,stroke:#dc3545,color:#721c24

Loading

_{Reviews (1): Last reviewed commit: "docs: remove competitive position and li..." | Re-trigger Greptile}