Research report · 24 October 2026
Four active source links: one tag alignment
The four cards still describe conditional, untested routes. The emails card cited tagged 2.1.4 but linked to mutable main; its primary link now points to the inspected v2.11.37 file. The other three selected-file links remain as labeled.
Selected-file check
| Card | Observed selected file | Link decision |
|---|---|---|
| Copywriting | Connector returned version 2.3.1 and blob SHA-1 e70bd2e1f4e96cb94ef69b3899150950b0128be5. The web broker showed 2.3.1, crawled today. | Retain labeled mutable link. The 16 October 2.3.1 observation is not a latest path pin. |
| Content Strategy | Connector returned source-declared version 1.0 and blob SHA-1 9ba65a2e2857a6fc825f35eb93a9b0ddc20a088a. Broker page was crawled two weeks earlier. | Retain mutable selected-file link; version 1.0 does not establish an immutable revision. |
| Competitor Discovery | Connector returned source-declared version 1.0 and blob SHA-1 0d2124d008b8498be059c56d34d3fd45ecfae798. Broker page was crawled two weeks earlier. | Retain mutable selected-file link; selected-file pin and full inventory remain open. |
emails, v2.11.37 | Connector resolved both tag and main to source-declared 2.1.4 and blob SHA-1 e660baf4adf7430ff90bfbdeaf9a9ad101a2d2ed in this check. | Use the tag for the primary 2.1.4 citation. Equal selected-file blobs at check time do not stabilize main. |
What the check cannot establish
The connector resolved original-repository files, but did not provide browser HTTP status, redirects, response headers, commit dates or cache policy. The web broker returned a cache miss for tagged email page and raw variants; that is a broker access failure, not proof of a missing GitHub path. A direct HTTPS check failed at DNS resolution before an HTTP response. These channels do not independently prove a fresh browser origin response.
Blob SHA-1 values identify selected-file content returned by the connector, not latest path-modification dates, release-archive SHA-256s or full installed packages. This was not a text-delta, directory, host, security or marketing-outcome test. Superamped provenance and inventory, Core Haines mutable-file freshness and package contents, effective host permissions and local-context access remain open. No external action is authorized by a source link.
Research library · Tagged email comparison · Copywriting selected-file comparison · Content Strategy boundary · Competitor Discovery boundary