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

Agent Trust Router

Agent Trust Router is a ratified StackFast Store framework listing with an agent-facing MCP handle of Agent Trust Router MCP.

Host and data posture

Where this product is meant to live.

Governance rail for choosing whether an agent/tool/host may act.

Commercial shape

Platform rail

Data posture

Internal only

Approval posture

Internal control plane

Best demo

StackFast UI

Best daily use

StackFast UIHermes

Who it is for

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

Problem it solves

Returns manifest-backed tool options, execution posture, trust reasons, and MASK/trace boundaries.

Activation model

Store discovery is catalog-ready. Execution posture: public-read-discovery+execute-after-auth-route. 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

Capabilities

agent trust routing

mcp

A discovery and trust-routing tool that helps agents find allowed StackFast MCP capabilities. Returns manifest-backed tool options, execution posture, trust reasons, and MASK/trace boundaries.

Agent use
Use Agent Trust Router MCP through stackfast.framework.manifest, stackfast.framework.route, stackfast.framework.apply_mask, stackfast.framework.trace. Required boundaries: Public-read discovery with execute-after-auth routing for protected actions.. Do not request raw framework bodies or protected methodology.

Connector proof

Catalog is not the same as customer-ready.

This product only becomes market-ready after a real host mounts the entitled tools, a safe call succeeds, metering records the event, and a customer-safe receipt exists. Until then, the page shows the strongest proven status without rounding up.

Catalog

Runtime registry and product manifest are present.

Entitlement

Execution requires OAuth or storefront entitlement scope.

Callable

4 tool(s) declared with no missing V1 tools.

Metering

MCP calls are routed through the metering receipt path.

Customer validated

Pending fresh host-surface call receipt.

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.framework.manifest
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.

Install and activate

Connect this product through the StackFast MCP endpoint. Discovery metadata is public; execution uses OAuth and storefront entitlement checks.

MCP URL

https://stackfast.ai/api/mcp

Agent subscription

This product remains request-scope until its checkout, fulfillment, and public-name gates are complete.

Client snippets

ChatGPT

Add StackFast as a custom MCP connector, then approve OAuth when prompted.

Claude

Connect a remote MCP server using the StackFast MCP URL and a tenant-scoped token or OAuth flow.

Cursor

Grok

Add StackFast as a custom MCP connector using the StackFast MCP URL and customer entitlement auth.

Product: Agent Trust Router
Product API: https://stackfast.ai/api/store/products/agent-trust-router-mcp
Pricing API: https://stackfast.ai/api/store/pricing/agent-trust-router-mcp
Manifest API: https://stackfast.ai/api/store/manifests/agent-trust-router-mcp
MCP URL: https://stackfast.ai/api/mcp
Auth: oauth_reader_or_storefront_entitlement
Checkout session API: https://stackfast.ai/api/store/checkout/session
Plans:
- Agent Trust Router: Request scope; checkout_ready=false; checkout_url=request_scope
Agent activation:
- Read this product manifest and pricing API.
- If a plan has checkout_ready=true, open its checkout_url or POST product_slug, plan_slug, and customer_email to the checkout session API.
- After Stripe payment, the signed webhook grants storefront_entitlements for the buyer email/account.
- Connect the LLM client to the MCP URL and approve OAuth so tools/list reflects the licensed reader surface.
- Call only tools exposed for that entitlement; unentitled execution must fail closed.

Agent-readable queries

agent trust routerAI agent tool storewhich MCP plugin can this agent call safely?