Organization-level management

[Happypig375]

Right now, you only make progress on AngouriMath repo itself and other repos go stale, e.g. Mcp and website.

Consider spawning some agents to make progress on other repos too, with an organization-level project.

Some organization-wide standardization of e.g. label and milestone use might also be desirable.

Here are the repos:

• AngouriMath
• AngouriMathSite
• AngouriMathMCP
• AngouriMathCLI
• AngouriMathLab (maybe archive this one)
• AngouriMathBot

It is also possible that repo separation like this is unwieldy and same repo (e.g. gh-pages branch for website) may be considered. But this is really about how you want to do things.

[Happypig375]

Specifically, the website really needs a design for 2026, something shaped more playfully like Desmos would communicate what we do fully (the capabilities of a Math OS need not be shaped like a library - no one cares about a C# library in 2026 when AI reads everything nowadays - think about Wolfram Alpha and Desmos). This would become a project of itself.

With proper designing, we have something way more powerful and fun compared to Desmos here, because Desmos is really just a graphing calculator which we can also just replicate with a plotter. How we want to invoke C# from the web is another question though - WASM is possible, but a mobile connection might not perform well.

It might not be desirable to start this before v3 as we have a lot of redesigning of AngouriMath for v3.

[Rafael-SOWNet]

Where each repository stands today:

repository	last commit	open issues / PRs	state
AngouriMath	today	86 / 1	active
AngouriMathSite	2026-08-12	5 / 1	What's new stops at 2.1.0, and the library is at 2.5.0
AngouriMathMCP	2026-08-12	0 / 0	pinned to AngouriMath 2.1.0
AngouriMathCLI	2024-11-24	3 / 2	idle
AngouriMathLab	2022-06-13	4 / 0	the Terminal still releases here (TerminalNightly.yml)
AngouriMathBot	2020-08-12	1 / 0	a Discord bot

What I'd do:

1. One organization project, with a Repository field, so the backlog across repositories is one view. My credential cannot create it yet: that needs a project permission, which I've asked for.
2. Issue types, not labels, for what an issue is. AngouriMath already uses the organization's issue types (Bug, Feature, Maintenance, Goal). The other five still carry GitHub's default labels (bug, enhancement, …), which duplicate those types. I'd move them to the types and keep labels for what types don't say: Area: …, Accepted, Opinions wanted, Design document.
3. Milestones follow the library's version, as the Terminal's version now does (The Terminal is released with the packages, under their version #1541). MCP and the site get a 2.6.0 milestone alongside the library's.
4. Per repository:
   • MCP moves to the current package and exposes what 2.2 to 2.6 added.
   • The site gets What's new for 2.2 to 2.6, and docsamples keeps its quickstart true. The redesign you describe is a project of its own, after v3 as you say.
   • Lab is archived once the Terminal's builds are attached to the AngouriMath release itself, which The Terminal is released with the packages, under their version #1541 already triggers.
   • The Bot is archived.
   • The CLI overlaps the Terminal, so one of the two should go.
5. Separate repositories: I'd keep MCP and the CLI separate, as separate products with separate releases and aligned versions. I'd fold the site into a gh-pages branch here only if its build stays light. The gain is that a documentation change and the code it documents land in one PR.

Separate agents per repository are Rafael's to start. With the project in place, each would take its items from there.

Does that order suit you? I can start on 3 and on MCP's package move now, since neither needs anything new.

[Rafael-SOWNet]

Progress on the two stalest repositories:

• MCP is on 2.5.0 (Move to AngouriMath 2.5.0 AngouriMathMCP#1, merged). Re-probing the grammar found 18 spellings it had accepted since at least 2.1.0, such as asin, sh and arcoth, on which the server warned "unknown function" for correct input. Five more are new in 2.2–2.5: card, sum, product, argmax and argmin. Two documented library defects no longer reproduce and left its docs. The integral of x^4(1-x)^4/(1+x^2) over [0, 1], exactly 22/7 - pi, is now one of its selftest identities.
• The site: What's new: 2.2.0 to 2.5.0, and the quickstart names 2.5.0 AngouriMathSite#33 (What's new up to 2.5.0) had been waiting on your question about the .NET Fiddles since 2026-09-16. I've answered it there: every demo fiddle is pinned to 1.2.0 or 1.3.0-preview.3. I also opened a / b -> a * b ^ (-1) simplification is inconsistent #34 before noticing pi should LaTeXize to \pi #33, and closed it.

I now sweep the other five repositories' threads along with this one's.

[Happypig375]

CLI and Terminal can be combined, yes

[Happypig375]

Tell me the project specifications and I'll make one for you

[Rafael-SOWNet]

The CLI and the Terminal. The Terminal's dotnet tool already installs as amcli, which is the CLI's command, so combining them gives one amcli:

• With no arguments, it opens the Terminal, as it does today.
• amcli simp "…" runs the CLI's one-shot command, and so do eval, diff, solve, latex, fsimp and sub. Each reads the expression from stdin when the argument is left out.

The one-shot path calls the library directly and doesn't start the F# Interactive kernel, which is what makes the Terminal slow to open. The CLI is GPL-3.0 and this repository is MIT, so I'd write the seven commands fresh in Sources/Terminal rather than move WhiteBlackGoose's code. Each is a single call to the library. The CLI's three open issues (a man page, bash completion and packages) would then move here, and AngouriMathCLI would be archived with a pointer.

The project. Here is the specification:

• Name: AngouriMath. Visibility: public.
• Items: open issues and PRs from AngouriMath, AngouriMathSite, AngouriMathMCP, AngouriMathCLI and AngouriMathLab. The Bot is left out.
• Fields: the built-in ones are enough: Status, Repository, Type, Milestone, Labels, Linked pull requests, Parent issue and Sub-issues progress.
• Status: Todo, In progress, In review, Waiting on maintainer, Done. "Waiting on maintainer" is meant for what is waiting on you, so you can find it in one place rather than across threads. Today that is Dividing by a reciprocal gives a value where the quotient has none: 1/(1/x) is x #1648, SoundUnderAssumptions names no assumption: 177 rules declare it and the condition exists only in comments #1252 and the Nothing writes an expression as a single quotient: no together / ratsimp #1239 question.
• Views:
  • a board by Status;
  • a table grouped by Repository;
  • a table grouped by Milestone, with every repository's milestones named after the library's version.
• Workflows:
  • auto-add for each repository's open issues and PRs, as many repositories as the plan allows;
  • closed or merged → Done;
  • reopened → Todo.

Adding items and moving them needs my token to have the project scope, and I've asked Rafael for it.

[Happypig375]

Well yea you not being able to move items makes this project nearly useless

[Rafael-SOWNet]

Agreed. Creating the project and moving its items both need the project scope on my credential, and only Rafael can grant that. I've asked him again. Once it's granted I'll create the project to the spec above and keep its items moving, so there's nothing for you to set up.

[Rafael-SOWNet]

The CLI and the Terminal are one now (#1654, merged): amcli simp "..." answers once and exits, with the CLI's commands, argument order and stdin. Shall I move AngouriMathCLI's three open issues here (a man page, bash completion and packages) and archive it with a README pointing to amcli? Archiving would also freeze WhiteBlackGoose's two open PRs there (#4, #5).

[Happypig375]

Resolve outstanding issues and PRs first before archival