routines(meet-filer): file Regen Commons calls to the Regen Commons drive

[Oba-One]

What

Rule 23 in routines/claude/meet-filer.md matches ^Regen Commons and pointed at 1Rr1xv4p…, which is Regen Coordination SD / Council. That is the wrong shared drive. Its own label admitted it.

It now points at 1XpYDQcJ…, Regen Commons SD / Council / Meetings, where the Council Call and Steward Jam history already lives.

-    { "order": 23, "regex": "^Regen Commons", "targetFolderId": "1Rr1xv4pWMflMY1OTMfd79yxZzNfQ6t0T", ...
+    { "order": 23, "regex": "^Regen Commons", "targetFolderId": "1XpYDQcJuhSFdXuBRfEO4KTPykKy4nFAd", ...

Why it went unnoticed

The Regen Commons drive did not get its Council/Meetings folder until 2026-08-20. Before that the rule's target was a reasonable stand-in. The folder was created and the July and Aug 6 artifacts were swept into it by hand, but the rule was never updated, so the routine kept filing new calls into Coordination.

Blast radius

Rule 23 also matches Regen Commons | Steward Jam. That is correct: every existing Steward Jam file is already in the same Council/Meetings folder, so both meetings converge on the right destination.

Rule 18 (^Regen Coordination Council Sync) is untouched and still routes the genuine Coordination series to the Coordination drive. Verified no earlier rule shadows ^Regen Commons for a Council Call filename, and the config block still parses (31 rules).

Not covered by this PR

Ten already-misfiled files (2026-08-13, 08-27, 09-03, 09-10 notes/chat/recording) are sitting in Regen Coordination › Council. They are outside the routine's sourceLock (Google Meet/** + Meet Recordings/** + Review/**), so meet-filer will never pick them up. They need a manual move in the Drive UI.

🤖 Generated with Claude Code

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Advanced

Run ID: 8315619a-e326-45b6-a449-5908a7aab527

📥 Commits

Reviewing files that changed from the base of the PR and between eba6bb7 and 22f621f.

📒 Files selected for processing (1)

• routines/claude/meet-filer.md

Included review availability: Your plan provides up to 1 included review per hour; 0 remain after this review.

📜 Recent review details

⏰ Context from checks skipped due to timeout. (1)

• GitHub Check: Analyze (javascript-typescript)

🧰 Additional context used

📓 Path-based instructions (4)

Do not reintroduce the former dev-guild PM URL or old migration language for project-management state

📄 CodeRabbit inference engine (AGENTS.md)

Files:

• routines/claude/meet-filer.md

Search for and retire stale terms: `app.charmverse.io`, `greenpill.network/dev-guild`, `FOMO`, `virality`, `leaderboards`, `streaks`, `AI-first`, former dev-guild PM URL, retired funded-work file names, old GitHub grant lifecycle labels, an...

📄 CodeRabbit inference engine (CLAUDE.md)

Files:

• routines/claude/meet-filer.md

Do not introduce guild-wide Season framing in documentation Do not describe the dev guild as the entire Greenpill Network in documentation Avoid growth-hacking and trend-chasing voice in documentation: no FOMO, virality, leaderboards, strea...

📄 CodeRabbit inference engine (AGENTS.md)

Files:

• routines/claude/meet-filer.md

Link to the issue-creation flow in docs that ask someone to "open" an issue or RFC, not just the source template file

📄 CodeRabbit inference engine (CLAUDE.md)

Files:

• routines/claude/meet-filer.md

🔇 Additional comments (1)

routines/claude/meet-filer.md (1)

194-194: LGTM!

---

📝 Summary

Summary by CodeRabbit

• Updates
  • Files matching “Regen Commons” are now routed to the Regen Commons SD / Council / Meetings shared drive.
  • Updated routing information clarifies that the destination is a different shared drive.

Walkthrough

Rule 23 for ^Regen Commons now routes files to Regen Commons SD / Council / Meetings. Its label identifies the destination as a different shared drive.

Changes

Meet filer routing

Layer / File(s)	Summary
Update Rule 23 destination routines/claude/meet-filer.md	Rule 23 now uses the Regen Commons meetings folder ID and updated shared-drive label.

Priority: ⬇️ Low

Estimated code review effort: 1 (Trivial) | ~2 minutes

Change: Bug fix

Merge Risk: ⚪ Minimal · up to 22f62

Future Regen Commons meeting files will be routed to the intended shared-drive folder. Previously misfiled files require separate manual relocation but do not block this change.

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly and concisely describes the main change: filing Regen Commons calls to the Regen Commons drive.
Description check	✅ Passed	The description directly explains the Rule 23 routing change, its scope, validation, and excluded manual cleanup.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0…
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch fix/meet-filer-regen-commons-target

---

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

_{A rabbit checks the meeting trail
Regen Commons hops past the old rail
The shared drive path is clear
Council meetings gather here
Rule 23 now lands without fail}

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