Owner: Researcher

Problem

Two active asset/onboarding documents expose a direct personal-account SharePoint/OneDrive source link for the SecMI CIFAR checkpoint bundle. The repository governance asks public and research-facing docs to avoid private or person-bound handoff surfaces; new teammates should use the project asset mirror, upstream paper/repository references, or a documented manual retrieval note instead of a direct account-scoped URL.

Evidence

• docs/assets-and-storage/research-download-current-status.md has an "Official link" block for the SecMI OneDrive bundle and includes the direct account-scoped source URL.
• docs/assets-and-storage/research-download-master-list.md lists GB-WT-01 with a Markdown link whose target is the same account-scoped source URL.
• docs/assets-and-storage/data-and-assets-handoff.md points new machines to GB-WT-01, so this source leaks into the first-wave asset handoff path.

Impact

This does not change any metric or admitted result, but it weakens public surface reliability and teammate handoff quality. It suggests that a public/research-facing asset path depends on a personal account-scoped manual link, and it leaves a private-looking download surface in live docs instead of a stable project asset-mirror or upstream-reference workflow.

Suggested fix

• Replace the direct account-scoped link with portable wording: project asset mirror or upstream SecMI release material, handled manually if access is required.
• Preserve the asset ID, destination path, and the fact that the bundle is already archived locally.
• Do not modify result artifacts, metrics, admitted evidence bundle rows, or experiment scripts.

Responsible Agent

Researcher