diff --git a/.github/ISSUE_TEMPLATE/bug_report.md b/.github/ISSUE_TEMPLATE/bug_report.md
deleted file mode 100644
index ca723bb8b..000000000
--- a/.github/ISSUE_TEMPLATE/bug_report.md
+++ /dev/null
@@ -1,22 +0,0 @@
----
-name: Report a bug
-about: A wrong answer, a crash, a hang, or an answer where there should have been a decline.
-title: ''
-type: Bug
-assignees: ''
-
----
-
-**The version I use**: <!--
-AngouriMath is shipped in four packages: AngouriMath, AngouriMath.FSharp, AngouriMath.Interactive, AngouriMath.CPP.
-Please, specify which one you are using, and specify its version (check it in your csproj file or on the Releases page in case
-you are using AngouriMath.CPP).
--->
-
-**Unexpected behaviour or bug**: <!--
-Here, describe the bug you are experiencing. If you are not sure if it's a bug or not, you still can create the issue, and
-we will know better which behaviour is really expected by users.
--->
-
-
-<!--Thanks for making AngouriMath better! You can also join our Discord chat https://discord.gg/YWJEX7a -->
\ No newline at end of file
diff --git a/.github/ISSUE_TEMPLATE/goal.md b/.github/ISSUE_TEMPLATE/goal.md
deleted file mode 100644
index 1e4968d5a..000000000
--- a/.github/ISSUE_TEMPLATE/goal.md
+++ /dev/null
@@ -1,24 +0,0 @@
----
-name: State a goal
-about: State a triaged outcome or initiative; it may start without sub-issues and generate work over time.
-title: ''
-type: Goal
-assignees: ''
-
----
-
-**What should be true**: <!--
-An outcome or initiative -- an input and the answer it should give, a class of problems (a textbook
-chapter, a competition, a paper's examples), or a capability. A goal does not need to list every
-future child up front. Use sub-issues for independently coordinated work; keep a checklist for
-mutable planning notes and small steps. A self-contained pull request may reference this Goal
-directly without a duplicate sub-issue.
--->
-
-**What happens today, if anything**: <!--
-The current answer, the exception, the timeout -- or "nothing, it is not there".
--->
-
-**Where it comes from** (optional): <!--
-A textbook, a paper, another system's answer, a link.
--->
diff --git a/.github/ISSUE_TEMPLATE/maintenance.md b/.github/ISSUE_TEMPLATE/maintenance.md
deleted file mode 100644
index c47194144..000000000
--- a/.github/ISSUE_TEMPLATE/maintenance.md
+++ /dev/null
@@ -1,20 +0,0 @@
----
-name: Plan maintenance
-about: Improve internal quality without primarily changing user-facing behaviour.
-title: ''
-type: Maintenance
-assignees: ''
-
----
-
-**What needs maintenance?** <!--
-Describe the internal code, tests, documentation, CI, dependency, or tooling work.
--->
-
-**Why is it needed?** <!--
-Explain the maintenance cost or risk it addresses.
--->
-
-**Definition of done** <!--
-List the checks or measurements that show the maintenance is complete.
--->
diff --git a/.github/ISSUE_TEMPLATE/report.md b/.github/ISSUE_TEMPLATE/report.md
new file mode 100644
index 000000000..9908e9c5c
--- /dev/null
+++ b/.github/ISSUE_TEMPLATE/report.md
@@ -0,0 +1,30 @@
+---
+name: Open an issue
+about: A wrong answer, something missing, an outcome to aim at, or upkeep. The kind is decided at triage — say what happened, not what to call it.
+title: ''
+assignees: ''
+
+---
+
+<!--
+No kind to choose. Whoever triages this reads what you wrote and sets the type — Bug, Feature,
+Goal or Maintenance — because the same report can be any of them depending on what turns out to be
+true. Fill in what you know and leave the rest; a blank issue is fine too.
+
+Questions belong in Discussions: https://github.com/asc-community/AngouriMath/discussions
+-->
+
+**What you ran**: <!--
+The expression or the code, as you ran it, so it can be pasted in. `"x^2".Integrate("x")` is
+enough; a screenshot of the same is harder to run. Say which package and version if you know it --
+AngouriMath, AngouriMath.FSharp, AngouriMath.Interactive or AngouriMath.CPP.
+-->
+
+**What it did**: <!--
+The answer it gave, the exception, the hang -- or "nothing, it is not there".
+-->
+
+**What it should have done**: <!--
+The answer you expected, and where that comes from if it is not obvious: a textbook, another
+system, a definition. For something that does not exist yet, what should be true once it does.
+-->
diff --git a/.github/ISSUE_TEMPLATE/suggest_idea.md b/.github/ISSUE_TEMPLATE/suggest_idea.md
deleted file mode 100644
index 5b5aeafea..000000000
--- a/.github/ISSUE_TEMPLATE/suggest_idea.md
+++ /dev/null
@@ -1,21 +0,0 @@
----
-name: Suggest an idea
-about: Your ideas might help the project!
-title: ''
-type: Feature
-assignees: ''
-
----
-
-**The package I want to suggest the idea to**: <!--
-AngouriMath is shipped in four packages: AngouriMath, AngouriMath.FSharp, AngouriMath.Interactive, AngouriMath.CPP.
-Please, specify which one you are using.
--->
-
-
-<!--
-Now, tell about the feature you want to suggest. Don't hesitate to suggest something you are not sure about. Every idea might
-be helpful.
--->
-
-<!--Thanks for making AngouriMath better! You can also join our Discord chat https://discord.gg/YWJEX7a -->
\ No newline at end of file
diff --git a/AGENTS.md b/AGENTS.md
index c5c63854a..668ce7b6d 100644
--- a/AGENTS.md
+++ b/AGENTS.md
@@ -488,8 +488,8 @@ Then:
    once answered, closed unless a work item came of it.
 
    **Triage is part of the first answer, not a pass of its own.** An issue with no type is
-   untriaged, and the reply that engages with it is where the type, the milestone and the labels
-   go on -- not a later sweep, which is one more thing to forget and leaves the tracker wrong in
+   untriaged -- which every issue is when it arrives, the one template asking for no kind -- and
+   the reply that engages with it is where the type, the milestone and the labels go on -- not a later sweep, which is one more thing to forget and leaves the tracker wrong in
    the meantime. A pull request is not triaged: it carries the issue it says it is `Part of`, and
    a type on it would be that issue's type written twice. A discussion is triaged by the category
    it is in; what it needs is an answer, and an issue only if work came of it.
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index 24c467594..7cfcfecd5 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -127,8 +127,12 @@ request saying `Part of #n` is the work claim.
 
 Questions and requests for opinions are **Discussions**, not issues -- the Q&A and Ideas
 categories -- and are answered there; an issue that turns out to be one is redirected and, once
-answered, closed unless a work item came of it. `up-for-grabs` marks an issue reserved for a
-newcomer.
+answered, closed unless a work item came of it.
+
+There is **one issue template**, and it asks for no kind: what you ran, what it did, what it
+should have done. The kind is decided at triage, because the same report is a Bug or a Feature
+depending on what turns out to be true, and the person who hit the behaviour is not the person
+best placed to say which. Blank issues are enabled beside it.
 
 Who is *working* an issue is whoever has an open pull request on it, draft or not, saying
 `Part of #n`: the pull request is the claim, a week without a push or a comment on it makes the