Docs: architecture diagrams

[jeremyeder]

We need diagrams for the ACP architecture. Use mermaid format and create a GHA so they are updated and linted before a release can be cut. Then add an architecture section to the documentation at a top level. Each architecture diagram (suggest the most useful few) gets its own sub-page and gets a paragraph of content describing what we are looking at. only document things relevant to someone trying to understand ACP itself, for example for extending it or debugging it. keep it tight.

fyi @nsingla

[jeremyeder]

@amber take a crack at this.

[github-actions]

Amber Change Summary

The following files were modified:

 docs/diagrams/architecture.md | 607 ++++++++++++++++++++++++++++++++++++++++++
 docs/index.md                 |   2 +
 mkdocs.yml                    |   3 +
 3 files changed, 612 insertions(+)

Next Steps:

• Review that changes match the issue description
• Verify no scope creep or unintended modifications
• A PR will be created shortly for formal review

---

🔍 View AI decision process (logs available for 90 days)

[github-actions]

🤖 Amber has created a pull request to address this issue: #438

The changes are ready for review. All automated checks will run on the PR.

---

🔍 View AI decision process (logs available for 90 days)

[nsingla]

Thanks @jeremyeder Amber has done a really good job

[jeremyeder]

Thanks @jeremyeder Amber has done a really good job

haha yeah its not bad and I can't find anything technically wrong. I am just making it black and white and then I'll add a lnk to the docs.

[jeremyeder]

@amber where is the GHA to keep this thing in sync with each release? Change mermaid theme to neutral. I can't read the text on the colored boxes.

[github-actions]

⚠️ Amber encountered an error while processing this issue.

Action Type: execute-proposal
Workflow Run: https://github.com/ambient-code/platform/actions/runs/19943886265

Please review the workflow logs for details. You may need to:

1. Check if the issue description provides sufficient context
2. Verify the specified files exist
3. Ensure the changes are feasible for automation

Manual intervention may be required for complex changes.