How farheenaiml/trace works
TRACE connects GitHub repositories, extracts and indexes decision evidence, then serves repository Q&A and maintainer tools. Its main workflow runs from repository submission through asynchronous ingestion, rationale extraction, graph/vector indexing, and issue triage; engineers then query the indexed evidence through the web app. Separate branches provide repository health trends and weekly briefs. The README documents the backend pipeline and product pages; sampled source confirms some calls, but not all route-to-API wiring, so uncertain links are omitted.
Main entry points: main.py REST API and jobs · graph_store.py Graph and vector indexing · llm.py LLM client · index.tsx Repository connect
Components 18
Web experience
- Repository connect
frontend/src/routes/index.tsx - Repository dashboard
frontend/src/routes/repo.$repoId.index.tsx - Decision recall
frontend/src/routes/repo.$repoId.recall.tsx - Answer display
frontend/src/components/trace/AnswerPanel.tsx - Guardian triage
frontend/src/routes/repo.$repoId.guardian.tsx - Health dashboard
frontend/src/routes/repo.$repoId.health.tsx
API and orchestration
- REST API and jobs
backend/main.py
Decision knowledge pipeline
- Repository ingestion
backend/ingest.py - Rationale extraction
backend/extractor.py - Graph and vector indexing
backend/graph_store.py - LLM client
backend/llm.py
Maintainer intelligence
- Issue triage agent
backend/agent.py - Health metrics
backend/health.py - Weekly brief
backend/brief.py
Other components
- Engineer
- GitHub
- Neo4j graph
- Qdrant vectors
Connections 23
- Engineer → Repository connect: connects repository
frontend/src/routes/index.tsx - Repository connect → REST API and jobs: submits repository
frontend/src/routes/index.tsx - REST API and jobs → Repository ingestion: schedules ingestion
README.md - Repository ingestion → GitHub: fetches repository data
README.md - REST API and jobs → Rationale extraction: runs extraction
README.md - REST API and jobs → Graph and vector indexing: loads indexes
README.md - Graph and vector indexing → Neo4j graph: writes graph
README.md - Graph and vector indexing → Qdrant vectors: writes vectors
README.md - REST API and jobs → Issue triage agent: runs triage
README.md - REST API and jobs → LLM client: calls client
backend/main.py - Issue triage agent → LLM client: requests scoring
backend/agent.py - Weekly brief → LLM client: requests summary
backend/brief.py - Engineer → Repository dashboard: opens repository
README.md - Engineer → Decision recall: asks decision question
README.md - Decision recall → REST API and jobs: requests evidence answer
README.md - REST API and jobs → Graph and vector indexing: queries indexed evidence
backend/main.py - REST API and jobs → LLM client: synthesizes answer
backend/main.py - REST API and jobs → Answer display: returns grounded answer
README.md - Engineer → Guardian triage: reviews triage
README.md - Guardian triage → REST API and jobs: requests scan status
frontend/src/routes/repo.$repoId.guardian.tsx - Engineer → Health dashboard: views health
README.md - REST API and jobs → Health metrics: serves health metrics
README.md - REST API and jobs → Weekly brief: generates weekly brief
README.md