Understand the software you own
1ADK vs IcePanel
1ADK helps you check how well your architecture model matches the implementation: explore components, trace connections, and see what changed after the team’s work.
Explore the components and connections found during analysis.Check the source reference behind a finding about a component.See new components and connections when comparing analyses.
Understand what’s behind the architecture diagram.
As an owner, you need more than a view of the system. You need a way to check your developer’s explanation. 1ADK turns analysis findings into a map with supporting references, open questions, and history. Architecture discussions start with specific findings from your project.
01
What you gain with 1ADK
Check the evidence behind an explanation
A finding points to where the agent found support for it—for example, the file that defines a call to a payment service. A developer with repository access can check that reference.
See changes that a UI demo can’t show
Compare two analyses to see whether a payment worker appeared, a queue connection changed, or a previously unclear detail was established. You can review work that never appears on screen.
Keep open questions on the agenda
If retry behavior is still unclear, the question stays with the project. You don’t have to reconstruct it from messages or remember who offered to investigate.
02
Turn the map into a useful conversation
Example
Payment processing changed, but the screens didn’t
Suppose the team moved payment processing into background jobs. The owner wants to understand what was delivered, even though the interface looks the same.
What 1ADK shows
The comparison shows a new queue, a payment worker, and their connections. The finding about retries points to its source in the project. If the retry limit hasn’t been established, it remains an open question.
You can bring a specific question to the review: “The queue is in place. What happens after the last failed attempt, and where has that been checked?”
03
What changes in your workflow
| Task | 1ADK | IcePanel |
|---|---|---|
| Where the picture comes from | Your coding agent examines the project; 1ADK connects the findings into a map and inventories. | The team maintains a shared C4 model manually or through integrations. |
| Checking a finding | Review its supporting reference and confirmation status. | Context and accuracy depend on how the model is populated and reviewed. |
| What history shows | Differences between analyses: system changes and newly established information. | Changes to the shared model and its versions. |
| What the owner gets | A map, supporting evidence, and questions for a concrete discussion with the team. | Architecture views and interaction flows for discussion. |
04
Using 1ADK and IcePanel together
If your team maintains its architecture in IcePanel, use 1ADK findings when updating the model. IcePanel helps present the system and plan changes; 1ADK keeps the implementation findings, evidence, and questions. Moving information between the tools is a separate team task.
Questions about using 1ADK
It connects architecture discussions to findings from your project. Owners can see the evidence behind a conclusion, what remains unclear, and what changed in the next analysis.
Yes, including through MCP, which connects external tools to an agent. 1ADK’s focus is organizing the result for the owner: findings, evidence, open questions, and analysis comparisons in one project.
No. Your agent reads the code in your environment. 1ADK receives a structured description and source references, not source files or repository access.
Product names and trademarks belong to their owners. 1ADK is not affiliated with these companies.
Find out what’s in your project.
The first analysis and one update are free. Your coding agent examines the project; 1ADK receives a structured description, not source files. Explore the map, check the evidence, and compare results.
No repository access. No source-code upload. No card.