Skip to content

Record release decisions, OpenDota permission, and the revised change rule - #39

Merged
vbabenko97 merged 3 commits into
mainfrom
docs/analyses-approval
Sep 28, 2026
Merged

vbabenko97 merged 3 commits into
mainfrom
docs/analyses-approval

Conversation

@vbabenko97

@vbabenko97 vbabenko97 commented Sep 28, 2026 •

Copy link
Copy Markdown
Owner

Summary

Records the owner's 2026-09-28 release decisions and revises the change rule that applies after verification. Documentation only: every frozen path is unchanged against the verified commit 3b1cb7c.

Commits

  1. Revise the post-verification change rule (1dd155e). The old rule allowed only the receipt and checklist to change after 3b1cb7c, which contradicted the plan's own release-docs step.

    • The new rule lists every top-level tracked path. Frozen: src tests config data reports predictions-from-llms pyproject.toml uv.lock .github LICENSE .gitignore. Documentation that may change: README, CONTRIBUTING, SECURITY, CITATION.cff, the scorecard, and docs/.
    • A local-link check must be re-run and recorded before tagging.
    • The old rule stays in the receipt next to the dated revision. This commit changes nothing else.
  2. Record owner approval of the analyses, version and OpenDota re-post (98df7f4).

  3. Record OpenDota's permission to publish the snapshots (00831e1). howardchung, an odota organization member and the top contributor to odota/core, replied "This sounds fine to me." on Permission to publish historical API snapshots in a public research repository odota/core#2989. The register records the reply with its link, the sender's authority, the materials covered, its conditions (none stated), and the unanswered Valve question. The deadline no longer gates publication. The Valve rules-page captures and the Steam news response move from "Hold" to "Accepted risk" under the owner's publication decision; no Valve permission is claimed.

An adversarial two-lens review of the first two commits raised findings; all are addressed here.

Checks

  • git diff --name-only 3b1cb7c -- src tests config data reports predictions-from-llms pyproject.toml uv.lock .github LICENSE .gitignore is empty.
  • The local-link check over all tracked markdown finds no broken links, apart from the known verbatim external audit.
  • Offline CI runs on this PR.

Merge

Use "Create a merge commit".

The rule recorded after 3b1cb7c allowed only the receipt and the checklist
to change. That contradicted the completion plan's own release-docs step,
which edits release notes and CITATION.cff before the tag.

The revised rule lists every top-level tracked path:
- Frozen, compared against 3b1cb7c: src, tests, config, data, reports,
  predictions-from-llms, pyproject.toml, uv.lock, .github, LICENSE and
  .gitignore.
- Documentation, may change: README.md, CONTRIBUTING.md, SECURITY.md,
  CITATION.cff, mlsd-scorecard-ti26.md and docs/.

Hosted CI must pass on every published or tagged commit. The local-link
check, the only documentation property the receipt attests, is re-run
and recorded before tagging.

This widens what may change, to documentation only. The old rule stays in
the receipt next to the dated revision. This commit changes no other file;
the edits the revision permits follow separately.
Documentation-only edits under the revised change rule (1dd155e). The
frozen paths are unchanged against 3b1cb7c, and the local-link check is
clean.

- data-sources.md: both analyses approved as they are by the owner
  (2026-09-28), as risk acceptance. The register records the provenance
  the owner gave: Google's Gemini app and OpenAI's ChatGPT app, each with
  Deep Research, on personal accounts. The OpenDota inquiry was re-posted
  as odota/core#2989.
- release-checklist.md: v0.1.0 selected, release PR merged as 8cd4184,
  analyses approved, the re-post linked, and the preamble no longer says
  no version is selected.
- README and release notes: provenance wording says what is actually
  unrecorded (prompts and settings) instead of "incomplete".
- Completion plan: 2026-09-28 decisions recorded; the rule change is
  described as a widening; acceptance requires the pre-tag link check.
- Scorecard: a dated status line under the top fix. Grades unchanged.
howardchung, an odota organization member and the top contributor to
odota/core, replied on odota/core#2989 at 2026-09-28T07:52:54Z: "This
sounds fine to me." (verified through the GitHub API).

The data-sources register records the reply with its link, the sender's
authority, the materials it covers (frozen explorer responses including
match and player account IDs, published with credit and removal on
request), its conditions (none stated), and that the question about
Valve's terms went unanswered.

The deadline no longer gates publication. Valve rules-page captures and
the Steam news response move from "Hold" to "Accepted risk" under the
owner's publication decision, with attribution and a takedown route; no
Valve permission is claimed. The checklist states the basis for each
material separately. The scorecard status line and the plan record are
updated.

Documentation only. The frozen paths are unchanged against 3b1cb7c, and
the local-link check is clean.
@vbabenko97 vbabenko97 changed the title Record release decisions and revise the post-verification change rule Record release decisions, OpenDota permission, and the revised change rule Sep 28, 2026
@vbabenko97
vbabenko97 merged commit fc9a35c into main Sep 28, 2026
2 checks passed
@vbabenko97
vbabenko97 deleted the docs/analyses-approval branch September 28, 2026 09:04
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant