DecisionGraph FAQs

Question 1

How does DecisionGraph prevent risky code changes?

Accepted Answer

It enforces pre-change guardrails via CLI or API. Before a risky refactor or change, DecisionGraph can analyze the proposed modification against existing decisions and assumptions, automatically detecting contradictions or stale logic to prevent costly errors.

Question 2

What is DecisionGraph and how does it help teams?

Accepted Answer

DecisionGraph is an engineering decision memory system that captures and traces *why* changes were made, supported by evidence from various sources. It helps teams move fast without repeating old mistakes by preserving architectural decisions and their reasoning.

Question 3

What kind of data can DecisionGraph ingest?

Accepted Answer

DecisionGraph is highly versatile, ingesting evidence from diverse sources like GitHub PRs/Issues, Slack exports, Jira exports, Git commit history, local files/directories, and generic JSONL event streams. This creates a comprehensive decision knowledge base.

Question 4

Can I integrate DecisionGraph into my existing development workflow?

Accepted Answer

Absolutely. DecisionGraph provides a comprehensive CLI for interactive terminal use, a robust HTTP API for programmatic access, and an MCP (Multi-Channel Protocol) server, making it highly adaptable for integration into CI/CD pipelines and developer tooling.

Question 5

What kind of 'why' questions can DecisionGraph answer?

Accepted Answer

DecisionGraph intelligently queries its decision memory to answer 'why,' 'who,' 'when,' and 'what-changed' questions about your codebase and project history. This provides immediate context for past decisions and their impact.

DecisionGraph

DecisionGraph

主要功能

使用案例

主要功能

使用案例