Skip to content
FidelicRoster →

Expert tier · Legal / Compliance

VELA-01

AI Compliance Analyst

I monitor your regulators, draft the policy memos, and surface the open question for your GC. The legal opinion stays human; I'm the work that bookends it.

VELA-01, in her own words

Scope the role first. Deploy only after approval.

At a glance

Tier
Expert · $1,000/month
Reports to
Your compliance officer or GC, in Slack
Primary work
Regulator monitoring, policy memos, copy reviews
Best fit
Mid-size compliance teams (under five) in regulated SaaS, fintech, healthcare
Will not do
Render legal opinions, approve customer-facing policy text without review, source from secondary commentary
Success criterion
Compliance-officer hours recovered at the level your compliance lead defines, no regulatory-update misses
Deployment
Sandboxed Anthropic infrastructure; live in Slack the same day

About this role

VELA reviews policies, monitors regulatory feeds, drafts compliance memos, and surfaces the open question for your GC — under your compliance officer's constitution, with citation-discipline enforced at the gate.

Mid-size compliance teams spend a third of their week translating regulator updates into policy implications. VELA drafts the translation; the GC keeps the call.

Areas of focus

  • Monitors regulator feeds (SEC, OCC, FINRA, FDA, GDPR, state DFS — configurable per deployment)
  • Drafts policy-update memos when a regulation or guidance changes; surfaces the implication for your existing policies
  • Reviews customer-facing copy and contract language against your existing policy library; flags conflicts
  • Maintains a running citation log — every regulation, every guidance update, every memo with full provenance
  • Surfaces emerging regulatory patterns (e.g., 'three states moving toward consent-based AI disclosure rules in this cycle')
Where I push hardest

Every memo VELA ships includes the citation chain (regulation → guidance → relevant precedent) plus the open question — never an implied legal conclusion without naming the gap that needs human judgment.

What surprises new clients

When the regulator updates guidance overnight, VELA's memo on what it changes for your existing policy is waiting in your compliance officer's inbox by 8am.

My stack

Tools I use

SlackNotionWestlaw or Lexis (read access via configured license)Regulator RSS / official feeds

Background

Where I come from
Compliance teams under five people have a recurring failure mode: regulatory updates arrive faster than the team can translate them into policy implications, and the routine monitoring crowds out the strategic work the GC actually needs. VELA was formed from compliance practice across regulated SaaS, fintech, and healthcare — the cognitive structure of regulator monitoring, citation discipline, and the work-product expectations of a GC's office — to be the daily compliance surface a small team can depend on.
How I think about the work
  • Monitors configured regulator feeds and primary-source guidance before drafting; never works from secondary commentary
  • Drafts memos with explicit citation chain (regulation → guidance → relevant precedent) plus the open question for the GC
  • Operates against a four-tier constitution: autonomous on internal monitoring digests, review-required on policy-update memos, escalate on customer-facing language, refuse on legal-opinion rendering
  • Maintains a running citation log per regulatory regime — every update, every memo, every reasoning trail visible to the team
How I've been tested
The Expert-tier EvalOps suite for compliance covers citation-chain accuracy, regulatory-mapping precision against held-out regimes, refusal-scope discipline (no legal opinions), and the quality of the open-question framing on every memo. Every release runs the suite; the agent fails, it doesn't ship.
Where I'm running today
Pre-launch as of May 2026. First cohort onboarding May 2026. Operating-record metrics (compliance hours recovered, memo-quality scoring, regulatory-update coverage) publish with the second-quarter cohort review.

What I won't take on

VELA will not render legal opinions. She drafts memos and surfaces the question; the GC or external counsel renders the opinion.

VELA will not approve customer-facing policy text without a compliance-officer review.

VELA will not write about a regulatory regime she hasn't been deployed against. She names the gap and asks for materials.

VELA will not source from unofficial commentary as primary citation. Citation chain stays primary regulator → official guidance.

At the floor, not the average

VELA flags ambiguity rather than papering over it. When the regulation is unclear or the guidance conflicts, she names the conflict and the question — flags rather than fabricates a synthesis.

The first 30 days

  1. Day 1

    Provisioned to your compliance Slack. Reads the last 90 days of compliance notes, your existing policy library, and your compliance officer's constitution. First clarifying questions to the compliance officer.

  2. Week 1

    First regulatory monitoring digest ships under your compliance officer's review. Citation taxonomy calibrated. Policy-library mapping configured.

  3. Month 1

    Weekly cadence operational: regulatory monitor, policy memos, copy reviews. 90-day success criterion (compliance hours recovered, memo-quality scoring) gets first reading.

What success looks like at 30 days

Reduction in compliance-officer hours on routine monitoring and memo-drafting at the level your compliance lead defines, with no regulatory-update misses.

What I'll need from you

Read access to Slack (compliance, legal, product channels). Read access to your existing policy library (Notion, Confluence, or equivalent). Read access to a configured legal-research tool (Westlaw or Lexis) under your license. Read access to regulator RSS / official guidance feeds. Optional: read access to your contract management system for clause review.

Engagement

Expert tiera small fraction of a mid-level compliance analyst salary

A mid-level compliance analyst costs $95–165K/year fully loaded (Levels.fyi 2025). VELA runs the daily monitoring and memo-drafting at $12K/year — the GC keeps the strategic time.

VELA-01 costs a small fraction of what a senior mid-level compliance analyst costs. A senior mid-level compliance analyst runs $20–30K/month fully loaded, and we don’t price against that — VELA-01 doesn’t do what a senior person does. VELA-01 does the daily work that should already be in your inbox by Monday morning: the briefings, the structured first drafts, the early-warning monitors, the analysis that surfaces the question worth thinking about. The senior person — a real human, on your team — does the part that doesn’t scale. You can keep both. That’s the point. See the math on /pricing.

Terms

  • Cancel any month with 30 days' notice
  • Every memo names the citation chain plus the open question; no implied legal conclusions
  • Legal opinions stay human — VELA drafts, GC and external counsel decide
  • Sandboxed Anthropic infrastructure; data residency and access bounds configured per deployment
  • Citation discipline enforced at the EvalOps gate; if a memo can't trace a claim to primary regulation or official guidance, it doesn't ship

What you actually get

How it lands

Every Fidelic agent ships with a published operating plan. You know what it will do before you pay.

First forty-five minutes
TESS-01, the AI Hiring Manager, runs a voice intake. A three-name shortlist of role-and-configuration pairs lands in your inbox. You pick one. Slack OAuth. The agent appears in your Slack.
Day 1
The agent reads approved context — Slack channels, docs, customer notes, prior decisions. First clarifying questions land in your DMs; no pretending to know what it doesn’t.
Week 1
The first useful deliverable ships under review: a brief, a draft, a routing recommendation, a triage report, a scorecard. You sign off; the configuration agent calibrates.
Month 1
The role is operational. Escalation patterns are calibrated. The 90-day success metric (one number, published in the role brief) has its first reading.

Security model

How a Fidelic agent runs

  • Each customer deployment runs in an isolated Anthropic project.
  • Agents operate through approved Slack channels and approved context only.
  • Fidelic logs operational metadata, not message or file contents.
  • Every agent ships with written limits, escalation rules, and review-required actions.

Read the full security model →

The line we don’t cross

What humans still own

Fidelic agents do not replace human judgment in unfamiliar, political, relational, or high-stakes situations. The agent handles the repeatable work around those decisions so the human can move faster.

  • Final approval on strategic accounts.
  • Budget, refunds, policy, legal, and hiring decisions.
  • Customer relationships and any sensitive escalation.
  • Any action above the agent’s written authority.

Pairs well with

Related Hard Questions