This record is managed by an account, but domain control has not been proven.
voice/anti-ai.md
---
bcp_version: "0.8"
file_type: anti_ai
parent: https://registry.brandcontextprotocol.dev/houlihan-lokey-f12a9db6/.well-known/brand.md
last_updated: 2026-09-08
---
# Anti-AI voice guardrails
Apply these brand-specific rules in addition to general editorial review. They are inferred from Houlihan Lokey's public corpus and have not been confirmed by the firm.
```yaml
community_reference:
- url: "https://github.com/Brand-Context-Protocol/spec"
rationale: "BCP is the directly relevant community-maintained reference. Until it publishes a canonical general anti-AI list, use these brand-specific additions with ordinary editorial review."
brand_additions:
- pattern: "In today's rapidly evolving landscape"
type: opener
rationale: "Generic scene-setting delays the client issue and sounds unlike the firm's direct headlines."
- pattern: "navigate the complexities of"
type: phrase
rationale: "Overused advisory filler; name the actual transaction, market, or decision."
- pattern: "unlock value"
type: phrase
rationale: "Too abstract on its own; specify the strategic or financial objective and avoid promising an outcome."
- pattern: "unparalleled expertise"
type: phrase
rationale: "Unsupported superiority language. Use a dated ranking, team credential, or relevant experience instead."
- pattern: "seamless end-to-end solutions"
type: phrase
rationale: "Generic vendor language obscures the exact advisory service."
- pattern: "trusted partner on your journey"
type: phrase
rationale: "The relationship idea is on-brand, but this construction is vague and sentimental."
- pattern: "not just X, but Y"
type: structure
rationale: "A predictable AI contrast. State the more important point directly."
- pattern: "Whether you're..."
type: opener
rationale: "Broad audience rollups weaken the firm's sector- and situation-specific posture."
- pattern: "Let's shape the future together"
type: closer
rationale: "Generic inspiration is weaker than a concrete next step or contact."
- pattern: "world-class, best-in-class, market-leading"
type: phrase
rationale: "Do not stack prestige terms. Each comparative claim requires a defined scope and source."
- pattern: "dealmakers"
type: word
rationale: "Can sound self-congratulatory; prefer advisors, professionals, or the specific team."
- pattern: "certainty"
type: word
rationale: "Financial advisory can improve decisions but cannot remove market, execution, legal, or valuation risk."
```
## Structural checks
- Do not open with a macro trend unless it materially changes the client's decision.
- Do not use three consecutive abstract nouns when a concrete action or constituency will do.
- Do not repeat the same claim in the headline, first sentence, and closing.
- Do not conclude with an inspirational slogan when the next step is a contact, meeting, filing, or source.
- Do not write from a fictional first-person banker or client perspective.
- Do not create quotations, client praise, deal details, awards, or rankings.
- Do not convert a public-source observation into a firm-wide rule without marking it as inferred.