Negotiate ABI capability before the first compression call
A newer binding calls an option function missing from the loaded native library and the process terminates during symbol resolution.
- Focused work estimate
- 4h + prerequisites
- Priority in the scenario
- High
- Engineering practice
- ABI versioning · Feature negotiation
Estimated field mix
- Systems programming70%
- Platform engineering30%
Field percentages are editorial estimates of the ticket's engineering focus. They total 100%; they are not measured time, proficiency scores, or ownership evidence.
Review it, then add it to your workspace.
The board opens an editable draft; nothing is saved until you confirm it. Sign-in and workspace permissions apply, and Demo boards remain ephemeral.
Project context
A fictional desktop backup tool calls a small Rust compression library from Node.js. The binding leaks buffers on exceptions and treats ABI mismatches as corrupted input. Build against generated byte arrays and a local native library; no production archive format or user files are supplied.
Setup prerequisites
- FFI ownership
- Binary compatibility
- Error handling
Preceding work
Complete these dependencies, or supply their agreed outputs before taking this ticket.
Acceptance criteria
- Initialization reads ABI version and explicit capability bits
- Unsupported required capabilities fail before accepting work
- Optional capabilities have documented fallback behavior
Implementation constraints
- Do not infer ABI compatibility from package version or filename alone.
Verification to include
- Load current and compatible older fixture libraries.
- Load a library missing a required symbol and fail closed before dispatch.
Deliverables
- ABI handshake and compatibility matrix
Rollout and recovery
Probe in startup readiness while the pure-language provider remains selectable.
Value of the work
For the engineer: Practice language-boundary contracts, native resource safety and version negotiation.
For the team: Review a binding that fails safely and can be rolled back before native code enters additional application paths.
Evidence boundaries
Outcome Evidence: Tests, patches, and runbooks are requested deliverables. They become Outcome Evidence only through a qualified Mission and immutable Evidence IDs.
Ownership Evidence: Independent adaptation must be observed under a declared verification policy and cite immutable Evidence IDs. Completing a planning ticket establishes no Ownership Evidence.