Getting Started with ContextDx

ContextDx is an Architectural Intelligence Framework that makes system architecture accessible to everyone in your organization. Whether you're a business analyst scoping requirements, a developer inheriting a complex system, or a CTO assessing technical risk—ContextDX provides the architectural context you need in language you understand.

Time to complete: 10 minutes

What you'll learn:

• Core concepts and terminology
• Setting up your first workspace
• Running your first architectural query
• Next steps for your role

---

Core Concepts

Organizational System-Map

Your organization's living architectural knowledge base. Unlike static diagrams, the system-map is queryable, context-aware, and continuously updated. It connects code repositories, infrastructure, documentation, and team ownership into a unified view.

Agents

Context-aware AI assistants that answer architectural questions tailored to your role and expertise level. A business analyst asking "What are the system boundaries for this feature?" receives a different response than a developer asking the same question.

Workboards

Role-specific interfaces for organizing architectural conversations. Each workboard maintains context across sessions, so you can pick up where you left off without re-explaining your project.

MCP Servers

Integrations that connect ContextDx to your existing tools—Git repositories, Jira, Confluence, CI/CD pipelines, monitoring systems, and more. These provide the raw data that powers architectural intelligence.

---

Step 1: Access Your Workspace

After your organization admin has set up ContextDx, you'll receive an invitation email.

1. Click the invitation link
2. Sign in with your organization's SSO
3. Complete your profile by selecting your primary role:
   • Business Analyst
   • Product Manager
   • Developer
   • Platform Engineer
   • Architect
   • Technical Leader / CTO

Your role selection customizes the interface and query responses to match your expertise level and typical questions.

---

Step 2: Explore the System-Map

Once logged in, you'll land on the System-Map Overview. This is your organization's architectural landscape.

What You'll See

Try It

Click on any service to see:

• What it does (plain language description)
• Who owns it
• What depends on it
• Recent changes
• Related documentation

---

Step 3: Run Your First Query

The Query Bar is at the top of every screen. Ask questions in natural language.

Example Queries by Role

Business Analyst:

"What are the system boundaries for the checkout process?"

Product Manager:

"What technical constraints affect the mobile app roadmap?"

Developer:

"What services would be impacted if I change the user authentication API?"

Platform Team:

"What's the blast radius if we upgrade the Kubernetes cluster?"

Architect:

"Show me all services with direct database access that bypass the API layer"

CTO:

"What's our exposure to the legacy payment system?"

Try It

Type this query:

"Give me an overview of the most critical services and their dependencies"

ContextDx will return:

• A prioritized list of critical services
• Key dependencies for each
• Risk factors and ownership
• Links to dive deeper

---

Step 4: Create Your First Workboard

Workboards help you organize ongoing work that requires architectural context.

1. Click + New Workboard in the sidebar
2. Name it (e.g., "Q2 Feature Planning" or "Payment Service Migration")
3. Set the scope—which parts of the system are relevant
4. Add team members who should collaborate

Workboard Features

---

Step 5: Connect Your First Integration

ContextDx becomes more powerful as it connects to your tools.

Quick Integrations (No Admin Required)

To Connect

1. Go to Settings → Integrations
2. Click the integration you want
3. Authorize access
4. Select which repositories/projects to include

Your system-map will automatically update with the new context within a few minutes.

---

What's Next?

Based on your role, we recommend these next steps:

For Business Analysts

→ Understanding System Boundaries Learn how to scope requirements using architectural context.

For Product Managers

→ Technical Constraint Visibility Use ContextDx for roadmap planning and feasibility assessment.

For Developers

→ Impact Analysis Workflows Understand dependencies before making changes.

For Platform Teams

→ Infrastructure Communication Communicate platform decisions and assess change impact.

For Architects

→ Managing the System-Map Configure governance, guardrails, and team enablement.

For CTOs

→ Strategic Architectural Intelligence Connect architecture to business outcomes.

---

Common Questions

How current is the system-map data? Integrations sync continuously. Most changes appear within 5-15 minutes.

Can I query systems I don't have code access to? Yes. ContextDx provides architectural context based on your role permissions, not code repository access.

What if I get an answer I don't understand? Ask follow-up questions. Try: "Explain that in simpler terms" or "What does that mean for [my specific concern]?"

How do I report incorrect information? Click the feedback icon on any response. Your architects will review and update the system-map.

---

Need Help?

• Troubleshooting & FAQ — Common issues and solutions
• Contact Support — We typically respond within 4 hours
• Community Slack — Connect with other ContextDx users

---

Ready to go deeper? Pick your role-specific guide to learn workflows tailored to your daily work.