Develop candidate pool for first consideration

Purpose

Assemble the initial pool of projects to run through the OSS intake process as the committee's first formal considerations once the intake system (PR #6) merges.

Candidates

1. OIA-Model: agenticsorg/OIA-Model

• Maintainer: @nicholas-ruest
• Already under the agenticsorg org (Owned track). Shipped to production 2026-04-22.
• Member-as-submitter pattern: @nicholas-ruest would submit; submitter-exclusion auto-recuses him from voting on it.

2. Video Sync: mrjcleaver/video-sync

• Maintainer: @mrjcleaver
• AF-purposed video indexing and publishing pipeline (Zoom, Fireflies, Loom, YouTube, Kaltura). Live at video-sync.agentics.org, gated by Google Cloud IAP, built on AF infrastructure (Cloud Run, Workspace).
• Foundation-track candidate. Tier depends on #10.

3. Summary Bot NG: summarybotng/summarybot-ng

• Maintainer: @mrjcleaver
• Discord bot that generates AI-powered conversation summaries (Claude via OpenRouter).
• Already submitted as a donation in the fork pilot (michaeloboyle/community-projects #33, 2026-05-20). Governance-agent predicted score 15 to 23/25, average 19.

Why these three

They exercise three distinct intake paths: Foundation-owned (OIA-Model), Foundation-track tool (Video Sync), and donation (Summary Bot NG). Running all three validates the pipeline across the categories it must handle, rather than testing one path repeatedly.

Acceptance criteria

• Confirm each maintainer is willing to submit.
• Assign tier to each (after #10 defines tiers).
• Run each through intake once PR #6 merges.

References

• Tier definitions: #10
• Fork pilot: Summary Bot NG donation, michaeloboyle/community-projects #33.

Read PR #6 to understand the intake system and issue #10 for the tier definitions. Confirm willingness with the three listed maintainers, assign each candidate a tier, and run all three through intake after PR #6 merges.