project-structure

To navigate an eBPF agent codebase, map repository structure and development workflows to reduce uncertainty. This identifies impacted backend, frontend, and protocol files along with required cross-layer synchronization checks before editing.

Adding an event field to an agent observability backend requires modifying impacted files across backend, eBPF, protocol, and frontend layers. Use file selection guidance to identify these specific components and execute required validation workflows.

Yes, repository navigation guidance applies to frontend and wrapper integrations in agent development. It maps these architectural layers to the right references, providing cross-component synchronization requirements and validation strategies for safe implementations.

The best way to ensure safe codebase analysis when modifying agent-ebpf-filter security controls is applying layered reference mapping. This provides validation workflow requirements and file selection rules to verify changes across security and documentation areas.

Cross-component synchronization checks are needed for agent development tasks because changes to eBPF filters, protocols, or APIs impact multiple layers. These checks provide validation strategies to implement modifications safely across the entire repository architecture.