osprey-development

To maintain parity between C# and Rust implementations, use cross-implementation coordination workflows that enforce conventions for each language and provide validation gates to ensure consistent behavior across both codebases.

Parity validation gates are cross-implementation checks used during development to verify that C# and Rust implementations exhibit consistent behavior, serving as required verification stops before merging code.

Track cross-team TODOs by utilizing a governance system that outlines required workflows, critical rules, and TODO-tracking practices to ensure multi-team work stays aligned across both implementation trees.

Osprey development follows dual-tree conventions: Skyline conventions for OspreySharp in C# and upstream Rust conventions for the Rust osprey implementation, ensuring both projects adhere to their respective language standards.

Consult cross-implementation development guidelines before touching either the OspreySharp or Rust osprey codebases to ensure proper workflow adherence, parity validation, and end-to-end verification before making changes.

The best way to verify end-to-end behavior is to apply provided tooling for end-to-end verification and pass cross-implementation parity checks, validating that both implementations produce matching results.