# A diagram walkthrough for a new engineer

Goal: explain one real system flow and identify the recorded reason for one non-obvious component.

## Buddy preparation

- Choose one checked, current diagram at a useful level of detail.
- Confirm the new teammate can access the board, relevant source discussion and formal design record.
- Identify the diagram owner and an appropriate correction/review process.
- Keep unknown or outdated relationships visible instead of inventing explanations.

## Walkthrough

1. Ask the teammate to trace the happy path in their own words.
2. Ask: "Which component surprised you, and why do you think it exists?"
3. Inspect the retained change and source message behind that component.
4. Read the formal design record for tradeoffs, consequences and ownership.
5. Find one unclear label or stale relationship together.
6. Request and review a correction. Keep the accepted version accessible.

## Prompts to adapt

```text
@Arialine why is the retry queue here?
@Arialine label the fulfillment worker's owner as the checkout team
```

Review the answer against available recorded context. Arialine does not scan your repository or recover unrecorded reasoning. Addressed edits may apply directly or require proposal review, depending on channel policy.

## Follow-up

| Question still unanswered | Source / person to consult | Owner |
| ------------------------- | -------------------------- | ----- |
|                           |                            |       |

Workflow: https://arialine.app/use-cases/engineering-onboarding
Decision context: https://arialine.app/use-cases/architecture-decision-records-in-slack