todo2code

Ticket 005: Audited cross-language reranking

Goal and scope

Evaluate a two-stage cross-language linking path: semantic retrieval may create only a bounded candidate list, while a separate structured reranker must cite repository-owned evidence and may abstain. Retain a production change only when it closes the six current cross-language gold gaps, preserves every forbidden pair and improves coverage on an additional tracked repository.

Executable implementation belongs in src/ and regression coverage in test/. Optional experiment reproducers belong in scripts/research/. This ticket directory is limited to governance, inputs, captured outputs, decisions and logs.

The approved continuation adds a prerequisite communication audit: verify that the governance-standard user-* and ai-* files are converted into distinct human/agent Intent DSL records, compare their intent, and identify the participant who must respond when scope, polarity or coverage diverges.

Acceptance criteria

Non-goals

Participants

Evidence

Approval

Conclusion

The communication prerequisite is retained. Governance user-* and ai-* sections become distinct human/agent Intent DSL records, and each detected divergence names the role and participant who must respond.

The semantic production candidate is rejected. Captured gold decisions satisfy 6/6 expected cross-language pairs with zero forbidden pairs, but three live OpenRouter attempts on the clean tracked subactor/platform snapshot failed the structured contract before any relation could be materialized. The provider first omitted decisions, then returned judgments, and finally returned an invalid non-numeric confidence. Consequently AC-06 and AC-07 were not demonstrated. The deterministic linker remains unchanged, and the experimental reranker is not exported from the package, CLI, MCP or A2A.