Domain · Use cases · Knowledge graph

A living constellation
of your domain knowledge.

Decision Atlas maps every domain into use cases, every use case into artifacts — BRDs, stories, code, transactional data, incidents — each with its own graph. Query Assist runs across all of them and returns one answer.

Live · 4 domains · 38 use cases · 11.2K entities mapped
The model

From domains to a single graph.

Decision Atlas organizes knowledge in three nested rings — each level enriches the next, and every link survives as a queryable edge in the final graph.

01 · DOMAIN

A bounded business area

Onboarding, lending, claims, risk — anything with its own vocabulary, stakeholders and stories. Each domain is a tenant in the graph.

02 · USE CASES

Workflows that live inside

Each domain holds many use cases — onboard SME, approve loan, detect anomaly. They define the artifacts you'll need to capture.

03 · ARTIFACTS → KG

A graph per artifact

Each artifact — BRD, story, code, transactional data, incident — builds its own knowledge graph. Entities, relationships and provenance, all queryable.

04 · QUERY LAYER

One question. Every graph.

Knowledge Assist routes a natural-language question across every artifact graph in the domain — incidents, code, stories, BRDs — and returns one unified answer.

Five artifacts

Every signal becomes a node.

Decision Atlas builds a dedicated knowledge graph for every artifact a use case produces. Query Assist runs across all of them — every artifact, every use case, the whole domain — and returns one answer.

BRDs

Business requirements parsed into intent, scope, actors and acceptance criteria.

Document
Stories

User stories generated from BRDs — split, linked to acceptance criteria and tickets.

Generated
Code

Repos ingested via ZIP or GitHub. Modules, functions and dependencies become nodes.

ZIP · GitHub
Transactional

Database schemas and live transactions feed the graph with real-world cardinality.

DB · Stream
Incidents

Post-mortems and on-call logs are linked back to the code and stories they touched.

Log · PIR
Live knowledge graph

Query it like a map. Read it like a constellation.

Every artifact contributes nodes and edges. Hover, query, drill — the graph is what your domain actually looks like under the hood.

lending / approve-loan
128 nodes · 412 edges
EntityProcessDataRuleActor
Structural hierarchy
Domain

Top-level business area

Lending
Sub-domain

Bounded context within a domain

Loan Origination
Use case

End-to-end workflow where artifacts bind

Approve Loan
BRDStoriesCodeDBIncidents
Workflow

Four moves. One graph.

From an empty domain to a queryable knowledge graph in minutes.

01

Define your domain

Spin up a tenant for lending, claims, onboarding — whatever the bounded context is.

02

Add use cases

Approve loan, onboard SME, detect anomaly — each becomes a leaf in the graph.

03

Ingest artifacts

Drop BRDs, push code, point at a DB. Decision Atlas parses and links them automatically.

04

Query the constellation

Ask in natural language. Trace impact, surface gaps, generate new artifacts on demand.

Map your first domain.

Start with a use case, ingest one artifact, and watch the graph form in real time.