Update program-structure.md

[SovereignSignal]

Description

I have removed Kubesqrt and added Sov (me!) to the list of Grants Committee. Everything else on this page looks correct.

Changes

• @Kubesqrt
• @Sov

Summary by CodeRabbit

• Documentation
  • Updated the Grants Committee roster in the governance docs: replaced Kubesqrt with Sov.
  • Updated the linked forum profile to Sov’s summary page.
  • No other content or structure changes.

[vercel]

@SovereignSignal is attempting to deploy a commit to the cow Team on Vercel.

A member of the Team first needs to authorize it.

[coderabbitai]

Walkthrough

Updated a documentation page to replace one community member in the Grants Committee list: changed “Kubesqrt” (link to /u/kubesqrt) to “Sov” (link to /u/sov/summary). No other edits.

Changes

Cohort / File(s)	Summary of changes
Docs: Grants Committee member update docs/governance/grants/program-structure.md	Replaced “Kubesqrt” with “Sov” in the 3 Community Members list; updated profile link to https://forum.cow.fi/u/sov/summary from https://forum.cow.fi/u/kubesqrt.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Pre-merge checks (2 passed, 1 inconclusive)

❌ Failed checks (1 inconclusive)

Check name	Status	Explanation	Resolution
Title Check	❓ Inconclusive	The title "Update program-structure.md" identifies the file changed but is overly generic and does not summarise the PR's main substantive change (removing Kubesqrt and adding Sov to the Grants Committee), so it does not clearly convey intent to a reviewer scanning history. Because it names the file rather than the action, the title is ambiguous about whether this is a minor docs tweak or a membership update. This makes the title inconclusive relative to the repository guideline to highlight the most important change.	Please update the title to a short, specific summary of the change, for example "Replace Kubesqrt with Sov on Grants Committee" or "Add Sov to Grants Committee (replace Kubesqrt)"; alternatively use "program-structure.md: add Sov to Grants Committee" if you want the filename included. A clearer title will make the PR intent obvious in history and speed review.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Description Check	✅ Passed	The PR description includes the required "# Description" and "# Changes" sections and clearly states that Kubesqrt was removed and Sov added to the Grants Committee, with links to both profiles, so the core information is present and reviewable. The "Changes" list uses plain list items rather than the template's checklist format and could also include a one-line rationale or a related issue reference for traceability. Overall the description is mostly complete and meets the repository template's intent.
Docstring Coverage	✅ Passed	No functions found in the changes. Docstring coverage check skipped.

Poem

A whisk of words, a nimble hop,
I tweak the roll, then softly stop—
Sov steps in, the list aligned,
Carrot-ink signatures neatly signed.
Patch applied, tail flick—done!
Docs refreshed beneath the sun. 🥕✨

Tip

👮 Agentic pre-merge checks are now available in preview!

Pro plan users can now enable pre-merge checks in their settings to enforce checklists before merging PRs.

• Built-in checks – Quickly apply ready-made checks to enforce title conventions, require pull request descriptions that follow templates, validate linked issues for compliance, and more.
• Custom agentic checks – Define your own rules using CodeRabbit’s advanced agentic capabilities to enforce organization-specific policies and workflows. For example, you can instruct CodeRabbit’s agent to verify that API documentation is updated whenever API schema files are modified in a PR. Note: Upto 5 custom checks are currently allowed during the preview period. Pricing for this feature will be announced in a few weeks.

Please see the documentation for more information.

Example:

reviews:
  pre_merge_checks:
    custom_checks:
      - name: "Undocumented Breaking Changes"
        mode: "warning"
        instructions: |
          Pass/fail criteria: All breaking changes to public APIs, CLI flags, environment variables, configuration keys, database schemas, or HTTP/GraphQL endpoints must be documented in the "Breaking Change" section of the PR description and in CHANGELOG.md. Exclude purely internal or private changes (e.g., code not exported from package entry points or explicitly marked as internal).

Please share your feedback with us on this Discord post.

✨ Finishing touches

🧪 Generate unit tests

• Create PR with unit tests
• Post copyable unit tests in a comment

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[github-actions]

Thank you for your submission, we really appreciate it. Like many open-source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution. You can sign the CLA by just posting a Pull Request Comment same as the below format.

---

I have read the CLA Document and I hereby sign the CLA

---

_{You can retrigger this bot by commenting recheck in this Pull Request. Posted by the CLA Assistant Lite bot.}

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (2)

docs/governance/grants/program-structure.md (2)

13-13: Use profile root URL (drop /summary) for consistency with other handles.

Other entries link to the forum profile root; align Sov’s link the same way.

-  - [@Sov](https://forum.cow.fi/u/sov/summary)
+  - [@Sov](https://forum.cow.fi/u/sov)

---

12-15: Optional: Alphabetize the community member list to reduce future diff churn.

Keeps ordering stable and predictable over time.

-  - [@Sov](https://forum.cow.fi/u/sov)
-  - [@Chim9](https://forum.cow.fi/u/chim9)
-  - [@mfw78](https://forum.cow.fi/u/mfw78)
+  - [@Chim9](https://forum.cow.fi/u/chim9)
+  - [@mfw78](https://forum.cow.fi/u/mfw78)
+  - [@Sov](https://forum.cow.fi/u/sov)

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between ed5e235 and 8d7b633.

📒 Files selected for processing (1)

• docs/governance/grants/program-structure.md (1 hunks)

🔇 Additional comments (1)

docs/governance/grants/program-structure.md (1)

11-16: Add governance decision record or revert committee change in docs/governance/grants/program-structure.md (lines 11–16).

Sov is listed as selected in public records (application and H1 2025 review) but there’s no public forum/Snapshot announcement removing Kubesqrt — add the authoritative decision link that ratifies Kubesqrt’s removal or revert the doc to retain Kubesqrt until a ratifying record is provided.

[blacktieaccountant]

Agree with changes. No other relevant changes needed.