What is ArchDocs?
ArchDocs is a shared workspace for software architecture, design documents, decisions and implementation records. It is aimed at engineering teams, including tech leads, architects, platform groups and engineers working with coding agents, who want people and agents to use the same plan and review what the work supports. Teams can map systems, develop changes, then compare documented plans with recorded work and evidence.
ArchDocs Features:
Shared Architecture Diagrams: Create diagrams from reusable service, queue, database and API objects, and see which docs and components may be affected by a change.
Design Documents: Develop a change in a document that brings its specification, implementation plan and open questions together.
Decision Records: Record the options considered, the reasons behind a choice and later amendments to the design.
MCP Agent Workflow: Coding agents can access architecture, plans and open questions over MCP, while task context and work handoffs are available on Team and higher plans.
AI Document Review: An AI reviewer checks a design document against other docs and code, with findings that can be posted as comments.
Plan And Evidence: Compare planned work with recorded changes, track acceptance criteria against evidence, and review GitHub pull request and check results on Business and Enterprise.
ArchDocs Benefits:
Session Continuity: Shared records help teams carry decisions and discoveries between people and agent sessions instead of rebuilding context from scratch.
Change Visibility: Seeing dependencies across diagrams and docs gives reviewers a clearer view of the potential reach of a proposed change.
Tradeoff Clarity: Keeping the reasoning behind choices alongside the design makes past tradeoffs easier to revisit as requirements or contributors change.
Work Gaps: Comparing plans with recorded work can reveal changes that were not planned and planned tasks without a recorded counterpart.
Evidence-Based Review: Tying acceptance criteria to evidence gives teams a more grounded way to assess whether a change meets its stated requirements.
Use Cases:
Cross-Service Reviews: Tech leads and architects can review a proposed change across services and inspect the affected components and documentation before work proceeds.
Infrastructure Migrations: Platform teams can coordinate a migration by mapping the system, documenting planned work and tracking its acceptance criteria.
Agent-Assisted Work: Engineers using coding agents can share a plan with an agent, pass along task context and leave a handoff for the next session.
First Engineering Changes: New team members can consult architecture, decisions and recorded work to understand the context for their first change.
System Design Interviews: Hiring teams can use ArchDocs to run and debrief system design interviews.