Skip to content

carve: force-replace both carved repo mains at the cut #549

Description

@mfw78

Decision recorded 2026-07-22, before the M5 carve. Raised by a train planning pass and independently by review of #520.

The two already-populated carve targets have diverged from shepherd and from each other:

Decision

The real carve force-replaces both mains. The tracing refactor and the dependabot work currently on those repos are not back-ported into shepherd, and are discarded when the carve overwrites nexum-runtime/main and videre-nexum-module/main from the shepherd extraction.

Recorded so this is a deliberate choice rather than a three-way reconciliation discovered at carve time.

Consequences to honour at carve time

  • Do not attempt to merge or rebase the existing carved-repo history; the carve is an overwrite.
  • Close the 12 open dependabot PRs on those repos as superseded rather than merging them first.
  • Anything genuinely wanted from the tracing refactor must be re-authored in shepherd before the carve base is cut. Nothing is currently identified as wanted; raise it here if that changes.
  • Fixes landing in shepherd (such as runtime: make the module event type extensible via a generic custom channel #520's) reach those repos only via the carve, not by propagation.

Acceptance criteria

  • The carve runbook states the overwrite explicitly.
  • The dependabot PRs on both carved repos are closed as superseded at carve time.

Metadata

Metadata

Assignees

No one assigned

    Labels

    component/toolsload-gen, orderbook-mock, backtest, baseline-latency, packaging/releasedebtCode works but makes future work harder.effort/hoursFew hours. Single PR.p2-annoyingNot broken, but annoying enough to matter.

    Type

    No type

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions