kernel-audit-trace

Explicit invocation only — do not auto-activate on related context; wait for a direct request.

When to use

• tracing a feature from user interaction through backend and storage
• understanding how a subsystem works end-to-end before changing it
• evaluating boundary flow, dependency flow, or structural risks across multiple layers
• identifying handoff problems, hidden coupling, or misplaced responsibilities in an existing feature

Definition of done

• End-to-end flow traced with concrete file and boundary references
• Structural concerns clarified with file and line references
• Refactoring roadmap produced, ordered by impact

Trace a feature or subsystem from top to bottom, identify where responsibilities and handoffs live, and recommend durable structural changes. Do not implement code.

Mandatory Protocol