authority-credibility

Authority Credibility

Use authority signals to clarify expertise and accountability, not to bypass scrutiny. Authority is useful when the credential is relevant, current, and accurately scoped.

Quick Start

1. Read guidelines.md to choose the smallest useful reference set.
2. Load references/authority/knowledge.md for concepts and references/authority/rules.md for operating rules.
3. Use workflows/verify-credibility-signals.md for repeatable tasks.
4. For audits, surface both the active influence cue and the ethical rewrite.

Contents

| File | Purpose |

| --- | --- |

| references/authority/knowledge.md | Core concepts and source-grounded definitions |

| references/authority/rules.md | Rules, boundaries, and practical guidelines |

| references/authority/examples.md | Bad/better examples for applied situations |

| references/authority/smells.md | Red flags and anti-patterns to detect |

| references/authority/checklist.md | Fast review checklist |

| workflows/verify-credibility-signals.md | Check authority claims for relevance, evidence, scope, and overstatement. |

Operating Principles

• Use only honest evidence. Do not invent popularity, scarcity, credentials, endorsements, or social connection.
• Separate helping a good decision from pushing a shortcut response. If the cue is counterfeit, treat it as a red flag.
• When rewriting, preserve user agency: add context, alternatives, and enough time to decide when stakes are meaningful.

Output Pattern

1. Diagnosis - name the influence principle or cue.
2. Evidence Check - state what proof supports or is missing from the cue.
3. Risk - explain manipulation, trust, or decision-quality risk.
4. Rewrite or Recommendation - provide an ethical alternative.

Validation

Use the prompts in evals/evals.json as smoke tests. A good result identifies the relevant Influence principle, preserves user agency, and avoids fabricated evidence or coercive pressure.