Establish OSS Committee Charter

[michaeloboyle]

Purpose

Establish the OSS Committee Charter: the durable statement of the committee's mission, scope, membership, voting model, and chair responsibilities. This is container #5 (Committee Operating Guidelines) in the scope-boundary model.

Context

• May 20 OSS meeting action item. Chair: @michaeloboyle.
• Per the governance-as-code principle (adopted 2026-05-13), the charter lives in this repo as version-controlled markdown, amended via PR, not as a Google Doc.
• Distinct from the OSS Intake Process (container Add open source project intake system #4, PR Add open source project intake system (supersedes #4) #6) and the Laws of Agentics / AF Manifesto (containers What's the best way to share secrets into an agentics environment? #1 and New issue created in 'Community Project' #2).

Scope of the charter

• Mission and scope boundary: what the committee governs and what it does not.
• Membership and the chair role.
• Voting model: escalation vote, then validation vote, simple majority (50%+1).
• Conflict-of-interest and recusal mechanics: submitter-exclusion (mechanical) and /coi (voluntary).
• Decision-recording convention: when a decision is an AF-GOV doc, an ADR, or a tracking issue.

Acceptance criteria

• Charter drafted as docs/operating-guidelines/committee-charter.md with author and maintainer frontmatter and @Handles.
• Reviewed by committee.
• Ratified via PR merge.

References

• Scope boundary: five containers (2026-05-13).
• Governance-as-code principle (2026-05-13).

[michaeloboyle]

Should flow from what's established here: https://github.com/agenticsorg/.github/blob/main/profile/README.md