Explain how $ARGUMENTS works in the lifelog system.
- •Find relevant code: Search for the component/feature across the codebase
- •Draw a data flow diagram: Use ASCII art showing how data moves between components
- •Trace the path: Walk through the code step-by-step, referencing specific file:line locations
- •Key types: List the important structs, enums, and traits involved
- •Connection points: Where does this interact with other parts of the system? (gRPC boundaries, DB calls, proto types)
- •Gotchas: What's non-obvious or could trip someone up?
Keep the explanation practical. Reference specific code, not abstractions.