improve mission statement

[meonkeys]

Summary

• update high-level mission statement in MISSION.md

Type of change

• Skill change (.claude/skills/<name>/) — eval fixtures updated below
• Tool / bridge contract (tools/<system>/*.md)
• Python package (tools/*/ with pyproject.toml)
• Groovy reference impl
• Cross-cutting (RFC, AGENTS.md, sandbox, privacy-LLM)
• Documentation (docs/, README.md, CONTRIBUTING.md)
• Project template (projects/_template/)
• CI / dev loop (prek, workflows, validators)
• Other:

No headers changed so I did not run doctoc.

Test plan

not applicable

RFC-AI-0004 compliance

not applicable, AFAICT

Linked issues

None. This is a drive-by PR but I'll stick around to absorb feedback, discuss, improve, etc.

Notes for reviewers (optional)

I joined the #magpie Slack channel in case you want to ping me in there. My handle is meonkeys in there as well.

[meonkeys]

Ah hmm... I skipped right past that important NOTE right above the text I changed.

I guess I'd still recommend changing the mission unless my patch somehow invalidates original commitments of the project, and remove the NOTE. It's just noise. If someone wants to plumb history, the original text will always and forever be in the git history.

As for the IMPORTANT/motto... how about making that the project's vision? What do you think?

[justinmclean]

Thanks for the PR. You've spotted a real problem: the duplicated "creation and maintenance of software related to" is a transcription error and needs fixing.

The replacement text doesn't quite work though. The Mission section mirrors the board resolution that established the project, so the wording isn't ours to change by PR, and "high-quality recipes" is marketing language rather than charter language. The enumerated scope (triage, mentoring, remediation, fix-and-merge automation) also matters here, as it bounds the scope of agent automation the project covers.

Could you revise it to remove the duplicate phrase and keep the rest as is? Your two-sentence plain-English description is good and would fit well in the README instead.

[meonkeys]

I removed the dup phrase and kept the rest as-is, but as you can see it ends in an incomplete sentence.

Do you have a copy of the original charter text? I found this press release and that uses different wording as well.

I'll update the README now.

[meonkeys]

as you can see it ends in an incomplete sentence

I'll just add a period. 😅

[meonkeys]

LMK what you think of this version. Honestly I still don't love the mission text, it sounds oddly, creatively worded. I've never heard of "maintainership" nor "narrowly-scoped fix-and-merge automation". 🤷

[justinmclean]

Thank for the changes