Borrowed rank-one adapters: 674 → 666 scalar allowance with no extra fields

research/borrowed-rankone/.gitattributes

@@ -0,0 +1 @@
+* -text

research/borrowed-rankone/ATTRIBUTION.md

@@ -0,0 +1,13 @@
+# Predecessors and overlap
+
+Immediate predecessor [#4499](https://github.com/CrocSwap/integer-mult-bounds/pull/4499), Dugongue, head fd18b37415986d818f643d74a69a2148374bead4, supplies the exact power-of-two gauge code, gauge proof, four selectors, 686 / 674 comparisons, source authentication and symbolic executor adapted here. [#4494](https://github.com/CrocSwap/integer-mult-bounds/pull/4494), head ad31d9fdf000d4ca98dd911afe489a45d2ea4f74, supplies the arbitrary-rank dyadic compiler and 698 comparison; [#4489](https://github.com/CrocSwap/integer-mult-bounds/pull/4489), head 67d1ded63edc604b3d9e6506a4f5d3689bdc9f41, supplies the owned rank-one shared sum. Their notices and Apache-2.0 license are retained. The new specialization is borrowed source/target conjugation, a sufficient cost-saving theorem, and the 666 zero-extra-field source-bound replacement. Reversible uncomputation and transvection conjugation are classical; no literature priority claim is made.
+
+The native cleanup windows and scalar pricing come from zxv's retained compiler lineage at canonical main 2a13eb1827784206202db90e5dc8327cf8a250db. Preserve the full source contributors and notices. Credit Jacob Alan Sussman's mixed-target compiler and Cinna Davis's padding, query-thinning, retiming and joint-boundary work in #4359, #4416, #4440, #4441, #4447 and #4470. This package does not replace those contributions or reprice their recursive calls.
+
+Current main AGENTS.md, autoresearch.md, CONTRIBUTING.md, priority revision 7, selected record and family expansion guidance were read. This session follows #4499's compiler continuation as a scoped local resource improvement, not a complete family expansion or κ-oriented scalar search. Public PR title/body pagination covered 352 open PRs at 2026-10-22T02:19:37Z. Terms borrowed / rank-one / dirty / conjugation yielded broad neighbors, including #3906 (Q8 dirty spectator audit), #1931 (E8 source reflection) and #4017 (finite Gaussian-lattice dirty scratch implementation). Those address different operators and implementation obligations; their dirty-state work is relevant precedent, not duplicated as a new general concept here. No full diff audit of those neighbors is claimed. Discussion API retrieval was rate-limited; visible handoff browsing and local note coverage were incomplete. The cached local search covered only 4 notes out of a 5,731-path HEAD inventory. Unknown coverage is not novelty evidence.
+
+MathProof source discovery inspected WeightedTIStabilizerShears20260906.lean for explicit transvections and invertible transport, and Problem18P34Subfield20261003NRecursiveWorkspaceRestore.lean for exact counted restoration of arbitrary saved memory and protected names. IntegerKappaBorrowFactors20261014.lean and IntegerKappaBorrowFeedback20261014.lean concern Gaussian factor order and numerical feedback, respectively; they do not prove the adapter here. The inherited rank-one/finite-sum precedents Meta/TITensorRank20260902.lean and Abstraction/VPVNPFixedGateVisiblePricing20260826.lean remain credited. These are source-level discovery references, not freshly audited Lean dependencies; no full-DAG search or new kernel check is claimed. The authoritative DAG and compiled modules remain unchanged.
+
+A bounded alternative was tried first: exact gauges inside the predecessor's fixed rank factors gave 366, 46, 46, 240, with no improvement. This was a fixed-factor observation, not a general barrier. The constructive route then changed to borrowed persistent fields. Prepared for Dugongue with substantial OpenAI assistance in mathematics, implementation and verification; no independent human review or Lean formalization is claimed.
+
+Submission checkpoint: canonical main was fetched again and remained at the pinned base. The public #4499 head was rechecked as fd18b37415986d818f643d74a69a2148374bead4. GitHub write authentication still returns HTTP 401 here; no device login, public Discussion post, push or PR creation was attempted by this worker.