[PR #123] [CLOSED] kb: add a Havok SDK-derived knowledge and enforcement record technique note #141

New issue

Closed

opened 2026-10-15 20:53:45 +00:00 by bsakaguchi · 0 comments

bsakaguchi commented

2026-10-15 20:53:45 +00:00

Owner

📋 Pull Request Information

Original PR: https://github.com/rehan-remade/universal-modder/pull/123
Author: @Selene0623
Created: 10/6/2026
Status: ❌ Closed

Base: main ← Head: kb/technique-havok-sdk-derived-knowledge

📝 Commits (2)

0f14f57 kb: add Havok SDK-derived knowledge and enforcement record technique note
acda62f kb: record how artefact-based takedowns actually work in the Havok note

📊 Changes

3 files changed (+165 additions, -1 deletions)

View changed files

📝 knowledge/INDEX.md (+2 -1)
📝 knowledge/index.json (+27 -0)
➕ knowledge/techniques/havok-sdk-derived-knowledge-and-enforcement-record.md (+136 -0)

📄 Description

Adds one technique note: knowledge/techniques/havok-sdk-derived-knowledge-and-enforcement-record.md.

It answers the question raised in #121 — how to write up Havok SDK-derived knowledge without disclosing
the source — from both directions:

What the licence says: Microsoft owns the IP; source other than shipped headers and demo code is
confidential and a trade secret; disclosure and reverse engineering are forbidden outright, with no
interoperability carve-out.
What actually gets enforced: no published takedown or litigation names Havok or Telekinesys anywhere
the notice corpora can be searched; legacy SDK mirrors stay up; Microsoft's own DMCA activity targets game
piracy and derivative clones; the one Havok source incident (2003) was a theft, not enforcement. The live
risk is platform and publisher policy, illustrated by the 2024 H2M C&D.
How to write it up: keep the knowledge and drop the artefact — own-words structure, no pasted code, no
attached headers, no mirror links, no keys, no fetch instructions, plus the reminder that a working-tree
scrub leaves git history and generated deploys intact.

Follows the rule settled in #65: knowledge from leaked SDKs or beta builds is fine in your own words,
including where it came from; the leaked material itself stays out. Checked with um kb check (PASS) and the
test suite (65 passed, 1 skipped), and the index was regenerated with um kb index.

_{🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.}

## 📋 Pull Request Information **Original PR:** https://github.com/rehan-remade/universal-modder/pull/123 **Author:** [@Selene0623](https://github.com/Selene0623) **Created:** 10/6/2026 **Status:** ❌ Closed **Base:** `main` ← **Head:** `kb/technique-havok-sdk-derived-knowledge` --- ### 📝 Commits (2) - [`0f14f57`](https://github.com/rehan-remade/universal-modder/commit/0f14f570c444fb2e1310e53a6b67ade1979cba30) kb: add Havok SDK-derived knowledge and enforcement record technique note - [`acda62f`](https://github.com/rehan-remade/universal-modder/commit/acda62f9e9dba6b3c72d8ca39198fb3f87474b81) kb: record how artefact-based takedowns actually work in the Havok note ### 📊 Changes **3 files changed** (+165 additions, -1 deletions) <details> <summary>View changed files</summary> 📝 `knowledge/INDEX.md` (+2 -1) 📝 `knowledge/index.json` (+27 -0) ➕ `knowledge/techniques/havok-sdk-derived-knowledge-and-enforcement-record.md` (+136 -0) </details> ### 📄 Description Adds one technique note: `knowledge/techniques/havok-sdk-derived-knowledge-and-enforcement-record.md`. It answers the question raised in #121 — how to write up Havok SDK-derived knowledge without disclosing the source — from both directions: - **What the licence says:** Microsoft owns the IP; source other than shipped headers and demo code is confidential and a trade secret; disclosure and reverse engineering are forbidden outright, with no interoperability carve-out. - **What actually gets enforced:** no published takedown or litigation names Havok or Telekinesys anywhere the notice corpora can be searched; legacy SDK mirrors stay up; Microsoft's own DMCA activity targets game piracy and derivative clones; the one Havok source incident (2003) was a theft, not enforcement. The live risk is platform and publisher policy, illustrated by the 2024 H2M C&D. - **How to write it up:** keep the knowledge and drop the artefact — own-words structure, no pasted code, no attached headers, no mirror links, no keys, no fetch instructions, plus the reminder that a working-tree scrub leaves git history and generated deploys intact. Follows the rule settled in #65: knowledge from leaked SDKs or beta builds is fine in your own words, including where it came from; the leaked material itself stays out. Checked with `um kb check` (PASS) and the test suite (`65 passed, 1 skipped`), and the index was regenerated with `um kb index`. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>

bsakaguchi

2026-10-15 20:53:45 +00:00

closed this issue
added the
pull-request
label

No labels

pull-request

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

rehan-remade/universal-modder#141

No description provided.

Rows
Columns