Tighten solo_founder_feasible evaluator to score first-10-customer GTM

In filter_score.js, locate the highSystem/lowSystem evaluator prompts for the solo_founder_feasible axis. Add the following anti-manipulation clause immediately before or inside the scoring rubric: 'CRITICAL — GTM scoring rule: Score the actual motion required to acquire the FIRST 10 paying customers given the specific ICP named in this hypothesis, not the product's eventual self-serve potential. Institutional ICPs (healthcare systems, regulated enterprises, established professional practices, government agencies, agricultural cooperatives, specific-sector trade networks) require relationship-based or conference-based acquisition for the first 10 customers regardless of how the proposer frames distribution. Score 0-1 for any ICP where the named buyer cannot be reached via async/inbound channels without warm introductions or sector-specific conference presence. Solo-inbound-only GTM (score 3) requires: a public community where the buyer self-identifies, an existing content audience, or an SEO surface with demonstrable low competition. A claim of content marketing or LinkedIn posts without an existing audience scores 1, not 2. Ignore future-state self-serve framing; score the launch-stage reality.'

Back-scoring hyp-2026-05-14-d3786b (Agronomy Advisory for UK soft-fruit and glasshouse growers — institutional trade-channel buyers) and hyp-2026-05-11-cc72cd (Bot-Promise Slip for B2B Support Ops — enterprise procurement buyers) with revised prompt produces solo_founder_feasible scores of 0-1, making them fail the kill threshold and preventing escalation to expensive council moves. Of 5 recent council-stage kills, at least 3 should have been catchable at filter_score with this instruction.

Back-score d3786b and cc72cd with revised prompt. If either scores ≥ 2 on solo_founder_feasible (treating UK agronomy trade-channel buyers or enterprise support-ops buyers as accessible via async inbound), the evaluator instruction is still insufficient. Complementary check: back-score hyp-2026-05-06-ec4507 (Support Escalation for B2B SaaS Support Ops, rated ROBUST by S157) — if it scores 0-1, the instruction over-restricts this ICP which has observable self-serve community channels.

Accepted with status: accepted with revision. Awaiting or completed implementation by Architect.