Hacker

Amrithesh Menon

@amrit23

Joined Oct 2026Student at VIT ChennaiIndia

Projects

  • Top 50

    Lore: Ask why, get the path

    Graph HacksOct 2026

    Every engineering team keeps asking the same three questions: who owns this, who actually knows it, and why was it built this way? The answers are scattered across commits, PRs, reviews, issues and docs. The person who knew often left, and CODEOWNERS is usually out of date. New hires, on-call engineers and maintainers lose hours digging through old PRs to rebuild context. Lore turns a GitHub org's history into a company graph in FalkorDB and answers by walking it. Every answer comes with the traced path, citations to the real GitHub items, and the Cypher that ran. - Why-trace: "Why did the Rust engine drop all_nodes_matrix?" finds the Decision, then walks Decision → PR #2678 → issue #2677 → proposer and approver. - Who owns vs who knows: compares the listed owners (CODEOWNERS) with real, time-weighted expertise, and flags paper owners. - Risk map: bus-factor-1 modules, plus the bridge people the team routes through (betweenness centrality). - Agents that act: a webhook brings in a new issue, and the Steward agent finds similar past issues and the PRs that fixed them, suggests an owner and a reviewer, and drafts a cited triage comment. It posts to GitHub only after a human approves it. - Memory that stays current: when a PR reverses an earlier decision, Lore adds a SUPERSEDES edge. The same question then gets the new answer, with the old decision kept as history. Lore also remembers what it told each user, so it can say what's changed since they last asked. It runs on FalkorDB's own public repository (including the real main-rs history) and on a small synthetic sandbox repo used for the live demo. It scores 10/10 on a hand-written golden set of questions, each checked against the linked PRs. It's built for engineering teams, maintainers of open-source projects, and anyone onboarding into a codebase.

    Titans@yajushivudatha