What is a Role Brain?

A Role Brain is a persistent decision-pattern repository that captures the tacit knowledge and instincts of key personnel. When an executive departs, their Role Brain remains as a corporate asset, allowing a successor to operate at full capacity from Day 1.

How does StackFast differ from standard RAG implementations?

Standard RAG retrieves text without understanding context. StackFast provides a reasoning layer that applies judgment through structured logic, builds persistent Role Brains that compound over time, and enforces knowledge sovereignty through a 3-layer governance gate.

What is Knowledge Sovereignty?

Knowledge Sovereignty means your organization's intelligence never leaks into third-party training sets. Every brain entry is tagged for compliance and M&A readiness, with audit trails generated automatically for EU AI Act, SOC2, and HIPAA compliance.

How does StackFast reduce Key-Person Risk?

StackFast captures executive decision patterns, client relationship nuances, and institutional knowledge into structured Role Brains. When key personnel leave, their judgment and instincts remain as a corporate asset, reducing onboarding time for replacements and preserving institutional intelligence.

Back to Catalog

plugin

Buyer Pain to Capability Matcher MCP

Buyer Pain to Capability Matcher MCP is a ratified StackFast Store framework listing for Buyer Pain to Capability Matcher.

Who it is for

Agents, operators, and CleverQ users that need a governed StackFast capability instead of a generic chat answer.

Problem it solves

Maps natural-language buyer needs to relevant capabilities without exposing protected framework vocabulary.

Activation model

Store discovery is catalog-ready. Execution posture: execute-after-auth. Public go-live remains gated until Robert ratifies publication.

Proof and source paths

Public job-name ratified 2026-05-27
Two-name doctrine applied
Proof-without-recipe disclosure boundary applied
Callable tools are real repo MCP tool IDs

Repo evidence

specs/CLEVERQ_FRAMEWORK_WORKBENCH_AND_AGENTIC_STORE_ADDENDUM_2026-05-27.md
specs/WO-CLEVERQ-FW-STORE-LISTINGS-P1-2026-05-27.md
lib/tool-registry/plugin-mcp-tools.ts
lib/framework-invocation/mcp-tools.ts
lib/perspective/mcp-tools.ts

Capabilities

buyer pain capability match

mcp

A capability matching tool that translates buyer pain into public-safe StackFast product and proof vocabulary. Maps natural-language buyer needs to relevant capabilities without exposing protected framework vocabulary.

Agent use
Use Buyer Pain to Capability Matcher MCP through stackfast.perspective.translate, stackfast.framework.route, stackfast.framework.apply_mask, stackfast.framework.trace. Required boundaries: Public-safe capability matching with protected-vocabulary masking.. Do not request raw framework bodies or protected methodology.

Runtime registry status

Primary registry

stackfast.ai/api/mcp

Status

partial public mcp

Install gate

Catalog-ready only. Do not publish publicly until Robert ratifies store go-live.

Callable tools

stackfast.perspective.translate
stackfast.framework.route
stackfast.framework.apply_mask
stackfast.framework.trace

Missing or gated tools

No missing tools declared for the current V1 boundary.

Framework listing layer only; no parallel CleverQ engine introduced.
Public surfaces must render the human job-name and proof-without-recipe card fields.

Agent-readable queries

buyer pain to capability matchermatch this buyer pain to StackFast capabilitieswhat product fits this customer request?