GeezerVison

Requested by David Soria Parra · Slack thread

Follow-up to #3513. Follows #3544.

Before: The Core Primitives WG has leads, a repository and a weekly meeting. It has no charter page, nav entry or Current groups line.

After: The group has a charter built from the charter template with only sourced content, a nav entry under Working Groups, and a Current groups line. Sections with no source say "To be confirmed" or "To be defined by the leads". Membership is omitted, as the template allows until the group has members. The overview row now links the charter.

Sources

• Mission and In Scope: the group's three problem statements, which David pointed to in review and in the Slack thread. The tool result shape statement is under review in docs: add tool result shape problem statement core-primitives-wg#2. The stability and audience statements are working documents and are not linked here. The primitive annotations item and the open-scope statement come from the roadmap (roadmap.mdx L65-L77, L22).
• Out of Scope: progressive discovery is handled by the Progressive Disclosure WG, per David's review comment.
• Related Groups: the File Uploads WG line in the same priority area (L77) and the progressive discovery item (L74), now handled by the Progressive Disclosure WG.
• Leads: the core-primitives-wg-leads team in Access (roles.ts L418-L428) with members kurtisvg and dsp-ant, added by Add Core Primitive Working Group access#172 and Add Core Primitives Working Group repository and leads team access#234.
• Organizations: Google for Kurtis from the Progressive Disclosure charter (docs/community/working-groups/progressive-disclosure.mdx, line 70), Anthropic for David from the Server Card charter (docs/community/working-groups/server-card.mdx, line 38).
• Operations: the weekly 60 minute meeting on the community calendar, the core-primitives-wg repository, and the Discord channel that the calendar events link. The Discord API returns the name core-primitives-wg for that channel id.
• Authority & Decision Rights: the template default table in docs/community/charter-template.mdx, unchanged.
• Active Work Items: the three current focus items. Status and champion for shape and stability come from the status and contributor lines of their problem statements. The audience statement names neither. No source gives target dates.
• Overview row: the row added by docs(community): list Core Primitives WG on working groups overview #3544 now links the charter.

Questions for @kurtisvg and @dsp-ant

1. Mission: the wording here paraphrases the roadmap. chore: bootstrap Core Primitives WG repository core-primitives-wg#1 is open and proposes a README sentence. Confirm this wording or replace it?
2. Progressive discovery: answered in review. It is out of scope and handled by the Progressive Disclosure WG.
3. Extra scope: partly answered in review. Tool Result Stability and Tool Result Audience are now in scope. Two points remain. The notes also list Resource Link Traversal with no owner. Is it in scope? Primitive annotations stays in scope as a roadmap item outside the current focus. Keep it there or remove it?
4. Out of Scope: partly answered in review. Progressive discovery is listed. Does anything else belong there?
5. Members: Access lists only the two leads. chore: bootstrap Core Primitives WG repository core-primitives-wg#1 proposes Kyle Rubenok, Luca Chang and Kryspin Ziemski. Who are the members, with organization, Discord handle and level?
6. Leadership: no source gives the lead terms. What are they?
7. Sponsorship: the template requires the group to be sponsored under "Forming a group" in docs/community/working-interest-groups.mdx. Who sponsored it?
8. Operations: is there an Office Hours slot, and should the charter link the meeting notes document?
9. Work items: status and champion for shape and stability now come from the problem statements. Who champions the audience item, and what are the SEP numbers and target dates? The notes say "March Spec" for most items. For success criteria, the notes list a definition of done: SEP, reference implementation, guidance and documentation updates.
10. Authority table: it is the template default. Should any row change?
11. Naming: Access spells the member role singular (core-primitive-wg, from Add Core Primitive Working Group access#172) and every other source is plural. Should Access be renamed?

This PR was drafted with AI assistance (Claude Code).