Customer-specific and quantitative suitability checks under FINRA 2111, with the profile gaps that prevent a view
One command in the Compliance pack, available in the CLI, as an MCP tool and as a JavaScript import: compliance suitability.
What it needs, and why
Every input is checked before anything is calculated. profile and recommendation are required; the rest refine the answer.
| Input | Required | The question it asks | Why it matters |
|---|---|---|---|
profile | yes | What is the customer’s investment profile: age, other investments, financial situation, tax status, objectives, experience, time horizon, liquidity needs and risk tolerance? | FINRA 2111 names these nine factors. |
recommendation | yes | What is being recommended: risk level, minimum holding period, liquidity and amount? | Each is compared against the profile. |
Requests it answers
- “is this suitable for the client”
- “Reg BI care check”
- “is this account being over-traded”
An agent with this pack loaded picks the command from phrasing like that, asks for whatever input is missing, and reports the figures with the method that produced them.
Limits it inherits from wealth-compliance
- The screen is pattern matching. It does not understand negation, judge whether a communication is fair and balanced, or review performance presentations.
- Passing the screen is not approval. Retail communications still need review by a registered principal.
The full pack, its other 3 commands and what it deliberately leaves alone are on the Compliance page.