- Record the commit and workspace version.
- Read
Cargo.toml, workspace members, and default features.
- Find the façade crate, binaries, and public entry points.
- Identify external boundaries: network, filesystem, database, or operating
system.
- Choose one representative public operation.
- Follow construction separately from execution.
- Record important state transitions and ownership changes.
- Identify every
.await, blocking call, spawned task, and channel boundary.
- Translate generic bounds into capabilities and relationships.
- List important associated types.
- Distinguish static dispatch from trait objects.
- Find the concrete implementations behind generic calls.
- Trace one application error and one infrastructure error.
- Find cancellation and drop behavior.
- Determine how resources become reusable.
- Identify retries and the conditions under which they are safe.
- Check examples and tests that exercise the path.
- Confirm diagrams name source files or symbols.
- Mark interpretations that are not directly established by code.
- Recheck the map after implementation changes.