feat: 'Rejected Proposals' page for evaluated but not qualified anchors

[raifdmueller]

Description

We need a place for anchor proposals that were evaluated but don't meet the criteria for a semantic anchor. Currently these just get rejected as issues with no visible outcome on the website.

Problem

Some proposals are good concepts but fail the semantic anchor test — for example:

• MIRRR UX Framework ([Anchor Proposal]: MIRRR UX Framework #150): A real framework, but not established enough in LLM training data to reliably activate the right knowledge
• TLDR: Underspecified, no defined structure — will never be a semantic anchor regardless of training data
• GoF Tier-3 patterns (Flyweight, Interpreter, Memento, Visitor): Too niche to work reliably as anchors

These represent different reasons for not qualifying:

1. Not in training data (yet) — good concept, but LLMs don't reliably recognize it
2. Structurally unsuitable — too vague, no defined methodology, pure instruction
3. Too niche — real pattern but too specialized for reliable activation

Goal

Create a non-prominent page on the website (not in main nav, linked from About/Contributing) that:

• Lists evaluated proposals that didn't qualify
• Explains WHY each didn't qualify (which criterion failed)
• Serves as reference to avoid re-proposals
• Educates contributors about what makes a good semantic anchor

Open design questions

• What should the page be called? Not "Candidates" (suggests they'll become anchors). Options:
  • "Evaluated Proposals" / "Bewertete Vorschläge"
  • "Not Qualified" / "Nicht qualifiziert"
  • "Rejected Proposals" / "Abgelehnte Vorschläge"
  • Something else?
• How to categorize the reasons (training data vs. structurally unsuitable vs. too niche)?
• Should Tier-3 GoF patterns appear here too, or only stay in the umbrella context?
• Should this be a static AsciiDoc page or generated from metadata?

Examples to include

Proposal	Reason	Category
TLDR	Underspecified, no structure	Structurally unsuitable
ELI5	Vague target, no pedagogical framework	Structurally unsuitable
MIRRR UX Framework (#150)	Not established in training data	Not in training data

References

• Anchor quality criteria: CLAUDE.md "Quality Criteria for Semantic Anchors"
• Existing Tier-3 handling: GoF umbrella (PR feat: umbrella anchors with GoF sub-patterns #159)

🤖 Generated with Claude Code