mafia-graph 0.9.0__tar.gz

mafia_graph-0.9.0/.amazonq/rules/mafia-agent.md

@@ -0,0 +1,88 @@
+---
+description: MANDATORY - Use mafia CLI for ALL code questions before any other tool
+globs: "**/*"
+---
+
+# CRITICAL RULE: Use `mafia` CLI FIRST for ALL code questions
+
+This project has a live dependency graph with 343 entities and 1433 relations.
+The `mafia` CLI is installed and initialized. You MUST use it.
+
+## MANDATORY BEHAVIOR
+
+**BEFORE using fileSearch, grep, find, or reading source files to answer ANY question
+about code structure, functions, classes, dependencies, imports, usage, or behavior —
+you MUST first run the appropriate `mafia` command via executeBash.**
+
+This applies to ALL of these question patterns (not just exact matches):
+
+| User asks about... | Run this FIRST |
+|---|---|
+| Any function, class, method, table, endpoint by name | `mafia search "<name>" --limit 10` |
+| "where is X used" / "who uses X" / "who calls X" | `mafia search "<X>"` then `mafia neighbors "<id>" --direction upstream` |
+| "what does X call" / "what does X depend on" | `mafia neighbors "<id>" --direction downstream` |
+| "what breaks if I change X" / "impact of changing X" | `mafia blast "<id>" --direction downstream` |
+| "how does X connect to Y" / "relationship between X and Y" | `mafia path "<X_id>" "<Y_id>"` |
+| "trace the flow" / "end to end" / "full chain" | `mafia trace "<id>" --depth 10` or `mafia flows --node "<id>"` |
+| "show me the flow for X" / "what flows involve X" | `mafia flows --node "<id>"` |
+| "unused code" / "dead code" / "orphans" | `mafia orphans` |
+| "how is the project structured" / "overview" | `mafia status` |
+| "find X" / "locate X" / "where is X defined" | `mafia search "<X>" --limit 10` |
+| "explain how X works" / "what does X do" | `mafia search "<X>"` → get ID → `mafia neighbors "<id>" --direction both` → THEN read source |
+| "list all endpoints" / "list all tables" | `mafia search "endpoint" --limit 50` or search by type |
+| "what changed" / "refresh" | `mafia update` |
+
+## WORKFLOW
+
+1. **Always start with `mafia search`** to find the entity ID
+2. **Use the entity ID** in follow-up commands (neighbors, blast, trace, flows, path)
+3. **Only THEN read source files** if the user needs to see actual code
+
+## DO NOT
+
+- Do NOT use fileSearch/grep to find function definitions when mafia search can find them
+- Do NOT manually read import statements to trace dependencies when mafia neighbors exists
+- Do NOT guess at call chains when mafia trace gives the real graph
+- Do NOT scan files to find usages when mafia neighbors --direction upstream gives them
+
+## Commands (real examples from this project)
+
+```bash
+# Search for any entity (function, class, table, endpoint)
+mafia search "py" --limit 10
+
+# Who calls this (upstream neighbors)
+mafia neighbors "code:module:MAFIA_Phase1_Execution:install.py" --direction upstream
+
+# What this calls (downstream neighbors)
+mafia neighbors "code:module:MAFIA_Phase1_Execution:install.py" --direction downstream
+
+# Full blast radius — what breaks if this changes
+mafia blast "code:module:MAFIA_Phase1_Execution:install.py" --direction downstream
+
+# Trace the downstream call chain
+mafia trace "code:module:MAFIA_Phase1_Execution:install.py" --depth 10
+
+# End-to-end flows through a node
+mafia flows --node "code:module:MAFIA_Phase1_Execution:install.py"
+
+# Shortest path between two entities
+mafia path "code:module:MAFIA_Phase1_Execution:install.py" "api:service:MAFIA_Phase1_Execution:mafia/api.py::MAFIA"
+
+# Dead code candidates
+mafia orphans
+
+# Project graph stats
+mafia status
+
+# Refresh graph after code changes
+mafia update
+```
+
+All commands run from: `C:\Users\MML\Downloads\Graphify-MAFIA\MAFIA_Phase1_Execution`
+
+## Entity ID format
+
+`{layer}:{type}:{repo}:{qualifier}` — e.g. `code:module:MAFIA_Phase1_Execution:install.py`
+
+Layers: ui, bff, api, db, config, shared

mafia_graph-0.9.0/.amazonq/rules/mafia-skills.md

@@ -0,0 +1,69 @@
+---
+description: MAFIA codebase analysis system — skills and capabilities reference
+globs: "**/*"
+---
+
+# MAFIA System Context
+
+This workspace is the MAFIA (Multi-Artifact Flow Intelligence Architecture) codebase analysis pipeline. When working in this project, you have access to these capabilities:
+
+## Quick Reference
+
+- **Scan repos:** `python -m phase2_repo_intake.repo_scanner --source-roots /path`
+- **Run pipeline:** `python -m phase3_extraction_framework.run_extraction` (incremental) or `--full`
+- **Rebuild graph only:** `python -m phase3_extraction_framework.run_extraction --from-phase 9`
+- **AST summaries:** `python -m phase10_ast.run_ast_summaries --discover`
+- **Build search index:** `python -m phase11_search.vector_index --incremental`
+- **Start server:** `python -m phase11_search.search_api1` → http://localhost:5001
+
+## Key Artifacts (all in output/)
+
+- `repo_manifest.json` — discovered repos with classification
+- `entities.jsonl` — all extracted entities (ID format: `layer:type:repo:qualifier`)
+- `relations.jsonl` — all edges between entities
+- `system_graph.json` — full graph (nodes + edges)
+- `e2e_flows.json` — end-to-end flows across catalogs
+- `ast_summaries.jsonl` — method-level structural summaries
+- `coverage_report.json`, `quality_gate_report.json` — health metrics
+
+## Architecture Layers
+
+UI (React) → BFF (Koa/Express) → API (Spring Boot) → DB (Postgres/Databricks)
+
+## When reading/modifying extractors
+
+- All extractors subclass `BaseExtractor` in `phase3_extraction_framework/base_extractor.py`
+- Extractors live in `phase4_extractors/` organized by layer
+- Entity IDs use canonical format: `{layer}:{type}:{repo}:{qualifier}`
+- Relations use: `{source_id}--{type}-->{target_id}`
+- Valid layers/types/relations defined in `schemas/id_format.py`
+- Emission goes through `schemas/emitter.py` (thread-safe, deduplicating)
+
+## When working on the UI
+
+- UI files in `phase12_ui/` — served by Flask at localhost:5001
+- API endpoints defined in `phase11_search/search_api1.py`
+- Key API routes: /search, /node/{id}, /flows, /flow/{id}, /blast_radius, /chat, /coverage
+
+## Agent CLI (for any project)
+
+MAFIA can be initialized on any project to give the agent codebase intelligence:
+
+```bash
+# Initialize on a project (scans, extracts, builds graph)
+python mafia_cli.py init --project-root /path/to/project
+
+# Query from the agent (no server needed)
+python mafia_cli.py search "getUserProfile" --limit 10
+python mafia_cli.py trace "api:endpoint:user_api:GET:/users"
+python mafia_cli.py blast "api:service:user_api:UserService" --direction downstream
+python mafia_cli.py flows --node "bff:endpoint:user_bff:/users"
+python mafia_cli.py neighbors "api:controller:user_api:UserController" --direction both
+python mafia_cli.py path "ui:fetch_def:web:getUsers" "db:table:pg:users"
+python mafia_cli.py orphans
+python mafia_cli.py update  # incremental after code changes
+```
+
+Init creates `.mafia/` in the target project with artifacts + installs agent rules into `.amazonq/rules/mafia-agent.md` and `CLAUDE.md` automatically.
+
+## For full skills reference, see skills.md in the project root.

mafia_graph-0.9.0/.continue/config.json

@@ -0,0 +1,3 @@
+{
+  "systemMessage": "CRITICAL RULE: Use `mafia` CLI FIRST for ALL code questions in this project.\n\nThis project has a live dependency graph (343 entities, 1433 relations). The `mafia` CLI is installed.\n\nBEFORE reading source files or answering questions about structure, dependencies, or behavior — run the appropriate `mafia` command.\n\nCommands (run from C:\\Users\\MML\\Downloads\\Graphify-MAFIA\\MAFIA_Phase1_Execution):\n- mafia search \"<name>\" --limit 10          # find any entity\n- mafia neighbors \"<id>\" --direction upstream   # who calls X\n- mafia neighbors \"<id>\" --direction downstream  # what X calls\n- mafia blast \"<id>\" --direction downstream      # blast radius\n- mafia trace \"<id>\" --depth 10                  # call chain\n- mafia flows --node \"<id>\"                      # e2e flows\n- mafia path \"<X_id>\" \"<Y_id>\"                   # shortest path\n- mafia orphans                                  # dead code\n- mafia status                                   # project overview\n- mafia update                                   # refresh graph\n\nWorkflow: mafia search → get ID → use ID in follow-up commands → read source only if needed.\nEntity ID format: {layer}:{type}:{repo}:{qualifier}"
+}

mafia_graph-0.9.0/.cursor/rules/mafia-agent.mdc

@@ -0,0 +1,60 @@
+---
+description: MANDATORY - Use mafia CLI for ALL code questions before any other tool
+globs: "**/*"
+alwaysApply: true
+---
+
+# CRITICAL RULE: Use `mafia` CLI FIRST for ALL code questions
+
+This project has a live dependency graph with 343 entities and 1433 relations.
+The `mafia` CLI is installed and initialized. You MUST use it.
+
+## MANDATORY BEHAVIOR
+
+**BEFORE using file search, grep, or reading source files to answer ANY question
+about code structure, functions, classes, dependencies, imports, usage, or behavior —
+you MUST first run the appropriate `mafia` command via terminal.**
+
+| User asks about... | Run this FIRST |
+|---|---|
+| Any function, class, method, table, endpoint by name | `mafia search "<name>" --limit 10` |
+| "where is X used" / "who calls X" | `mafia neighbors "<id>" --direction upstream` |
+| "what does X call" / "what does X depend on" | `mafia neighbors "<id>" --direction downstream` |
+| "what breaks if I change X" | `mafia blast "<id>" --direction downstream` |
+| "how does X connect to Y" | `mafia path "<X_id>" "<Y_id>"` |
+| "trace the flow" / "end to end" | `mafia trace "<id>" --depth 10` |
+| "what flows involve X" | `mafia flows --node "<id>"` |
+| "unused code" / "dead code" | `mafia orphans` |
+| "project overview" / "structure" | `mafia status` |
+| "what changed" / "refresh" | `mafia update` |
+
+## WORKFLOW
+
+1. `mafia search "<name>"` → get entity ID
+2. Use ID in follow-up commands (neighbors, blast, trace, flows, path)
+3. Only THEN read source files if user needs actual code
+
+## DO NOT
+
+- Do NOT grep/search files to find function definitions when `mafia search` can find them
+- Do NOT manually trace imports when `mafia neighbors` exists
+- Do NOT guess call chains when `mafia trace` gives the real graph
+
+## Commands
+
+```bash
+mafia search "getUserProfile" --limit 10
+mafia neighbors "code:module:MAFIA_Phase1_Execution:install.py" --direction both
+mafia blast "code:module:MAFIA_Phase1_Execution:install.py" --direction downstream
+mafia trace "code:module:MAFIA_Phase1_Execution:install.py" --depth 10
+mafia flows --node "code:module:MAFIA_Phase1_Execution:install.py"
+mafia path "<source_id>" "<target_id>"
+mafia orphans
+mafia status
+mafia update
+```
+
+All commands run from: `C:\Users\MML\Downloads\Graphify-MAFIA\MAFIA_Phase1_Execution`
+
+Entity ID format: `{layer}:{type}:{repo}:{qualifier}`
+Layers: ui, bff, api, db, config, shared

mafia_graph-0.9.0/.github/copilot-instructions.md

@@ -0,0 +1,34 @@
+# GitHub Copilot Custom Instructions
+
+## CRITICAL: Use `mafia` CLI FIRST for ALL code questions
+
+This project has a live dependency graph (343 entities, 1433 relations). The `mafia` CLI is installed.
+
+**BEFORE suggesting code, searching files, or answering questions about structure, dependencies, or behavior — run the appropriate `mafia` command.**
+
+| Question type | Command |
+|---|---|
+| Find any function/class/endpoint | `mafia search "<name>" --limit 10` |
+| Who calls X / upstream deps | `mafia neighbors "<id>" --direction upstream` |
+| What X calls / downstream deps | `mafia neighbors "<id>" --direction downstream` |
+| Impact of changing X | `mafia blast "<id>" --direction downstream` |
+| Path between X and Y | `mafia path "<X_id>" "<Y_id>"` |
+| Full call chain trace | `mafia trace "<id>" --depth 10` |
+| Flows through X | `mafia flows --node "<id>"` |
+| Dead/unused code | `mafia orphans` |
+| Project overview | `mafia status` |
+| Refresh after changes | `mafia update` |
+
+### Workflow
+1. `mafia search "<name>"` → get entity ID
+2. Use ID in follow-up commands
+3. Only read source files if user needs actual code
+
+### Do NOT
+- Grep or file-search for definitions when `mafia search` works
+- Manually trace imports when `mafia neighbors` exists
+- Guess call chains when `mafia trace` gives the real graph
+
+All commands run from: `C:\Users\MML\Downloads\Graphify-MAFIA\MAFIA_Phase1_Execution`
+
+Entity ID format: `{layer}:{type}:{repo}:{qualifier}` — e.g. `code:module:MAFIA_Phase1_Execution:install.py`

mafia_graph-0.9.0/.kiro/rules/mafia-agent.md

@@ -0,0 +1,88 @@
+---
+description: MANDATORY - Use mafia CLI for ALL code questions before any other tool
+globs: "**/*"
+---
+
+# CRITICAL RULE: Use `mafia` CLI FIRST for ALL code questions
+
+This project has a live dependency graph with 343 entities and 1433 relations.
+The `mafia` CLI is installed and initialized. You MUST use it.
+
+## MANDATORY BEHAVIOR
+
+**BEFORE using fileSearch, grep, find, or reading source files to answer ANY question
+about code structure, functions, classes, dependencies, imports, usage, or behavior —
+you MUST first run the appropriate `mafia` command via executeBash.**
+
+This applies to ALL of these question patterns (not just exact matches):
+
+| User asks about... | Run this FIRST |
+|---|---|
+| Any function, class, method, table, endpoint by name | `mafia search "<name>" --limit 10` |
+| "where is X used" / "who uses X" / "who calls X" | `mafia search "<X>"` then `mafia neighbors "<id>" --direction upstream` |
+| "what does X call" / "what does X depend on" | `mafia neighbors "<id>" --direction downstream` |
+| "what breaks if I change X" / "impact of changing X" | `mafia blast "<id>" --direction downstream` |
+| "how does X connect to Y" / "relationship between X and Y" | `mafia path "<X_id>" "<Y_id>"` |
+| "trace the flow" / "end to end" / "full chain" | `mafia trace "<id>" --depth 10` or `mafia flows --node "<id>"` |
+| "show me the flow for X" / "what flows involve X" | `mafia flows --node "<id>"` |
+| "unused code" / "dead code" / "orphans" | `mafia orphans` |
+| "how is the project structured" / "overview" | `mafia status` |
+| "find X" / "locate X" / "where is X defined" | `mafia search "<X>" --limit 10` |
+| "explain how X works" / "what does X do" | `mafia search "<X>"` → get ID → `mafia neighbors "<id>" --direction both` → THEN read source |
+| "list all endpoints" / "list all tables" | `mafia search "endpoint" --limit 50` or search by type |
+| "what changed" / "refresh" | `mafia update` |
+
+## WORKFLOW
+
+1. **Always start with `mafia search`** to find the entity ID
+2. **Use the entity ID** in follow-up commands (neighbors, blast, trace, flows, path)
+3. **Only THEN read source files** if the user needs to see actual code
+
+## DO NOT
+
+- Do NOT use fileSearch/grep to find function definitions when mafia search can find them
+- Do NOT manually read import statements to trace dependencies when mafia neighbors exists
+- Do NOT guess at call chains when mafia trace gives the real graph
+- Do NOT scan files to find usages when mafia neighbors --direction upstream gives them
+
+## Commands (real examples from this project)
+
+```bash
+# Search for any entity (function, class, table, endpoint)
+mafia search "py" --limit 10
+
+# Who calls this (upstream neighbors)
+mafia neighbors "code:module:MAFIA_Phase1_Execution:install.py" --direction upstream
+
+# What this calls (downstream neighbors)
+mafia neighbors "code:module:MAFIA_Phase1_Execution:install.py" --direction downstream
+
+# Full blast radius — what breaks if this changes
+mafia blast "code:module:MAFIA_Phase1_Execution:install.py" --direction downstream
+
+# Trace the downstream call chain
+mafia trace "code:module:MAFIA_Phase1_Execution:install.py" --depth 10
+
+# End-to-end flows through a node
+mafia flows --node "code:module:MAFIA_Phase1_Execution:install.py"
+
+# Shortest path between two entities
+mafia path "code:module:MAFIA_Phase1_Execution:install.py" "api:service:MAFIA_Phase1_Execution:mafia/api.py::MAFIA"
+
+# Dead code candidates
+mafia orphans
+
+# Project graph stats
+mafia status
+
+# Refresh graph after code changes
+mafia update
+```
+
+All commands run from: `C:\Users\MML\Downloads\Graphify-MAFIA\MAFIA_Phase1_Execution`
+
+## Entity ID format
+
+`{layer}:{type}:{repo}:{qualifier}` — e.g. `code:module:MAFIA_Phase1_Execution:install.py`
+
+Layers: ui, bff, api, db, config, shared

mafia_graph-0.9.0/.kiro/skills.md

@@ -0,0 +1,44 @@
+# MAFIA Skills for Kiro
+
+## First-Time Setup
+```bash
+cd MAFIA_Phase1_Execution
+setup.bat              # creates venv, installs deps, validates
+setup.bat --extras     # + extra language grammars
+# Then activate: .venv\Scripts\activate
+```
+
+## Available Operations
+
+### Analyze Codebase
+- Scan repos: `python -m phase2_repo_intake.repo_scanner --source-roots {paths}`
+- Extract: `python -m phase3_extraction_framework.run_extraction` (add `--full` for full, `--from-phase 9` for graph-only)
+- AST: `python -m phase10_ast.run_ast_summaries --discover`
+
+### Query Data (Python)
+```python
+import json
+# Load entities
+entities = [json.loads(l) for l in open("output/entities.jsonl")]
+# Load graph
+graph = json.load(open("output/system_graph.json"))
+# Load flows
+flows = json.load(open("output/e2e_flows.json"))
+# Filter: entities by layer/type/repo/confidence
+api_eps = [e for e in entities if e["layer"]=="api" and e["type"]=="endpoint"]
+```
+
+### Query Data (HTTP — localhost:5001)
+- Search: `GET /search?q={query}&layer={layer}`
+- Node: `GET /node/{entity_id}`
+- Neighbors: `GET /node/{id}/neighbors?depth=2`
+- Flows: `GET /flows` or `GET /flow/{flow_id}?depth=deep`
+- Blast radius: `POST /blast_radius {"component_id": "...", "direction": "both"}`
+- Code: `GET /code/{entity_id}` or `GET /codefile?id={entity_id}`
+- Chat: `POST /chat {"message": "...", "code_mode": true}`
+
+### Entity ID Format
+`{layer}:{type}:{repo}:{qualifier}` — e.g. `api:endpoint:flags_api:GET:/flagTypes`
+
+### Layers
+ui → bff → api → db (+ config, shared)

mafia_graph-0.9.0/.windsurf/rules/mafia-agent.md

@@ -0,0 +1,64 @@
+---
+description: MANDATORY - Use mafia CLI for ALL code questions before any other tool
+globs: "**/*"
+---
+
+# CRITICAL RULE: Use `mafia` CLI FIRST for ALL code questions
+
+This project has a live dependency graph with 343 entities and 1433 relations.
+The `mafia` CLI is installed and initialized. You MUST use it.
+
+## MANDATORY BEHAVIOR
+
+**BEFORE using fileSearch, grep, find, or reading source files to answer ANY question
+about code structure, functions, classes, dependencies, imports, usage, or behavior —
+you MUST first run the appropriate `mafia` command via executeBash.**
+
+| User asks about... | Run this FIRST |
+|---|---|
+| Any function, class, method, table, endpoint by name | `mafia search "<name>" --limit 10` |
+| "where is X used" / "who uses X" / "who calls X" | `mafia search "<X>"` then `mafia neighbors "<id>" --direction upstream` |
+| "what does X call" / "what does X depend on" | `mafia neighbors "<id>" --direction downstream` |
+| "what breaks if I change X" / "impact of changing X" | `mafia blast "<id>" --direction downstream` |
+| "how does X connect to Y" / "relationship between X and Y" | `mafia path "<X_id>" "<Y_id>"` |
+| "trace the flow" / "end to end" / "full chain" | `mafia trace "<id>" --depth 10` or `mafia flows --node "<id>"` |
+| "show me the flow for X" / "what flows involve X" | `mafia flows --node "<id>"` |
+| "unused code" / "dead code" / "orphans" | `mafia orphans` |
+| "how is the project structured" / "overview" | `mafia status` |
+| "find X" / "locate X" / "where is X defined" | `mafia search "<X>" --limit 10` |
+| "explain how X works" / "what does X do" | `mafia search "<X>"` → get ID → `mafia neighbors "<id>" --direction both` → THEN read source |
+| "list all endpoints" / "list all tables" | `mafia search "endpoint" --limit 50` or search by type |
+| "what changed" / "refresh" | `mafia update` |
+
+## WORKFLOW
+
+1. **Always start with `mafia search`** to find the entity ID
+2. **Use the entity ID** in follow-up commands (neighbors, blast, trace, flows, path)
+3. **Only THEN read source files** if the user needs to see actual code
+
+## DO NOT
+
+- Do NOT use fileSearch/grep to find function definitions when mafia search can find them
+- Do NOT manually read import statements to trace dependencies when mafia neighbors exists
+- Do NOT guess at call chains when mafia trace gives the real graph
+- Do NOT scan files to find usages when mafia neighbors --direction upstream gives them
+
+## Commands
+
+```bash
+mafia search "py" --limit 10
+mafia neighbors "code:module:MAFIA_Phase1_Execution:install.py" --direction upstream
+mafia neighbors "code:module:MAFIA_Phase1_Execution:install.py" --direction downstream
+mafia blast "code:module:MAFIA_Phase1_Execution:install.py" --direction downstream
+mafia trace "code:module:MAFIA_Phase1_Execution:install.py" --depth 10
+mafia flows --node "code:module:MAFIA_Phase1_Execution:install.py"
+mafia path "code:module:MAFIA_Phase1_Execution:install.py" "api:service:MAFIA_Phase1_Execution:mafia/api.py::MAFIA"
+mafia orphans
+mafia status
+mafia update
+```
+
+All commands run from: `C:\Users\MML\Downloads\Graphify-MAFIA\MAFIA_Phase1_Execution`
+
+Entity ID format: `{layer}:{type}:{repo}:{qualifier}` — e.g. `code:module:MAFIA_Phase1_Execution:install.py`
+Layers: ui, bff, api, db, config, shared

mafia_graph-0.9.0/.zed/rules.md

@@ -0,0 +1,27 @@
+# MAFIA Project — Zed AI Rules
+
+## CRITICAL: Use `mafia` CLI FIRST for ALL code questions
+
+This project has a live dependency graph (343 entities, 1433 relations). The `mafia` CLI is installed.
+
+**BEFORE reading source files or answering questions about structure, dependencies, or behavior —
+run the appropriate `mafia` command in the terminal.**
+
+| Question | Command |
+|---|---|
+| Find function/class/endpoint | `mafia search "<name>" --limit 10` |
+| Who calls X | `mafia neighbors "<id>" --direction upstream` |
+| What X calls | `mafia neighbors "<id>" --direction downstream` |
+| Impact of changing X | `mafia blast "<id>" --direction downstream` |
+| Path from X to Y | `mafia path "<X_id>" "<Y_id>"` |
+| Full call chain | `mafia trace "<id>" --depth 10` |
+| Flows through X | `mafia flows --node "<id>"` |
+| Dead code | `mafia orphans` |
+| Project overview | `mafia status` |
+| Refresh after changes | `mafia update` |
+
+Workflow: search → get ID → neighbors/blast/trace → read source only if needed.
+
+All commands run from: `C:\Users\MML\Downloads\Graphify-MAFIA\MAFIA_Phase1_Execution`
+
+Entity ID: `{layer}:{type}:{repo}:{qualifier}` — e.g. `code:module:MAFIA_Phase1_Execution:install.py`

mafia_graph-0.9.0/AGENTS.md

@@ -0,0 +1,72 @@
+# MAFIA — Agent Instructions
+
+## CRITICAL: Use `mafia` CLI FIRST for ALL code questions
+
+This project has a live dependency graph (343 entities, 1433 relations). The `mafia` CLI is installed and initialized.
+
+**BEFORE using grep, find, or reading source files to answer ANY question about code structure,
+functions, classes, dependencies, imports, usage, or behavior — run the appropriate `mafia` command.**
+
+## Command Reference
+
+```bash
+# Find any entity (function, class, table, endpoint)
+mafia search "<name>" --limit 10
+
+# Upstream callers / who uses X
+mafia neighbors "<id>" --direction upstream
+
+# Downstream callees / what X depends on
+mafia neighbors "<id>" --direction downstream
+
+# Full blast radius — what breaks if X changes
+mafia blast "<id>" --direction downstream
+
+# Trace the call chain
+mafia trace "<id>" --depth 10
+
+# End-to-end flows through a node
+mafia flows --node "<id>"
+
+# Shortest path between two entities
+mafia path "<source_id>" "<target_id>"
+
+# Dead code candidates
+mafia orphans
+
+# Project graph stats
+mafia status
+
+# Refresh graph after code changes
+mafia update
+```
+
+All commands run from: `C:\Users\MML\Downloads\Graphify-MAFIA\MAFIA_Phase1_Execution`
+
+## Workflow
+
+1. `mafia search "<name>"` → get entity ID
+2. Use ID in follow-up commands (neighbors, blast, trace, flows, path)
+3. Only read source files if the user needs to see actual code
+
+## Entity ID Format
+
+`{layer}:{type}:{repo}:{qualifier}` — e.g. `code:module:MAFIA_Phase1_Execution:install.py`
+
+Layers: ui, bff, api, db, config, shared
+
+## DO NOT
+
+- Grep/search files for definitions when `mafia search` can find them
+- Manually trace imports when `mafia neighbors` exists
+- Guess call chains when `mafia trace` gives the real graph
+- Scan files for usages when `mafia neighbors --direction upstream` gives them
+
+## Project Overview
+
+```
+UI (React) → BFF (Koa/Express) → API (Spring Boot) → DB (Postgres/Databricks)
+```
+
+Key entry point: `phase3_extraction_framework/run_extraction.py`
+Server: `python -m phase11_search.search_api1` → http://localhost:5001