boettiger-lab-stack

Cross-repo issue routing directs debugging tasks to the owning repository by consulting a stack map. This skill traces data-flow ownership across the data pipeline, enforcing per-repo ownership documentation to clarify which repository needs the fix.

A stack map for cross-repo debugging visualizes per-repo ownership and data-flow across the entire stack. It serves as a single source of truth for pipeline governance, helping teams determine which repository to edit when diagnosing cross-repo issues across data workflows.

Route issues across the data, STAC, and LLM-agent pipeline by checking the stack map for upstream ownership. This guides cross-repo debugging by mapping clear data-flow layers from raw data to LLM agents and identifying the responsible repository for fixes.

Yes, you can use the stack map to find where to implement fixes for data workflow issues. It provides guidance on the responsible repository and directs you to the upstream owner where the code changes need to be applied across the stack.

Cross-repo issue routing relies on per-repo ownership documentation to function correctly. The stack map enforces this documentation as a single source of truth, ensuring accurate data-flow mapping and responsible repository identification across the pipeline.