Last updated April 21, 2026
For Architects
You're the one holding the map. Whether you've inherited a tangled legacy landscape or you're steering a greenfield migration, ContextDX gives you a living workspace to capture what exists, govern how it evolves, and share that understanding across the organization — without it going stale in a wiki nobody reads.
Your First Week Checklist
Get up and running fast. Hit these milestones in your first few days:
- Create your workspace and invite your team
- Set up the Master Board (the root-level board every workspace has — it represents your whole system landscape) with top-level domains
- Create at least two child boards for key bounded contexts
- Define archetypes for your node types (service, database, queue, etc.)
- Bind at least one governing source (GitHub repo or Confluence space) per board
- Run your first insight analysis from the Insights Bar
- Publish a board for stakeholder review
Core Architect Workflows
Map Your System End-to-End
Start with the Master Board — your single source of truth for the entire system landscape. Create boards for each bounded context, service cluster, or domain, then organize them into folders and layers so the hierarchy mirrors how your architecture actually works, not how some org chart says it should.
Use layers to separate concerns — infrastructure on one layer, domain models on another. Stakeholders only see what matters to them.
Connect Sources for Truth Reconciliation
Bind GitHub repos, Confluence spaces, Jira projects, and web URLs as sources on your boards. Set them as governing (authoritative) or reference (supplementary) so chat knows which truth wins when sources conflict. This is where ContextDX stops being a drawing tool and starts being an intelligence platform.
Attach at least two sources per board — that's where reconciliation gets interesting. One source is documentation; two sources is insight.