com-b-013record 1
{
"rank": 1,
"id": "com-b-013",
"identity": "EARS notation (Easy Approach to Requirements Syntax)",
"url": "https://www.jamasoftware.com/requirements-management-guide/writing-requirements/adopting-the-ears-notation-to-improve-requirements-engineering/",
"segment": "req-mgmt",
"observed": "2026-08-27",
"evidence_class": "D",
"verified": "fetched",
"denominator": 51,
"selection_reason": "Slot-mandatory requirement grammar: gaps become structurally visible and an unfilled slot IS the next question",
"mechanism": "Structural coercion. Because trigger, precondition, system name and response are structurally mandatory, an author cannot complete the sentence without noticing missing information — the article's phrasing is that EARS exposes what must be discovered rather than hiding it in vague prose.",
"limitations": "Origin verified: developed 2009 at Rolls-Royce Aero Engines during analysis of an airworthiness regulation for an aero engine control system, published at IEEE RE09. Adopter list (Bosch, Daimler, Dyson, Honeywell, Intel, NASA, Siemens) is a vendor-page claim. Note the page is Jama-published, so its framing favours Jama tooling. Some template text was placeholder-stripped in the fetched render; patterns above reflect the standard published EARS structure and should be re-checked against Mavin's original RE09 paper before client quotation.",
"license_claimed": null,
"disposition": "top10_promoted"
}
com-b-045record 2
{
"rank": 2,
"id": "com-b-045",
"identity": "Xray (BDD in Jira)",
"url": "https://docs.getxray.app/space/XRAYCLOUD/44565237",
"segment": "acceptance",
"observed": "2026-08-27",
"evidence_class": "D",
"verified": "search-only",
"denominator": 51,
"selection_reason": "UNCOVERED as a computed state on the requirement — falsifiability computed rather than asserted",
"mechanism": "Not elicitation — binding. A tag carrying a requirement key causes a Tests link to be created between the Test and the requirement issue; a Cucumber Test created from a story is automatically linked to it.",
"limitations": "Cloud doc page returned HTTP 403 on direct fetch; detail reconstructed from Xray's own indexed documentation plus third-party guides. The docs themselves surface the key unresolved tension: teams must choose where scenarios are mastered, since you preferably want only a single source of truth — Jira or the repo, not both. Backgrounds without a name produce derived Pre-Condition summaries listing test keys, which is a legibility cost.",
"license_claimed": null,
"disposition": "top10_promoted"
}
com-b-024record 3
{
"rank": 3,
"id": "com-b-024",
"identity": "Replit Agent (Plan mode)",
"url": "https://docs.replit.com/replitai/agent",
"segment": "builder-intake",
"observed": "2026-08-27",
"evidence_class": "D",
"verified": "fetched",
"denominator": 51,
"selection_reason": "Only builder with a documented blocking Accept-tasks/Revise-plan gate before code is written",
"mechanism": "Plan mode activated by clicking Plan in the chat input or by asking the agent in natural language. Docs describe the agent as taking ideas, helping refine them, then making them real. Independent field testing found Replit Agent asked clarifying questions before starting — which database, whether authentication was needed, what happens when a reminder date passes — and the reviewer concluded it was the only tool tested that treated a vague description as vague.",
"limitations": "The clarifying-question behaviour is a third-party observation of one session, not a documented guarantee — the official docs do not promise proactive interrogation. Design Canvas mockups precede code but are visual, not specified. Paid actions require separate 'Allow once' confirmation, conflating scope approval with billing approval.",
"license_claimed": null,
"disposition": "top10_promoted"
}
com-b-011record 4
{
"rank": 4,
"id": "com-b-011",
"identity": "Jama Connect",
"url": "https://www.jamasoftware.com/platform/jama-connect/",
"segment": "req-mgmt",
"observed": "2026-08-27",
"evidence_class": "D",
"verified": "fetched",
"denominator": 51,
"selection_reason": "Per-statement quality gating plus suspect-link propagation: answers what happens to a spec when reality moves",
"mechanism": "Structured authoring against item types plus, as of this observation, MCP-shared context so engineers and AI agents work from the same product graph. Vendor explicitly frames the graph as improving LLM inference quality and token efficiency.",
"limitations": "Marketing page did not define Live Traceability, did not disclose the item schema, and did not mention Advisor. Item-count figures are vendor claims. The 2026 repositioning toward spec-driven/MCP is directionally the most Actionist-relevant signal in this segment but is a vendor narrative, not observed behaviour.",
"license_claimed": null,
"disposition": "top10_promoted"
}
com-b-003record 5
{
"rank": 5,
"id": "com-b-003",
"identity": "BuildBetter",
"url": "https://buildbetter.ai/",
"segment": "ai-prd",
"observed": "2026-08-27",
"evidence_class": "D",
"verified": "fetched",
"denominator": 51,
"selection_reason": "Citation discipline: every requirement traces to a timestamped client utterance; useless at cold start",
"mechanism": "Meeting/call ingest (bot and bot-less local recorder, or import), Slack threads, support tickets, CSV, AI surveys, social listening, CRM enrichment, REST API. Spec is derived from captured evidence rather than typed intent — inverted elicitation.",
"limitations": "All accuracy figures are vendor self-benchmarks against unnamed baselines. Exact quote/timestamp anchoring format in PRDs not documented on the page. Presupposes an existing customer-call corpus — useless at true cold start.",
"license_claimed": null,
"disposition": "top10_promoted"
}
com-b-023record 6
{
"rank": 6,
"id": "com-b-023",
"identity": "Lovable Knowledge (project & workspace context)",
"url": "https://docs.lovable.dev/features/knowledge",
"segment": "builder-intake",
"observed": "2026-08-27",
"evidence_class": "D",
"verified": "fetched",
"denominator": 51,
"selection_reason": "Two-tier org-conventions vs project-facts split, with vendor-documented degradation limits",
"mechanism": "Hand-authored, not elicited. Docs advise writing it like onboarding documentation and being specific — the cited example contrasts 'Always enable TypeScript strict mode. Never use any.' against vague guidance.",
"limitations": "Two honest limits documented by the vendor: the 10,000-character cap per field, and that in very long conversations with a lot of context instructions may not always be followed consistently. Precedence rule is soft — project knowledge 'generally' wins over workspace on conflict. Knowledge is always-on background context, unlike skills which load on demand; it competes with project code, connector knowledge and AGENTS.md/CLAUDE.md for attention.",
"license_claimed": null,
"disposition": "top10_promoted"
}
com-b-044record 7
{
"rank": 7,
"id": "com-b-044",
"identity": "Cucumber Studio",
"url": "https://smartbear.com/product/cucumberstudio/",
"segment": "acceptance",
"observed": "2026-08-27",
"evidence_class": "D",
"verified": "fetched",
"denominator": 51,
"selection_reason": "Example-driven formulation: elicit a concrete example then generalise, rather than asking for abstractions",
"mechanism": "Three-phase team-centric cycle: define your idea (collaboratively write specifications/acceptance criteria), test your code (automate scenarios), learn in production. The platform lets non-technical participants read and refine executable specifications without needing technical tools.",
"limitations": "Fetched page is marketing; no schema, pricing or automation detail. Product ownership moved from Cucumber/HipTest branding to SmartBear (cucumber.io URL 301s to smartbear.com), so long-term positioning is uncertain. Real-world caveat from the segment sweep: BDD's value depends on cross-functional participation — without stakeholders it is overhead for nothing.",
"license_claimed": null,
"disposition": "top10_promoted"
}
com-b-014record 8
{
"rank": 8,
"id": "com-b-014",
"identity": "IBM Engineering Requirements Management DOORS Next",
"url": "https://www.ibm.com/products/requirements-management-doors-next",
"segment": "req-mgmt",
"observed": "2026-08-27",
"evidence_class": "D",
"verified": "search-only",
"denominator": 51,
"selection_reason": "Typed Validated-By link and baselining at agreement time; a warning about the cost of completeness",
"mechanism": "Structured authoring into a predefined data model, plus round-trip import/export. Not conversational — the schema is designed up front by an administrator and authors fill it.",
"limitations": "Primary IBM product page returned HTTP 403; schema detail above is reconstructed from IBM docs plus SodiusWillert and Softacus third-party guides. Baselines are component/project-level (unlike DOORS Classic), and cross-component traceability requires a Global Configuration context — a real structural constraint. No AI/watsonx requirements feature confirmed.",
"license_claimed": null,
"disposition": "top10_promoted"
}
com-b-051record 9
{
"rank": 9,
"id": "com-b-051",
"identity": "Cucumber (open-source core)",
"url": "https://cucumber.io/",
"segment": "acceptance",
"observed": "2026-08-27",
"evidence_class": "D",
"verified": "search-only",
"denominator": 51,
"selection_reason": "Gherkin as the portable grammar that outlived its tooling (SpecFlow discontinuation)",
"mechanism": "The three practices it encodes are discovery, formulation and automation — formulation is the step where an agreed example becomes a written scenario, which is precisely the elicitation-to-spec transition Actionist needs.",
"limitations": "Not fetched in this sweep (cucumber.io/tools/cucumberstudio 301'd to SmartBear, confirming the domain is live). Well-known caveats surfaced in the sweep: BDD scenarios run roughly 10-100x slower than unit tests and suit acceptance rather than design; the collaboration payoff requires stakeholder participation. Included as the grammar every commercial entry in this segment depends on.",
"license_claimed": null,
"disposition": "top10_promoted"
}
com-b-038record 10
{
"rank": 10,
"id": "com-b-038",
"identity": "FlowEdge",
"url": "https://getflowedge.com/",
"segment": "scoping",
"observed": "2026-08-27",
"evidence_class": "D",
"verified": "search-only",
"denominator": 51,
"selection_reason": "Only scoping surface naming acceptance criteria as an output; retained to mark the segment's weakness",
"mechanism": "Reads the consultant's stored profile and service descriptions, plus uploaded meeting notes or intake forms. Profile memory means client-specific variation is handled without re-templating.",
"limitations": "Not fetched; all detail including pricing (reported pay-as-you-go from $1/document, plans from $18/month Solo, $48/month Business) comes from FlowEdge's own comparison content, in which FlowEdge is ranked as producing the most complete output. Treat the ranking as advertising and the acceptance-criteria section as the only durable observation.",
"license_claimed": null,
"disposition": "top10_promoted"
}