Established in scope
Atlas detail retrieval recovers existing D4 solution after content ranking repair
In the question: Automated construction of operator maps and sources
Retrieval software repair, not a new theory proof or direct graph edit. Existing old MCP processes do not hot-reload; fresh isolated connection was actually verified without stopping other clients. No full server-suite claim. Until normal reconnect, use exact IDs or the existing fresh stdio path rather than interpreting missed retrieval as scientific openness.
Read the exact result, assumptions and evidence
Result
The actual natural D4 request reached the correct large problem, but full-JSON detail ranking let source metadata hide the existing solution. The small existing Rust retrieval now prioritizes semantic coverage and result text while preserving exact IDs and metadata fallback; bilingual tokens and continuation packing were repaired. Three regressions and all19 research-module tests pass. A fresh actual run.sh mcp request retrieves the existing D4 repair first with seven sources and within budget at the same data revision.
Required assumptions
- Do not identify source types
Observable algebra, OS reflection, state, collar operator, time evolution, carrier connection, family holonomy, and readout are distinct data until an original map relates them.
Original evidence
- ATLAS-D4-RETRIEVAL-REPAIR.txt lines 1–87
Source checked at this snapshot
Original location and fingerprint
experiments/theory-contracts/tfpt-unified-source-derivation-20261029/aps_source_review/ATLAS-D4-RETRIEVAL-REPAIR.txt
9e6e12ab493168fe77df58604d02e1b5900f7bc085fde98e65b9e0204d579bdb
finding:atlas-detail-retrieval-recovers-existing-d4-solution