diff --git a/agendas/2026/01-Jan/01-primary.md b/agendas/2026/01-Jan/01-primary.md
new file mode 100644
index 0000000..9df44f7
--- /dev/null
+++ b/agendas/2026/01-Jan/01-primary.md
@@ -0,0 +1 @@
+This meeting is cancelled due to the winter break.
diff --git a/agendas/2026/01-Jan/08-week-2.md b/agendas/2026/01-Jan/08-week-2.md
new file mode 100644
index 0000000..d0ad16d
--- /dev/null
+++ b/agendas/2026/01-Jan/08-week-2.md
@@ -0,0 +1,118 @@
+<!--
+
+# How to join (copied directly from /JoiningAMeeting.md)
+
+Hello! You're welcome to join our subcommittee meeting and add to the agenda by
+following these three steps:
+
+1.  Add your name to the list of attendees (in alphabetical order).
+
+    - To respect meeting size, attendees should be relevant to the agenda. That
+      means we expect most who join the meeting to participate in discussion. If
+      you'd rather just watch, check out our YouTube[1].
+
+    - Please include the organization (or project) you represent, and the
+      location (including country code[2]) you expect to be located in during
+      the meeting.
+
+    - If you're willing to help take notes, add "✏️" after your name (eg. Ada
+      Lovelace ✏). This is hugely helpful!
+
+2.  If relevant, add your topic to the agenda (sorted by expected time).
+
+    - Every agenda item has four parts: 1) the topic, 2) an expected time
+      constraint, 3) who's leading the discussion, and 4) a list of any relevant
+      links (RFC docs, issues, PRs, presentations, etc). Follow the format of
+      existing agenda items.
+
+    - Know what you want to get out of the agenda topic - what feedback do you
+      need? What questions do you need answered? Are you looking for consensus
+      or just directional feedback?
+
+    - If your topic is a new proposal it's likely an "RFC 0"[3]. The barrier of
+      entry for documenting new proposals is intentionally low, writing a few
+      sentences about the problem you're trying to solve and the rough shape of
+      your proposed solution is normally sufficient.
+
+      You can create a link for this:
+
+      - As an issue against this repo.
+      - As a GitHub discussion in this repo.
+      - As an RFC document into the rfcs/ folder of this repo.
+
+3.  Review our guidelines and agree to our Spec Membership & CLA.
+
+    - Review and understand our Spec Membership Agreement, Participation &
+      Contribution Guidelines, and Code of Conduct. You'll find links to these
+      in the first agenda item of every meeting.
+
+    - If this is your first time, our bot will comment on your Pull Request with
+      a link to our Spec Membership & CLA. Please follow along and agree before
+      your PR is merged.
+
+      Your organization may sign this for all of its members. To set this up,
+      please ask operations@graphql.org.
+
+PLEASE TAKE NOTE:
+
+- By joining this meeting you must agree to the Specification Membership
+  Agreement and Code of Conduct.
+
+- Meetings are recorded and made available on YouTube[1], by joining you consent
+  to being recorded.
+
+[1] Youtube: https://www.youtube.com/channel/UCERcwLeheOXp_u61jEXxHMA [2]
+Country codes:
+https://en.wikipedia.org/wiki/List_of_ISO_3166_country_codes#Current_ISO_3166_country_codes
+[3] RFC stages:
+https://github.com/graphql/graphql-spec/blob/main/CONTRIBUTING.md#rfc-contribution-stages
+
+
+-->
+
+| This is an open meeting: To attend, read [JoiningAMeeting.md][] then edit and PR this file. (Edit: ✎ above, or press "e") |
+| ---------------------------------------------------------------------------------------- |
+
+# Composite Schemas WG — January 2026 (Week 2)
+
+The Composite Schemas subcommittee meets weekly to progress the "Composite
+Schemas Specification" project.
+
+The first meeting each month is the primary monthly meeting; to enable a greater
+cadence of progress we also have weekly meetings which tend to be more informal.
+
+- **Date & Time**: [January 8, 2026, 6:00 – 7:00 PM GMT+1](https://www.timeanddate.com/worldclock/converter.html?iso=20260108T170000&p1=3775&p2=110&p3=24&p4=37&p5=188&p6=496&p7=676&p8=438&p9=268&p10=234&p11=78&p12=604)
+  - View the [calendar][], or subscribe ([Google Calendar][], [ical file][]).
+  - _Please Note:_ The date or time may change. Please check this agenda the
+    week of the meeting to confirm. While we try to keep all calendars accurate,
+    this agenda document is the source of truth.
+- **Video Conference Link**: https://zoom.us/j/91078840351
+  - _Password:_ composite
+- **Live Notes**: [Live Notes][]
+
+[calendar]: https://calendar.google.com/calendar/embed?src=linuxfoundation.org_ik79t9uuj2p32i3r203dgv5mo8%40group.calendar.google.com
+[google calendar]: https://calendar.google.com/calendar?cid=bGludXhmb3VuZGF0aW9uLm9yZ19pazc5dDl1dWoycDMyaTNyMjAzZGd2NW1vOEBncm91cC5jYWxlbmRhci5nb29nbGUuY29t
+[ical file]: https://calendar.google.com/calendar/ical/linuxfoundation.org_ik79t9uuj2p32i3r203dgv5mo8%40group.calendar.google.com/public/basic.ics
+[JoiningAMeeting.md]: https://github.com/graphql/composite-schemas-wg/blob/main/JoiningAMeeting.md
+[live notes]: https://docs.google.com/document/d/1hJO6U7daYvcNcQ3FBKnh3v4R256ers6M8IGyqRpY_kE/edit?usp=sharing
+
+## Attendees
+
+<!-- prettier-ignore -->
+| Name             | GitHub        | Organization       | Location              |
+| :--------------- | :------------ | :----------------- | :-------------------- |
+
+
+## Agenda
+
+1. Agree to Membership Agreement, Participation & Contribution Guidelines and Code of Conduct (1m, Host)
+   - [Specification Membership Agreement](https://github.com/graphql/foundation)
+   - [Participation Guidelines](https://github.com/graphql/graphql-wg#participation-guidelines)
+   - [Contribution Guide](https://github.com/graphql/graphql-spec/blob/main/CONTRIBUTING.md)
+   - [Code of Conduct](https://github.com/graphql/foundation/blob/master/CODE-OF-CONDUCT.md)
+   - Meetings are [published to YouTube](https://www.youtube.com/@GraphQLFoundation/videos) and we may use LLM/AI summary tools
+1. Introduction of attendees (5m, Host)
+1. Determine volunteers for note taking (1m, Host)
+1. Review agenda (2m, Host)
+1. Check for [ready for review agenda items](https://github.com/graphql/composite-schemas-wg/issues?q=is%3Aissue+is%3Aopen+label%3A%22Ready+for+review+%F0%9F%99%8C%22+sort%3Aupdated-desc) (5m, Host)
+1. Reminder: [grants available for key initiatives](https://graphql.org/community/foundation/community-grant/) (1m, Host)
diff --git a/agendas/2026/01-Jan/15-week-3.md b/agendas/2026/01-Jan/15-week-3.md
new file mode 100644
index 0000000..070b365
--- /dev/null
+++ b/agendas/2026/01-Jan/15-week-3.md
@@ -0,0 +1,118 @@
+<!--
+
+# How to join (copied directly from /JoiningAMeeting.md)
+
+Hello! You're welcome to join our subcommittee meeting and add to the agenda by
+following these three steps:
+
+1.  Add your name to the list of attendees (in alphabetical order).
+
+    - To respect meeting size, attendees should be relevant to the agenda. That
+      means we expect most who join the meeting to participate in discussion. If
+      you'd rather just watch, check out our YouTube[1].
+
+    - Please include the organization (or project) you represent, and the
+      location (including country code[2]) you expect to be located in during
+      the meeting.
+
+    - If you're willing to help take notes, add "✏️" after your name (eg. Ada
+      Lovelace ✏). This is hugely helpful!
+
+2.  If relevant, add your topic to the agenda (sorted by expected time).
+
+    - Every agenda item has four parts: 1) the topic, 2) an expected time
+      constraint, 3) who's leading the discussion, and 4) a list of any relevant
+      links (RFC docs, issues, PRs, presentations, etc). Follow the format of
+      existing agenda items.
+
+    - Know what you want to get out of the agenda topic - what feedback do you
+      need? What questions do you need answered? Are you looking for consensus
+      or just directional feedback?
+
+    - If your topic is a new proposal it's likely an "RFC 0"[3]. The barrier of
+      entry for documenting new proposals is intentionally low, writing a few
+      sentences about the problem you're trying to solve and the rough shape of
+      your proposed solution is normally sufficient.
+
+      You can create a link for this:
+
+      - As an issue against this repo.
+      - As a GitHub discussion in this repo.
+      - As an RFC document into the rfcs/ folder of this repo.
+
+3.  Review our guidelines and agree to our Spec Membership & CLA.
+
+    - Review and understand our Spec Membership Agreement, Participation &
+      Contribution Guidelines, and Code of Conduct. You'll find links to these
+      in the first agenda item of every meeting.
+
+    - If this is your first time, our bot will comment on your Pull Request with
+      a link to our Spec Membership & CLA. Please follow along and agree before
+      your PR is merged.
+
+      Your organization may sign this for all of its members. To set this up,
+      please ask operations@graphql.org.
+
+PLEASE TAKE NOTE:
+
+- By joining this meeting you must agree to the Specification Membership
+  Agreement and Code of Conduct.
+
+- Meetings are recorded and made available on YouTube[1], by joining you consent
+  to being recorded.
+
+[1] Youtube: https://www.youtube.com/channel/UCERcwLeheOXp_u61jEXxHMA [2]
+Country codes:
+https://en.wikipedia.org/wiki/List_of_ISO_3166_country_codes#Current_ISO_3166_country_codes
+[3] RFC stages:
+https://github.com/graphql/graphql-spec/blob/main/CONTRIBUTING.md#rfc-contribution-stages
+
+
+-->
+
+| This is an open meeting: To attend, read [JoiningAMeeting.md][] then edit and PR this file. (Edit: ✎ above, or press "e") |
+| ---------------------------------------------------------------------------------------- |
+
+# Composite Schemas WG — January 2026 (Week 3)
+
+The Composite Schemas subcommittee meets weekly to progress the "Composite
+Schemas Specification" project.
+
+The first meeting each month is the primary monthly meeting; to enable a greater
+cadence of progress we also have weekly meetings which tend to be more informal.
+
+- **Date & Time**: [January 15, 2026, 6:00 – 7:00 PM GMT+1](https://www.timeanddate.com/worldclock/converter.html?iso=20260115T170000&p1=3775&p2=110&p3=24&p4=37&p5=188&p6=496&p7=676&p8=438&p9=268&p10=234&p11=78&p12=604)
+  - View the [calendar][], or subscribe ([Google Calendar][], [ical file][]).
+  - _Please Note:_ The date or time may change. Please check this agenda the
+    week of the meeting to confirm. While we try to keep all calendars accurate,
+    this agenda document is the source of truth.
+- **Video Conference Link**: https://zoom.us/j/91078840351
+  - _Password:_ composite
+- **Live Notes**: [Live Notes][]
+
+[calendar]: https://calendar.google.com/calendar/embed?src=linuxfoundation.org_ik79t9uuj2p32i3r203dgv5mo8%40group.calendar.google.com
+[google calendar]: https://calendar.google.com/calendar?cid=bGludXhmb3VuZGF0aW9uLm9yZ19pazc5dDl1dWoycDMyaTNyMjAzZGd2NW1vOEBncm91cC5jYWxlbmRhci5nb29nbGUuY29t
+[ical file]: https://calendar.google.com/calendar/ical/linuxfoundation.org_ik79t9uuj2p32i3r203dgv5mo8%40group.calendar.google.com/public/basic.ics
+[JoiningAMeeting.md]: https://github.com/graphql/composite-schemas-wg/blob/main/JoiningAMeeting.md
+[live notes]: https://docs.google.com/document/d/1hJO6U7daYvcNcQ3FBKnh3v4R256ers6M8IGyqRpY_kE/edit?usp=sharing
+
+## Attendees
+
+<!-- prettier-ignore -->
+| Name             | GitHub        | Organization       | Location              |
+| :--------------- | :------------ | :----------------- | :-------------------- |
+
+
+## Agenda
+
+1. Agree to Membership Agreement, Participation & Contribution Guidelines and Code of Conduct (1m, Host)
+   - [Specification Membership Agreement](https://github.com/graphql/foundation)
+   - [Participation Guidelines](https://github.com/graphql/graphql-wg#participation-guidelines)
+   - [Contribution Guide](https://github.com/graphql/graphql-spec/blob/main/CONTRIBUTING.md)
+   - [Code of Conduct](https://github.com/graphql/foundation/blob/master/CODE-OF-CONDUCT.md)
+   - Meetings are [published to YouTube](https://www.youtube.com/@GraphQLFoundation/videos) and we may use LLM/AI summary tools
+1. Introduction of attendees (5m, Host)
+1. Determine volunteers for note taking (1m, Host)
+1. Review agenda (2m, Host)
+1. Check for [ready for review agenda items](https://github.com/graphql/composite-schemas-wg/issues?q=is%3Aissue+is%3Aopen+label%3A%22Ready+for+review+%F0%9F%99%8C%22+sort%3Aupdated-desc) (5m, Host)
+1. Reminder: [grants available for key initiatives](https://graphql.org/community/foundation/community-grant/) (1m, Host)
diff --git a/agendas/2026/01-Jan/22-week-4.md b/agendas/2026/01-Jan/22-week-4.md
new file mode 100644
index 0000000..de323ff
--- /dev/null
+++ b/agendas/2026/01-Jan/22-week-4.md
@@ -0,0 +1,118 @@
+<!--
+
+# How to join (copied directly from /JoiningAMeeting.md)
+
+Hello! You're welcome to join our subcommittee meeting and add to the agenda by
+following these three steps:
+
+1.  Add your name to the list of attendees (in alphabetical order).
+
+    - To respect meeting size, attendees should be relevant to the agenda. That
+      means we expect most who join the meeting to participate in discussion. If
+      you'd rather just watch, check out our YouTube[1].
+
+    - Please include the organization (or project) you represent, and the
+      location (including country code[2]) you expect to be located in during
+      the meeting.
+
+    - If you're willing to help take notes, add "✏️" after your name (eg. Ada
+      Lovelace ✏). This is hugely helpful!
+
+2.  If relevant, add your topic to the agenda (sorted by expected time).
+
+    - Every agenda item has four parts: 1) the topic, 2) an expected time
+      constraint, 3) who's leading the discussion, and 4) a list of any relevant
+      links (RFC docs, issues, PRs, presentations, etc). Follow the format of
+      existing agenda items.
+
+    - Know what you want to get out of the agenda topic - what feedback do you
+      need? What questions do you need answered? Are you looking for consensus
+      or just directional feedback?
+
+    - If your topic is a new proposal it's likely an "RFC 0"[3]. The barrier of
+      entry for documenting new proposals is intentionally low, writing a few
+      sentences about the problem you're trying to solve and the rough shape of
+      your proposed solution is normally sufficient.
+
+      You can create a link for this:
+
+      - As an issue against this repo.
+      - As a GitHub discussion in this repo.
+      - As an RFC document into the rfcs/ folder of this repo.
+
+3.  Review our guidelines and agree to our Spec Membership & CLA.
+
+    - Review and understand our Spec Membership Agreement, Participation &
+      Contribution Guidelines, and Code of Conduct. You'll find links to these
+      in the first agenda item of every meeting.
+
+    - If this is your first time, our bot will comment on your Pull Request with
+      a link to our Spec Membership & CLA. Please follow along and agree before
+      your PR is merged.
+
+      Your organization may sign this for all of its members. To set this up,
+      please ask operations@graphql.org.
+
+PLEASE TAKE NOTE:
+
+- By joining this meeting you must agree to the Specification Membership
+  Agreement and Code of Conduct.
+
+- Meetings are recorded and made available on YouTube[1], by joining you consent
+  to being recorded.
+
+[1] Youtube: https://www.youtube.com/channel/UCERcwLeheOXp_u61jEXxHMA [2]
+Country codes:
+https://en.wikipedia.org/wiki/List_of_ISO_3166_country_codes#Current_ISO_3166_country_codes
+[3] RFC stages:
+https://github.com/graphql/graphql-spec/blob/main/CONTRIBUTING.md#rfc-contribution-stages
+
+
+-->
+
+| This is an open meeting: To attend, read [JoiningAMeeting.md][] then edit and PR this file. (Edit: ✎ above, or press "e") |
+| ---------------------------------------------------------------------------------------- |
+
+# Composite Schemas WG — January 2026 (Week 4)
+
+The Composite Schemas subcommittee meets weekly to progress the "Composite
+Schemas Specification" project.
+
+The first meeting each month is the primary monthly meeting; to enable a greater
+cadence of progress we also have weekly meetings which tend to be more informal.
+
+- **Date & Time**: [January 22, 2026, 6:00 – 7:00 PM GMT+1](https://www.timeanddate.com/worldclock/converter.html?iso=20260122T170000&p1=3775&p2=110&p3=24&p4=37&p5=188&p6=496&p7=676&p8=438&p9=268&p10=234&p11=78&p12=604)
+  - View the [calendar][], or subscribe ([Google Calendar][], [ical file][]).
+  - _Please Note:_ The date or time may change. Please check this agenda the
+    week of the meeting to confirm. While we try to keep all calendars accurate,
+    this agenda document is the source of truth.
+- **Video Conference Link**: https://zoom.us/j/91078840351
+  - _Password:_ composite
+- **Live Notes**: [Live Notes][]
+
+[calendar]: https://calendar.google.com/calendar/embed?src=linuxfoundation.org_ik79t9uuj2p32i3r203dgv5mo8%40group.calendar.google.com
+[google calendar]: https://calendar.google.com/calendar?cid=bGludXhmb3VuZGF0aW9uLm9yZ19pazc5dDl1dWoycDMyaTNyMjAzZGd2NW1vOEBncm91cC5jYWxlbmRhci5nb29nbGUuY29t
+[ical file]: https://calendar.google.com/calendar/ical/linuxfoundation.org_ik79t9uuj2p32i3r203dgv5mo8%40group.calendar.google.com/public/basic.ics
+[JoiningAMeeting.md]: https://github.com/graphql/composite-schemas-wg/blob/main/JoiningAMeeting.md
+[live notes]: https://docs.google.com/document/d/1hJO6U7daYvcNcQ3FBKnh3v4R256ers6M8IGyqRpY_kE/edit?usp=sharing
+
+## Attendees
+
+<!-- prettier-ignore -->
+| Name             | GitHub        | Organization       | Location              |
+| :--------------- | :------------ | :----------------- | :-------------------- |
+
+
+## Agenda
+
+1. Agree to Membership Agreement, Participation & Contribution Guidelines and Code of Conduct (1m, Host)
+   - [Specification Membership Agreement](https://github.com/graphql/foundation)
+   - [Participation Guidelines](https://github.com/graphql/graphql-wg#participation-guidelines)
+   - [Contribution Guide](https://github.com/graphql/graphql-spec/blob/main/CONTRIBUTING.md)
+   - [Code of Conduct](https://github.com/graphql/foundation/blob/master/CODE-OF-CONDUCT.md)
+   - Meetings are [published to YouTube](https://www.youtube.com/@GraphQLFoundation/videos) and we may use LLM/AI summary tools
+1. Introduction of attendees (5m, Host)
+1. Determine volunteers for note taking (1m, Host)
+1. Review agenda (2m, Host)
+1. Check for [ready for review agenda items](https://github.com/graphql/composite-schemas-wg/issues?q=is%3Aissue+is%3Aopen+label%3A%22Ready+for+review+%F0%9F%99%8C%22+sort%3Aupdated-desc) (5m, Host)
+1. Reminder: [grants available for key initiatives](https://graphql.org/community/foundation/community-grant/) (1m, Host)
diff --git a/agendas/2026/01-Jan/29-week-5.md b/agendas/2026/01-Jan/29-week-5.md
new file mode 100644
index 0000000..51d395c
--- /dev/null
+++ b/agendas/2026/01-Jan/29-week-5.md
@@ -0,0 +1,118 @@
+<!--
+
+# How to join (copied directly from /JoiningAMeeting.md)
+
+Hello! You're welcome to join our subcommittee meeting and add to the agenda by
+following these three steps:
+
+1.  Add your name to the list of attendees (in alphabetical order).
+
+    - To respect meeting size, attendees should be relevant to the agenda. That
+      means we expect most who join the meeting to participate in discussion. If
+      you'd rather just watch, check out our YouTube[1].
+
+    - Please include the organization (or project) you represent, and the
+      location (including country code[2]) you expect to be located in during
+      the meeting.
+
+    - If you're willing to help take notes, add "✏️" after your name (eg. Ada
+      Lovelace ✏). This is hugely helpful!
+
+2.  If relevant, add your topic to the agenda (sorted by expected time).
+
+    - Every agenda item has four parts: 1) the topic, 2) an expected time
+      constraint, 3) who's leading the discussion, and 4) a list of any relevant
+      links (RFC docs, issues, PRs, presentations, etc). Follow the format of
+      existing agenda items.
+
+    - Know what you want to get out of the agenda topic - what feedback do you
+      need? What questions do you need answered? Are you looking for consensus
+      or just directional feedback?
+
+    - If your topic is a new proposal it's likely an "RFC 0"[3]. The barrier of
+      entry for documenting new proposals is intentionally low, writing a few
+      sentences about the problem you're trying to solve and the rough shape of
+      your proposed solution is normally sufficient.
+
+      You can create a link for this:
+
+      - As an issue against this repo.
+      - As a GitHub discussion in this repo.
+      - As an RFC document into the rfcs/ folder of this repo.
+
+3.  Review our guidelines and agree to our Spec Membership & CLA.
+
+    - Review and understand our Spec Membership Agreement, Participation &
+      Contribution Guidelines, and Code of Conduct. You'll find links to these
+      in the first agenda item of every meeting.
+
+    - If this is your first time, our bot will comment on your Pull Request with
+      a link to our Spec Membership & CLA. Please follow along and agree before
+      your PR is merged.
+
+      Your organization may sign this for all of its members. To set this up,
+      please ask operations@graphql.org.
+
+PLEASE TAKE NOTE:
+
+- By joining this meeting you must agree to the Specification Membership
+  Agreement and Code of Conduct.
+
+- Meetings are recorded and made available on YouTube[1], by joining you consent
+  to being recorded.
+
+[1] Youtube: https://www.youtube.com/channel/UCERcwLeheOXp_u61jEXxHMA [2]
+Country codes:
+https://en.wikipedia.org/wiki/List_of_ISO_3166_country_codes#Current_ISO_3166_country_codes
+[3] RFC stages:
+https://github.com/graphql/graphql-spec/blob/main/CONTRIBUTING.md#rfc-contribution-stages
+
+
+-->
+
+| This is an open meeting: To attend, read [JoiningAMeeting.md][] then edit and PR this file. (Edit: ✎ above, or press "e") |
+| ---------------------------------------------------------------------------------------- |
+
+# Composite Schemas WG — January 2026 (Week 5)
+
+The Composite Schemas subcommittee meets weekly to progress the "Composite
+Schemas Specification" project.
+
+The first meeting each month is the primary monthly meeting; to enable a greater
+cadence of progress we also have weekly meetings which tend to be more informal.
+
+- **Date & Time**: [January 29, 2026, 6:00 – 7:00 PM GMT+1](https://www.timeanddate.com/worldclock/converter.html?iso=20260129T170000&p1=3775&p2=110&p3=24&p4=37&p5=188&p6=496&p7=676&p8=438&p9=268&p10=234&p11=78&p12=604)
+  - View the [calendar][], or subscribe ([Google Calendar][], [ical file][]).
+  - _Please Note:_ The date or time may change. Please check this agenda the
+    week of the meeting to confirm. While we try to keep all calendars accurate,
+    this agenda document is the source of truth.
+- **Video Conference Link**: https://zoom.us/j/91078840351
+  - _Password:_ composite
+- **Live Notes**: [Live Notes][]
+
+[calendar]: https://calendar.google.com/calendar/embed?src=linuxfoundation.org_ik79t9uuj2p32i3r203dgv5mo8%40group.calendar.google.com
+[google calendar]: https://calendar.google.com/calendar?cid=bGludXhmb3VuZGF0aW9uLm9yZ19pazc5dDl1dWoycDMyaTNyMjAzZGd2NW1vOEBncm91cC5jYWxlbmRhci5nb29nbGUuY29t
+[ical file]: https://calendar.google.com/calendar/ical/linuxfoundation.org_ik79t9uuj2p32i3r203dgv5mo8%40group.calendar.google.com/public/basic.ics
+[JoiningAMeeting.md]: https://github.com/graphql/composite-schemas-wg/blob/main/JoiningAMeeting.md
+[live notes]: https://docs.google.com/document/d/1hJO6U7daYvcNcQ3FBKnh3v4R256ers6M8IGyqRpY_kE/edit?usp=sharing
+
+## Attendees
+
+<!-- prettier-ignore -->
+| Name             | GitHub        | Organization       | Location              |
+| :--------------- | :------------ | :----------------- | :-------------------- |
+
+
+## Agenda
+
+1. Agree to Membership Agreement, Participation & Contribution Guidelines and Code of Conduct (1m, Host)
+   - [Specification Membership Agreement](https://github.com/graphql/foundation)
+   - [Participation Guidelines](https://github.com/graphql/graphql-wg#participation-guidelines)
+   - [Contribution Guide](https://github.com/graphql/graphql-spec/blob/main/CONTRIBUTING.md)
+   - [Code of Conduct](https://github.com/graphql/foundation/blob/master/CODE-OF-CONDUCT.md)
+   - Meetings are [published to YouTube](https://www.youtube.com/@GraphQLFoundation/videos) and we may use LLM/AI summary tools
+1. Introduction of attendees (5m, Host)
+1. Determine volunteers for note taking (1m, Host)
+1. Review agenda (2m, Host)
+1. Check for [ready for review agenda items](https://github.com/graphql/composite-schemas-wg/issues?q=is%3Aissue+is%3Aopen+label%3A%22Ready+for+review+%F0%9F%99%8C%22+sort%3Aupdated-desc) (5m, Host)
+1. Reminder: [grants available for key initiatives](https://graphql.org/community/foundation/community-grant/) (1m, Host)
diff --git a/agendas/2026/02-Feb/05-primary.md b/agendas/2026/02-Feb/05-primary.md
new file mode 100644
index 0000000..8c5717b
--- /dev/null
+++ b/agendas/2026/02-Feb/05-primary.md
@@ -0,0 +1,123 @@
+<!--
+
+# How to join (copied directly from /JoiningAMeeting.md)
+
+Hello! You're welcome to join our subcommittee meeting and add to the agenda by
+following these three steps:
+
+1.  Add your name to the list of attendees (in alphabetical order).
+
+    - To respect meeting size, attendees should be relevant to the agenda. That
+      means we expect most who join the meeting to participate in discussion. If
+      you'd rather just watch, check out our YouTube[1].
+
+    - Please include the organization (or project) you represent, and the
+      location (including country code[2]) you expect to be located in during
+      the meeting.
+
+    - If you're willing to help take notes, add "✏️" after your name (eg. Ada
+      Lovelace ✏). This is hugely helpful!
+
+2.  If relevant, add your topic to the agenda (sorted by expected time).
+
+    - Every agenda item has four parts: 1) the topic, 2) an expected time
+      constraint, 3) who's leading the discussion, and 4) a list of any relevant
+      links (RFC docs, issues, PRs, presentations, etc). Follow the format of
+      existing agenda items.
+
+    - Know what you want to get out of the agenda topic - what feedback do you
+      need? What questions do you need answered? Are you looking for consensus
+      or just directional feedback?
+
+    - If your topic is a new proposal it's likely an "RFC 0"[3]. The barrier of
+      entry for documenting new proposals is intentionally low, writing a few
+      sentences about the problem you're trying to solve and the rough shape of
+      your proposed solution is normally sufficient.
+
+      You can create a link for this:
+
+      - As an issue against this repo.
+      - As a GitHub discussion in this repo.
+      - As an RFC document into the rfcs/ folder of this repo.
+
+3.  Review our guidelines and agree to our Spec Membership & CLA.
+
+    - Review and understand our Spec Membership Agreement, Participation &
+      Contribution Guidelines, and Code of Conduct. You'll find links to these
+      in the first agenda item of every meeting.
+
+    - If this is your first time, our bot will comment on your Pull Request with
+      a link to our Spec Membership & CLA. Please follow along and agree before
+      your PR is merged.
+
+      Your organization may sign this for all of its members. To set this up,
+      please ask operations@graphql.org.
+
+PLEASE TAKE NOTE:
+
+- By joining this meeting you must agree to the Specification Membership
+  Agreement and Code of Conduct.
+
+- Meetings are recorded and made available on YouTube[1], by joining you consent
+  to being recorded.
+
+[1] Youtube: https://www.youtube.com/channel/UCERcwLeheOXp_u61jEXxHMA [2]
+Country codes:
+https://en.wikipedia.org/wiki/List_of_ISO_3166_country_codes#Current_ISO_3166_country_codes
+[3] RFC stages:
+https://github.com/graphql/graphql-spec/blob/main/CONTRIBUTING.md#rfc-contribution-stages
+
+
+-->
+
+| This is an open meeting: To attend, read [JoiningAMeeting.md][] then edit and PR this file. (Edit: ✎ above, or press "e") |
+| ---------------------------------------------------------------------------------------- |
+
+# Composite Schemas WG — February 2026 (Primary)
+
+The Composite Schemas subcommittee meets weekly to progress the "Composite
+Schemas Specification" project.
+
+The first meeting each month is the primary monthly meeting; to enable a greater
+cadence of progress we also have weekly meetings which tend to be more informal.
+
+- **Date & Time**: [February 5, 2026, 6:00 – 7:00 PM GMT+1](https://www.timeanddate.com/worldclock/converter.html?iso=20260205T170000&p1=3775&p2=110&p3=24&p4=37&p5=188&p6=496&p7=676&p8=438&p9=268&p10=234&p11=78&p12=604)
+  - View the [calendar][], or subscribe ([Google Calendar][], [ical file][]).
+  - _Please Note:_ The date or time may change. Please check this agenda the
+    week of the meeting to confirm. While we try to keep all calendars accurate,
+    this agenda document is the source of truth.
+- **Video Conference Link**: https://zoom.us/j/91078840351
+  - _Password:_ composite
+- **Live Notes**: [Live Notes][]
+
+[calendar]: https://calendar.google.com/calendar/embed?src=linuxfoundation.org_ik79t9uuj2p32i3r203dgv5mo8%40group.calendar.google.com
+[google calendar]: https://calendar.google.com/calendar?cid=bGludXhmb3VuZGF0aW9uLm9yZ19pazc5dDl1dWoycDMyaTNyMjAzZGd2NW1vOEBncm91cC5jYWxlbmRhci5nb29nbGUuY29t
+[ical file]: https://calendar.google.com/calendar/ical/linuxfoundation.org_ik79t9uuj2p32i3r203dgv5mo8%40group.calendar.google.com/public/basic.ics
+[JoiningAMeeting.md]: https://github.com/graphql/composite-schemas-wg/blob/main/JoiningAMeeting.md
+[live notes]: https://docs.google.com/document/d/1hJO6U7daYvcNcQ3FBKnh3v4R256ers6M8IGyqRpY_kE/edit?usp=sharing
+
+## Attendees
+
+<!-- prettier-ignore -->
+| Name             | GitHub        | Organization       | Location              |
+| :--------------- | :------------ | :----------------- | :-------------------- |
+
+
+## Agenda
+
+1. Agree to Membership Agreement, Participation & Contribution Guidelines and Code of Conduct (1m, Host)
+   - [Specification Membership Agreement](https://github.com/graphql/foundation)
+   - [Participation Guidelines](https://github.com/graphql/graphql-wg#participation-guidelines)
+   - [Contribution Guide](https://github.com/graphql/graphql-spec/blob/main/CONTRIBUTING.md)
+   - [Code of Conduct](https://github.com/graphql/foundation/blob/master/CODE-OF-CONDUCT.md)
+   - Meetings are [published to YouTube](https://www.youtube.com/@GraphQLFoundation/videos) and we may use LLM/AI summary tools
+1. Introduction of attendees (5m, Host)
+1. Determine volunteers for note taking (1m, Host)
+1. Review agenda (2m, Host)
+1. Review prior secondary meetings (5m, Host)
+   - [Composite Schemas WG — January 2026 (Week 2)](https://github.com/graphql/composite-schemas-wg/blob/main/agendas/2026/01-Jan/08-week-2.md)
+   - [Composite Schemas WG — January 2026 (Week 3)](https://github.com/graphql/composite-schemas-wg/blob/main/agendas/2026/01-Jan/15-week-3.md)
+   - [Composite Schemas WG — January 2026 (Week 4)](https://github.com/graphql/composite-schemas-wg/blob/main/agendas/2026/01-Jan/22-week-4.md)
+   - [Composite Schemas WG — January 2026 (Week 5)](https://github.com/graphql/composite-schemas-wg/blob/main/agendas/2026/01-Jan/29-week-5.md)
+1. Check for [ready for review agenda items](https://github.com/graphql/composite-schemas-wg/issues?q=is%3Aissue+is%3Aopen+label%3A%22Ready+for+review+%F0%9F%99%8C%22+sort%3Aupdated-desc) (5m, Host)
+1. Reminder: [grants available for key initiatives](https://graphql.org/community/foundation/community-grant/) (1m, Host)
diff --git a/agendas/2026/02-Feb/12-week-2.md b/agendas/2026/02-Feb/12-week-2.md
new file mode 100644
index 0000000..2a3131b
--- /dev/null
+++ b/agendas/2026/02-Feb/12-week-2.md
@@ -0,0 +1,118 @@
+<!--
+
+# How to join (copied directly from /JoiningAMeeting.md)
+
+Hello! You're welcome to join our subcommittee meeting and add to the agenda by
+following these three steps:
+
+1.  Add your name to the list of attendees (in alphabetical order).
+
+    - To respect meeting size, attendees should be relevant to the agenda. That
+      means we expect most who join the meeting to participate in discussion. If
+      you'd rather just watch, check out our YouTube[1].
+
+    - Please include the organization (or project) you represent, and the
+      location (including country code[2]) you expect to be located in during
+      the meeting.
+
+    - If you're willing to help take notes, add "✏️" after your name (eg. Ada
+      Lovelace ✏). This is hugely helpful!
+
+2.  If relevant, add your topic to the agenda (sorted by expected time).
+
+    - Every agenda item has four parts: 1) the topic, 2) an expected time
+      constraint, 3) who's leading the discussion, and 4) a list of any relevant
+      links (RFC docs, issues, PRs, presentations, etc). Follow the format of
+      existing agenda items.
+
+    - Know what you want to get out of the agenda topic - what feedback do you
+      need? What questions do you need answered? Are you looking for consensus
+      or just directional feedback?
+
+    - If your topic is a new proposal it's likely an "RFC 0"[3]. The barrier of
+      entry for documenting new proposals is intentionally low, writing a few
+      sentences about the problem you're trying to solve and the rough shape of
+      your proposed solution is normally sufficient.
+
+      You can create a link for this:
+
+      - As an issue against this repo.
+      - As a GitHub discussion in this repo.
+      - As an RFC document into the rfcs/ folder of this repo.
+
+3.  Review our guidelines and agree to our Spec Membership & CLA.
+
+    - Review and understand our Spec Membership Agreement, Participation &
+      Contribution Guidelines, and Code of Conduct. You'll find links to these
+      in the first agenda item of every meeting.
+
+    - If this is your first time, our bot will comment on your Pull Request with
+      a link to our Spec Membership & CLA. Please follow along and agree before
+      your PR is merged.
+
+      Your organization may sign this for all of its members. To set this up,
+      please ask operations@graphql.org.
+
+PLEASE TAKE NOTE:
+
+- By joining this meeting you must agree to the Specification Membership
+  Agreement and Code of Conduct.
+
+- Meetings are recorded and made available on YouTube[1], by joining you consent
+  to being recorded.
+
+[1] Youtube: https://www.youtube.com/channel/UCERcwLeheOXp_u61jEXxHMA [2]
+Country codes:
+https://en.wikipedia.org/wiki/List_of_ISO_3166_country_codes#Current_ISO_3166_country_codes
+[3] RFC stages:
+https://github.com/graphql/graphql-spec/blob/main/CONTRIBUTING.md#rfc-contribution-stages
+
+
+-->
+
+| This is an open meeting: To attend, read [JoiningAMeeting.md][] then edit and PR this file. (Edit: ✎ above, or press "e") |
+| ---------------------------------------------------------------------------------------- |
+
+# Composite Schemas WG — February 2026 (Week 2)
+
+The Composite Schemas subcommittee meets weekly to progress the "Composite
+Schemas Specification" project.
+
+The first meeting each month is the primary monthly meeting; to enable a greater
+cadence of progress we also have weekly meetings which tend to be more informal.
+
+- **Date & Time**: [February 12, 2026, 6:00 – 7:00 PM GMT+1](https://www.timeanddate.com/worldclock/converter.html?iso=20260212T170000&p1=3775&p2=110&p3=24&p4=37&p5=188&p6=496&p7=676&p8=438&p9=268&p10=234&p11=78&p12=604)
+  - View the [calendar][], or subscribe ([Google Calendar][], [ical file][]).
+  - _Please Note:_ The date or time may change. Please check this agenda the
+    week of the meeting to confirm. While we try to keep all calendars accurate,
+    this agenda document is the source of truth.
+- **Video Conference Link**: https://zoom.us/j/91078840351
+  - _Password:_ composite
+- **Live Notes**: [Live Notes][]
+
+[calendar]: https://calendar.google.com/calendar/embed?src=linuxfoundation.org_ik79t9uuj2p32i3r203dgv5mo8%40group.calendar.google.com
+[google calendar]: https://calendar.google.com/calendar?cid=bGludXhmb3VuZGF0aW9uLm9yZ19pazc5dDl1dWoycDMyaTNyMjAzZGd2NW1vOEBncm91cC5jYWxlbmRhci5nb29nbGUuY29t
+[ical file]: https://calendar.google.com/calendar/ical/linuxfoundation.org_ik79t9uuj2p32i3r203dgv5mo8%40group.calendar.google.com/public/basic.ics
+[JoiningAMeeting.md]: https://github.com/graphql/composite-schemas-wg/blob/main/JoiningAMeeting.md
+[live notes]: https://docs.google.com/document/d/1hJO6U7daYvcNcQ3FBKnh3v4R256ers6M8IGyqRpY_kE/edit?usp=sharing
+
+## Attendees
+
+<!-- prettier-ignore -->
+| Name             | GitHub        | Organization       | Location              |
+| :--------------- | :------------ | :----------------- | :-------------------- |
+
+
+## Agenda
+
+1. Agree to Membership Agreement, Participation & Contribution Guidelines and Code of Conduct (1m, Host)
+   - [Specification Membership Agreement](https://github.com/graphql/foundation)
+   - [Participation Guidelines](https://github.com/graphql/graphql-wg#participation-guidelines)
+   - [Contribution Guide](https://github.com/graphql/graphql-spec/blob/main/CONTRIBUTING.md)
+   - [Code of Conduct](https://github.com/graphql/foundation/blob/master/CODE-OF-CONDUCT.md)
+   - Meetings are [published to YouTube](https://www.youtube.com/@GraphQLFoundation/videos) and we may use LLM/AI summary tools
+1. Introduction of attendees (5m, Host)
+1. Determine volunteers for note taking (1m, Host)
+1. Review agenda (2m, Host)
+1. Check for [ready for review agenda items](https://github.com/graphql/composite-schemas-wg/issues?q=is%3Aissue+is%3Aopen+label%3A%22Ready+for+review+%F0%9F%99%8C%22+sort%3Aupdated-desc) (5m, Host)
+1. Reminder: [grants available for key initiatives](https://graphql.org/community/foundation/community-grant/) (1m, Host)
diff --git a/agendas/2026/02-Feb/19-week-3.md b/agendas/2026/02-Feb/19-week-3.md
new file mode 100644
index 0000000..4288033
--- /dev/null
+++ b/agendas/2026/02-Feb/19-week-3.md
@@ -0,0 +1,118 @@
+<!--
+
+# How to join (copied directly from /JoiningAMeeting.md)
+
+Hello! You're welcome to join our subcommittee meeting and add to the agenda by
+following these three steps:
+
+1.  Add your name to the list of attendees (in alphabetical order).
+
+    - To respect meeting size, attendees should be relevant to the agenda. That
+      means we expect most who join the meeting to participate in discussion. If
+      you'd rather just watch, check out our YouTube[1].
+
+    - Please include the organization (or project) you represent, and the
+      location (including country code[2]) you expect to be located in during
+      the meeting.
+
+    - If you're willing to help take notes, add "✏️" after your name (eg. Ada
+      Lovelace ✏). This is hugely helpful!
+
+2.  If relevant, add your topic to the agenda (sorted by expected time).
+
+    - Every agenda item has four parts: 1) the topic, 2) an expected time
+      constraint, 3) who's leading the discussion, and 4) a list of any relevant
+      links (RFC docs, issues, PRs, presentations, etc). Follow the format of
+      existing agenda items.
+
+    - Know what you want to get out of the agenda topic - what feedback do you
+      need? What questions do you need answered? Are you looking for consensus
+      or just directional feedback?
+
+    - If your topic is a new proposal it's likely an "RFC 0"[3]. The barrier of
+      entry for documenting new proposals is intentionally low, writing a few
+      sentences about the problem you're trying to solve and the rough shape of
+      your proposed solution is normally sufficient.
+
+      You can create a link for this:
+
+      - As an issue against this repo.
+      - As a GitHub discussion in this repo.
+      - As an RFC document into the rfcs/ folder of this repo.
+
+3.  Review our guidelines and agree to our Spec Membership & CLA.
+
+    - Review and understand our Spec Membership Agreement, Participation &
+      Contribution Guidelines, and Code of Conduct. You'll find links to these
+      in the first agenda item of every meeting.
+
+    - If this is your first time, our bot will comment on your Pull Request with
+      a link to our Spec Membership & CLA. Please follow along and agree before
+      your PR is merged.
+
+      Your organization may sign this for all of its members. To set this up,
+      please ask operations@graphql.org.
+
+PLEASE TAKE NOTE:
+
+- By joining this meeting you must agree to the Specification Membership
+  Agreement and Code of Conduct.
+
+- Meetings are recorded and made available on YouTube[1], by joining you consent
+  to being recorded.
+
+[1] Youtube: https://www.youtube.com/channel/UCERcwLeheOXp_u61jEXxHMA [2]
+Country codes:
+https://en.wikipedia.org/wiki/List_of_ISO_3166_country_codes#Current_ISO_3166_country_codes
+[3] RFC stages:
+https://github.com/graphql/graphql-spec/blob/main/CONTRIBUTING.md#rfc-contribution-stages
+
+
+-->
+
+| This is an open meeting: To attend, read [JoiningAMeeting.md][] then edit and PR this file. (Edit: ✎ above, or press "e") |
+| ---------------------------------------------------------------------------------------- |
+
+# Composite Schemas WG — February 2026 (Week 3)
+
+The Composite Schemas subcommittee meets weekly to progress the "Composite
+Schemas Specification" project.
+
+The first meeting each month is the primary monthly meeting; to enable a greater
+cadence of progress we also have weekly meetings which tend to be more informal.
+
+- **Date & Time**: [February 19, 2026, 6:00 – 7:00 PM GMT+1](https://www.timeanddate.com/worldclock/converter.html?iso=20260219T170000&p1=3775&p2=110&p3=24&p4=37&p5=188&p6=496&p7=676&p8=438&p9=268&p10=234&p11=78&p12=604)
+  - View the [calendar][], or subscribe ([Google Calendar][], [ical file][]).
+  - _Please Note:_ The date or time may change. Please check this agenda the
+    week of the meeting to confirm. While we try to keep all calendars accurate,
+    this agenda document is the source of truth.
+- **Video Conference Link**: https://zoom.us/j/91078840351
+  - _Password:_ composite
+- **Live Notes**: [Live Notes][]
+
+[calendar]: https://calendar.google.com/calendar/embed?src=linuxfoundation.org_ik79t9uuj2p32i3r203dgv5mo8%40group.calendar.google.com
+[google calendar]: https://calendar.google.com/calendar?cid=bGludXhmb3VuZGF0aW9uLm9yZ19pazc5dDl1dWoycDMyaTNyMjAzZGd2NW1vOEBncm91cC5jYWxlbmRhci5nb29nbGUuY29t
+[ical file]: https://calendar.google.com/calendar/ical/linuxfoundation.org_ik79t9uuj2p32i3r203dgv5mo8%40group.calendar.google.com/public/basic.ics
+[JoiningAMeeting.md]: https://github.com/graphql/composite-schemas-wg/blob/main/JoiningAMeeting.md
+[live notes]: https://docs.google.com/document/d/1hJO6U7daYvcNcQ3FBKnh3v4R256ers6M8IGyqRpY_kE/edit?usp=sharing
+
+## Attendees
+
+<!-- prettier-ignore -->
+| Name             | GitHub        | Organization       | Location              |
+| :--------------- | :------------ | :----------------- | :-------------------- |
+
+
+## Agenda
+
+1. Agree to Membership Agreement, Participation & Contribution Guidelines and Code of Conduct (1m, Host)
+   - [Specification Membership Agreement](https://github.com/graphql/foundation)
+   - [Participation Guidelines](https://github.com/graphql/graphql-wg#participation-guidelines)
+   - [Contribution Guide](https://github.com/graphql/graphql-spec/blob/main/CONTRIBUTING.md)
+   - [Code of Conduct](https://github.com/graphql/foundation/blob/master/CODE-OF-CONDUCT.md)
+   - Meetings are [published to YouTube](https://www.youtube.com/@GraphQLFoundation/videos) and we may use LLM/AI summary tools
+1. Introduction of attendees (5m, Host)
+1. Determine volunteers for note taking (1m, Host)
+1. Review agenda (2m, Host)
+1. Check for [ready for review agenda items](https://github.com/graphql/composite-schemas-wg/issues?q=is%3Aissue+is%3Aopen+label%3A%22Ready+for+review+%F0%9F%99%8C%22+sort%3Aupdated-desc) (5m, Host)
+1. Reminder: [grants available for key initiatives](https://graphql.org/community/foundation/community-grant/) (1m, Host)
diff --git a/agendas/2026/02-Feb/26-week-4.md b/agendas/2026/02-Feb/26-week-4.md
new file mode 100644
index 0000000..24b6230
--- /dev/null
+++ b/agendas/2026/02-Feb/26-week-4.md
@@ -0,0 +1,118 @@
+<!--
+
+# How to join (copied directly from /JoiningAMeeting.md)
+
+Hello! You're welcome to join our subcommittee meeting and add to the agenda by
+following these three steps:
+
+1.  Add your name to the list of attendees (in alphabetical order).
+
+    - To respect meeting size, attendees should be relevant to the agenda. That
+      means we expect most who join the meeting to participate in discussion. If
+      you'd rather just watch, check out our YouTube[1].
+
+    - Please include the organization (or project) you represent, and the
+      location (including country code[2]) you expect to be located in during
+      the meeting.
+
+    - If you're willing to help take notes, add "✏️" after your name (eg. Ada
+      Lovelace ✏). This is hugely helpful!
+
+2.  If relevant, add your topic to the agenda (sorted by expected time).
+
+    - Every agenda item has four parts: 1) the topic, 2) an expected time
+      constraint, 3) who's leading the discussion, and 4) a list of any relevant
+      links (RFC docs, issues, PRs, presentations, etc). Follow the format of
+      existing agenda items.
+
+    - Know what you want to get out of the agenda topic - what feedback do you
+      need? What questions do you need answered? Are you looking for consensus
+      or just directional feedback?
+
+    - If your topic is a new proposal it's likely an "RFC 0"[3]. The barrier of
+      entry for documenting new proposals is intentionally low, writing a few
+      sentences about the problem you're trying to solve and the rough shape of
+      your proposed solution is normally sufficient.
+
+      You can create a link for this:
+
+      - As an issue against this repo.
+      - As a GitHub discussion in this repo.
+      - As an RFC document into the rfcs/ folder of this repo.
+
+3.  Review our guidelines and agree to our Spec Membership & CLA.
+
+    - Review and understand our Spec Membership Agreement, Participation &
+      Contribution Guidelines, and Code of Conduct. You'll find links to these
+      in the first agenda item of every meeting.
+
+    - If this is your first time, our bot will comment on your Pull Request with
+      a link to our Spec Membership & CLA. Please follow along and agree before
+      your PR is merged.
+
+      Your organization may sign this for all of its members. To set this up,
+      please ask operations@graphql.org.
+
+PLEASE TAKE NOTE:
+
+- By joining this meeting you must agree to the Specification Membership
+  Agreement and Code of Conduct.
+
+- Meetings are recorded and made available on YouTube[1], by joining you consent
+  to being recorded.
+
+[1] Youtube: https://www.youtube.com/channel/UCERcwLeheOXp_u61jEXxHMA [2]
+Country codes:
+https://en.wikipedia.org/wiki/List_of_ISO_3166_country_codes#Current_ISO_3166_country_codes
+[3] RFC stages:
+https://github.com/graphql/graphql-spec/blob/main/CONTRIBUTING.md#rfc-contribution-stages
+
+
+-->
+
+| This is an open meeting: To attend, read [JoiningAMeeting.md][] then edit and PR this file. (Edit: ✎ above, or press "e") |
+| ---------------------------------------------------------------------------------------- |
+
+# Composite Schemas WG — February 2026 (Week 4)
+
+The Composite Schemas subcommittee meets weekly to progress the "Composite
+Schemas Specification" project.
+
+The first meeting each month is the primary monthly meeting; to enable a greater
+cadence of progress we also have weekly meetings which tend to be more informal.
+
+- **Date & Time**: [February 26, 2026, 6:00 – 7:00 PM GMT+1](https://www.timeanddate.com/worldclock/converter.html?iso=20260226T170000&p1=3775&p2=110&p3=24&p4=37&p5=188&p6=496&p7=676&p8=438&p9=268&p10=234&p11=78&p12=604)
+  - View the [calendar][], or subscribe ([Google Calendar][], [ical file][]).
+  - _Please Note:_ The date or time may change. Please check this agenda the
+    week of the meeting to confirm. While we try to keep all calendars accurate,
+    this agenda document is the source of truth.
+- **Video Conference Link**: https://zoom.us/j/91078840351
+  - _Password:_ composite
+- **Live Notes**: [Live Notes][]
+
+[calendar]: https://calendar.google.com/calendar/embed?src=linuxfoundation.org_ik79t9uuj2p32i3r203dgv5mo8%40group.calendar.google.com
+[google calendar]: https://calendar.google.com/calendar?cid=bGludXhmb3VuZGF0aW9uLm9yZ19pazc5dDl1dWoycDMyaTNyMjAzZGd2NW1vOEBncm91cC5jYWxlbmRhci5nb29nbGUuY29t
+[ical file]: https://calendar.google.com/calendar/ical/linuxfoundation.org_ik79t9uuj2p32i3r203dgv5mo8%40group.calendar.google.com/public/basic.ics
+[JoiningAMeeting.md]: https://github.com/graphql/composite-schemas-wg/blob/main/JoiningAMeeting.md
+[live notes]: https://docs.google.com/document/d/1hJO6U7daYvcNcQ3FBKnh3v4R256ers6M8IGyqRpY_kE/edit?usp=sharing
+
+## Attendees
+
+<!-- prettier-ignore -->
+| Name             | GitHub        | Organization       | Location              |
+| :--------------- | :------------ | :----------------- | :-------------------- |
+
+
+## Agenda
+
+1. Agree to Membership Agreement, Participation & Contribution Guidelines and Code of Conduct (1m, Host)
+   - [Specification Membership Agreement](https://github.com/graphql/foundation)
+   - [Participation Guidelines](https://github.com/graphql/graphql-wg#participation-guidelines)
+   - [Contribution Guide](https://github.com/graphql/graphql-spec/blob/main/CONTRIBUTING.md)
+   - [Code of Conduct](https://github.com/graphql/foundation/blob/master/CODE-OF-CONDUCT.md)
+   - Meetings are [published to YouTube](https://www.youtube.com/@GraphQLFoundation/videos) and we may use LLM/AI summary tools
+1. Introduction of attendees (5m, Host)
+1. Determine volunteers for note taking (1m, Host)
+1. Review agenda (2m, Host)
+1. Check for [ready for review agenda items](https://github.com/graphql/composite-schemas-wg/issues?q=is%3Aissue+is%3Aopen+label%3A%22Ready+for+review+%F0%9F%99%8C%22+sort%3Aupdated-desc) (5m, Host)
+1. Reminder: [grants available for key initiatives](https://graphql.org/community/foundation/community-grant/) (1m, Host)
diff --git a/notes/2025/summary-2025-10-30.md b/notes/2025/summary-2025-10-30.md
new file mode 100644
index 0000000..94eff49
--- /dev/null
+++ b/notes/2025/summary-2025-10-30.md
@@ -0,0 +1,63 @@
+# Meeting Summary for Composite Schemas WG
+
+**NOTICE**: This summary was auto-generated by Zoom's "AI". AI-generated
+content may be inaccurate or misleading. Always check for accuracy. If in
+doubt, please consult the meeting recording at
+https://youtube.com/@GraphQLFoundation/playlists
+
+- Meeting start: 2025-10-30T16:57:45Z
+- Meeting end: 2025-10-30T17:20:55Z
+- Summary start: 2025-10-30T17:02:01Z
+- Summary end: 2025-10-30T17:20:54Z
+
+The meeting began with discussions about time zone switches and introductions, followed by reminders about GraphQL specification requirements and documentation guidelines. The team then focused on various technical discussions including enum merging, validation rules, and error code standardization, with particular attention given to removing abbreviations and improving clarity in error messages. The conversation ended with updates on pull request merges and algorithm simplification efforts, with Pascal noting the efficient 10-minute introduction.
+
+## Next Steps
+
+- Pascal and team: Collect examples of different enum merging rules and combinations to explain to users simply and get everyone on the same page
+- Pascal and team: Replace all instances of "arc" abbreviation with "argument" in error codes throughout the specification
+- Pascal and team: Review and replace any other abbreviations found in error codes with full words
+- Pascal and team: Generalize field and argument reference validation rules to have only two rules: "reference to inaccessible type" and "reference to internal type
+- Team members: Review and comment on algorithmic pull requests for validation rules  before they are merged
+
+## Summary
+
+### GraphQL Spec Meeting Overview
+
+The meeting began with a discussion about time zone switches, with Michael confirming that Europe had switched the previous week and waiting for another switch to occur the following Sunday. Pascal and Kamil briefly interacted in what appeared to be a mix of English and another language, discussing something about copying machines. Michael then led the meeting, reminding attendees about the GraphQL spec membership agreements, participation guidance, Code of Conduct, and contribution guide. He also mentioned that the meeting sessions would be uploaded to YouTube and that they were using LMM for summarization. The conversation ended with Michael introducing himself and noting that Martine was absent.
+
+### Validation Rules Discussion Summary
+
+Pascal raised a question about validation rules, particularly regarding granularity and similarity, which Michael noted for discussion. The conversation ended with no additional agenda items, and Pascal was invited to elaborate on the rules topic.
+
+### Enum Merging Rules Discussion
+
+The team discussed the status of enum merging, with Pascal noting they need to collect examples to better understand the merging rules and create clear user instructions. Michael confirmed they have Sasheen's proposal and are working on validation routes through pull requests, though the exact approach for including the proposal in the Composite schema remains to be determined.
+
+### Validation Rules Naming Convention Update
+
+Pascal and Michael discussed the finalization of a version 1 document, with a focus on addressing inconsistencies in the naming of validation rules. They agreed to align the naming convention by replacing underscores with full written words, as proposed in a Slack channel. The task was deemed easy to implement and would ensure consistency between the specification and code.
+
+### Error Code Standardization Discussion
+
+The team discussed changing error codes from Apollo Federation, deciding to use full words instead of abbreviations for better clarity. Michael explained the need to replace "arc" with "argument" in error codes, which Derek and Sachin supported. Pascal pointed out inconsistencies in the current error codes, such as using "arc" and "in field" in different contexts, and the team agreed to replace all abbreviations with full words.
+
+### Error Code Abbreviation Standardization
+
+The team discussed removing abbreviations from error codes for clarity and consistency. Derek and Sachin agreed that abbreviations should be avoided unless error codes become excessively long, in which case a shorter name might be considered. Michael noted that this was an opportunity to standardize error code naming that had previously been inconsistent.
+
+### Type Reference Rules Consolidation Discussion
+
+Pascal discussed the need to clarify and potentially consolidate rules related to field and argument references to inaccessible and internal types. He presented two options: generalizing the rules into broader categories or expanding them to account for specific locations where these types might occur. Pascal sought input on the direction to take, emphasizing the importance of making these rules meaningful and effective.
+
+### Error Message Clarity Discussion
+
+Michael and Pascal discussed the clarity of error messages in their system, particularly regarding coordinates and input/output types. Pascal pointed out that coordinates alone do not clearly indicate whether they are input or output types, which Michael acknowledged. They also touched on the current use of error codes in their system, with Pascal asking about the specific circumstances under which these codes are used.
+
+### Schema Error Code Standardization
+
+The team discussed error codes for schema accessibility, with Sachin explaining that while contracts can mark things inaccessible, there isn't a way to automatically mark things accessible through regular composition. Pascal inquired about the possibility of different error codes for different behaviors, but Sachin suggested that having one error code for all schemas might be more practical given the complexity of schema references. Derek noted that error messages typically include type information before the coordinate, and suggested that while the code could be generic, additional information could be included in the message if needed.
+
+### Algorithm Simplification and Validation Discussion
+
+The team discussed finalizing rules and algorithms, with Pascal mentioning they are simplifying to two main rules for easier validation. Michael reported merging small pull requests that addressed inconsistent examples and invited others to comment on algorithmic work, noting that pull requests can be reopened if issues are spotted. The conversation ended ahead of schedule, with Pascal acknowledging the 10-minute introduction.