Architecture reviews in Slack
Turn a design review into a shared Mermaid diagram, review proposed edits, and keep the source message behind the accepted version.
Review the failure path while everyone can see the same diagram
In a checkout review, an engineer asks what happens when payment succeeds but fulfillment fails. Keep the question, the proposed queue and the accepted revision connected instead of posting another unexplained export.
1Establish the review scope
Supply the components you want to review
@Arialine map checkout: API, payment processor and fulfillment worker
The result is a board with Mermaid source and published diagram files. Confirm the components and relationships before discussing changes.
2Make the change explicit
Turn a review decision into an addressed request
@Arialine add a retry queue before the worker because fulfillment may fail after payment succeeds
Ordinary replies remain discussion. In proposal mode, inspect the proposal and apply it only after review.
See what the accepted change adds
Toggle between the diagram as reviewed and the version the proposal would publish. In the app, Edit proposal adjusts the plain-language request; applying it posts this new version to the thread.
Review question: does the queue make the failed-fulfillment path clear, and have you defined the retry and exhaustion behavior elsewhere? A plausible diagram is not a complete reliability design.

Finish with an accepted reference
- Check the plain-language proposal against the intended design.
- Apply the accepted change, or edit/dismiss the proposal; then verify the generated diagram and Mermaid.
- Revisit the resulting version and the source request behind it.
- Record formal alternatives, consequences and ownership in your ADR or design document.
Arialine does not inspect your repository or discover deployed architecture automatically. Supply the relevant design context and retain your normal review controls.
Take the next step
Try one real team workflow
Install in an approved workspace, invite Arialine to the channel, create a small board and review one addressed revision.
