cross-repo

Cross-repo coordination uses a canonical bundle file set and LINEAGE trace to enforce bilateral consistency and traceability across repos. It defines a single canonical path for inbound, outbound, bilateral, and operator-pending interactions.

A LINEAGE trace in CDD-based cross-repo development provides end-to-end traceability across two repos during a cycle. It records hat-collapse attribution and defines the lifecycle for bilateral iterations to ensure auditable handoffs.

To prevent state drift between repositories, apply explicit STATUS and LINEAGE rules to bilateral iterations. This canonical schema enforces auditable records and defined archival behavior to avoid synchronization loss across repos.

A canonical STATUS lifecycle is needed for cross-repo proposals when processing inbound proposals and operator-pending bundles. It satisfies protocol edge cases and ensures correct archival behavior for all bilateral interactions.

To start a cross-repo coordination cycle for outbound iteration traces, identify the applicable cross-repo case and populate LINEAGE.md. This initiates the coordination protocol and establishes the required canonical bundle file set.

The cross-repo protocol supports operator-pending bundles with defined archival rules. It applies a unified STATUS and LINEAGE schema across all interaction types to guarantee auditable records and correct archival behavior.