Update process documentation to refer to TC57

This updates our process documentation to properly separate the concerns
between the work we will do here going forward and the work that is
ongoing in Ecma TC57. It will still be some time before we'll want to
remove specification langauge from this repository, but this at least
gets our process docs updated.

Author: llvm-beanz

.github/ISSUE_TEMPLATE/agenda_item.md

@@ -28,14 +28,6 @@ This project has adopted the [Microsoft Open Source Code of Conduct](https://ope
 For more information see the [Code of Conduct FAQ](https://opensource.microsoft.com/codeofconduct/faq/) or
 contact [opencode@microsoft.com](mailto:opencode@microsoft.com) with any additional questions or comments.
 
-## Public Design Meeting
-
-The HLSL team organizes a meeting every two weeks which is open to the public to discuss work in progress in this repository.
-That includes proposals for new HLSL features as well as the ongoing work to write a language specification.
-
-For more information on this meeting and the terms and conditions for
-participation, see the [Design Meeting](docs/DesignMeeting.md) documentation.
-
 ## Trademarks
 
 This project may contain trademarks or logos for projects, products, or services. Authorized use of Microsoft

README.md

@@ -3,7 +3,9 @@ title: "Design Meeting Minutes"
 weight: 20
 ---
 
-This section contains the HLSL Design Meeting minutes.
+This section contains the HLSL Design Meeting minutes. These meeting minutes are
+left for historical record, but the meetings themselves have been replaced by
+[Ecma TC57](https://github.com/hlsl-tc57).
 
 ## All meetings
 

docs/DesignMeeting.md

@@ -3,17 +3,28 @@ title: Proposal Process
 ---
 
 The primary purpose of this repository is to provide visibility into the feature
-development process for HLSL and solicit feedback from the wider community.
+development process for DirectX extensions to HLSL and solicit feedback from the
+wider community.
+
+> Note: As of January 2026, this GitHub project is _only_ for DirectX specific
+> features. Development of the HLSL core language has moved to [Ecma
+> TC57](https://github.com/hlsl-tc57). HLSL core features developed in this
+> space are left for historical record, but all future core language features
+> are being handled in TC57.
+>
+> Similarly HLSL Vulkan extensions are now being developed and managed by the
+> Khronos Vulkan Workin Group. Vulkan features developed in this space are left
+> for historical record, but all new features are being handled in spaces
+> managed by The Khronos Group.
+
 Despite the openness of this process there are two significant caveats that
 should be noted:
 
-1. Final decisions about what features are included or excluded from HLSL are
-   made by the MSFT HLSL Team. Our goals are to make HLSL the best programming
-   language across all supported runtime targets, not just DirectX or Vulkan.
+1. Final decisions about what features are included or excluded from DirectX are
+   made by the MSFT HLSL Team.
 2. Some HLSL features may instead go through a
-
-   [Fast-track](#fast-track-for-extensions) process. This process is reserved
-   for platform and vendor extensions and is not suitable to all features.
+   [Fast-track](#fast-track-for-extensions) process, although we aim for
+   openness as early as possible.
 
 Feature proposals from outside the HLSL team will be interpreted as requests,
 and may be considered or rejected based on team and release priorities. You
@@ -44,10 +55,6 @@ features we require at least one _Sponsor_ from the HLSL team and one _Sponsor_
 from the Khronos Vulkan Working Group. If you need assistance finding a
 _Sponsor_ for a proposal reach out to the [HLSL Team](Contact.md).
 
-All feature proposals are evaluated against the goals for the next HLSL language
-revision. The goals for the upcoming HLSL language version can be found
-[here](HLSL202x.md).
-
 When writing a feature proposal you should also familiarize yourself with the
 HLSL [Design Considerations](DesignConsiderations.md).
 
@@ -122,9 +129,8 @@ New proposals should be merged as **Under Consideration**. After assigning a
 number and merging the PR the author(s) should file issues tracking the work to
 flesh out and complete the detailed design.
 
-PRs introducing new proposals for language features will be reviewed at the
-[Design Meeting](/docs/DesignMeeting.md). PRs introducing new proposals for
-DirectX or DXIL features will be reviewed by Microsoft on a regular cadence.
+PRs introducing new proposals for language features will be reviewed by the
+Microsoft HLSL team on a regular cadence.
 
 #### Completing the Detailed Design