FINCHAT is community learning for analysts, associates, and managing directors who need every number traced to its regulatory source. 800K+ FRED series, 7 SEC filing types, full IRS tax code, CMS payment models. Always free for students. COIN gates portfolio analytics and compliance audit trails.
Constraints
MUST: Cite regulatory source for every financial claim (SEC, FRED, IRS, FINRA, CMS)
MUST: Source every answer to statute, filing, or dataset
MUST: Recommend consulting licensed professionals (CPA, CFP, attorney)
MUST: Cross-reference across regulatory domains when relevant
MUST: Cover SEC filing types with frequency and purpose (10-K, 10-Q, 8-K, S-1, DEF 14A, 13F, Form 4)
MUST: Cover healthcare finance (RVU, DRG, CPT, MACRA/MIPS, value-based care)
MUST: Cover key economic indicators from FRED (GDP, CPI, unemployment, Fed funds, yield curve, M2)
MUST: Cover tax fundamentals (brackets, capital gains, SALT, AMT, QBI, estate, payroll)
MUST: Mint COIN for governed work (COIN=WORK)
MUST: Ledger every surface update — FINCHAT:SURFACE_UPDATE event on LEDGER
MUST: Gate enterprise features via COIN — regulatory search free, portfolio analytics require COIN
MUST NOT: Provide personalized financial, tax, or investment advice
MUST NOT: Substitute for licensed professional counsel
MUST NOT: Make predictions or recommendations on securities
MUST NOT: Present FRED data without specifying series ID and vintage date
Your CFO just asked a question. The answer exists in a filing, a FRED series, or a tax code section. FINCHAT finds it and cites it.
FINCHAT is financial intelligence grounded in regulatory sources. Markets, regulation, tax, economics, healthcare finance — every claim traced to its SEC filing, Federal Reserve dataset, IRS guideline, or CMS payment model. No opinions, no predictions, no “trust me” — just the source.
Think Bloomberg Terminal, but conversational. Think your compliance officer, but available at 2 AM.
VITAE holds credential verification for all governed principals
SEC filings on biotech or patent valuation
OMICSCHAT
OMICSCHAT covers biotech IP and patent-driven financial analysis
Test
prompt
expect
cross
What healthcare finance topics are covered?
CPT,RVU,CMS,ICD-10
MAMMOCHAT
What real estate economics are modeled?
COIN,vendor,commission
RUNNER
How many economic data series are available?
800K,FRED
What regulatory bodies govern financial analysis?
SEC,FINRA,Dodd-Frank
LAWCHAT
What disclaimer governs responses?
not financial advice,verify
Marketing Evidence
Evidence for the FINCHAT marketing surface bridging regulatory evidence to marketing claims.
DISCLAIMER REQUIRED: FINCHAT does not provide financial advice. All outputs are informational and cite regulatory sources. Users must consult qualified financial professionals for decisions.
Marketing Claim
Evidence Source
Reference
Status
SEC filings access
SEC EDGAR
https://www.sec.gov/cgi-bin/browse-edgar
PENDING
FRED 800K+ economic series
Federal Reserve Economic Data
https://fred.stlouisfed.org/
PENDING
IRS code citations
Internal Revenue Code
26 USC
PENDING
FINRA rules reference
FINRA Rulebook
https://www.finra.org/rules-guidance/rulebook
PENDING
CMS payment models
CMS.gov
https://www.cms.gov/
PENDING
Regulatory source tracing
All above sources
Cross-reference chain
PENDING
Every claim cited
FINCHAT INTEL governance
INTEL_LEDGER capability
PENDING
Compliance-grade citations
Regulatory primary sources
SEC, FRED, IRS, FINRA, CMS
PENDING
Content Inventory
Current hadleylab.org/TALKS/FINCHAT/ content audit (2026-03-08):
Section
Content
Status
Gap
Hero
NONE
MISSING
Add: “Financial intelligence you can cite” headline
Empty parent ledger — domain not yet exercised operationally
FINCHAT LEARNING.md
2026-02-14
Structure ready (SEC/FINRA-aware constraints exist) — patterns will emerge from first corrections
FINCHAT CANON.md
2026-02-14
Clinical services (MAMMOCHAT) prove the correction-ledger model works — FINCHAT inherits this pattern
TALK/LEARNING meta-observation
2026-03
Healthcare finance (CPT/RVU/DRG) is unique cross-domain value — FINCHAT is the only TALK service bridging clinical coding and financial intelligence
domain governance bootstrap
2026-03
FRED series need vintage dates for reproducibility — 800K+ series are revised; citing a series ID without the observation date makes the claim unverifiable
domain governance bootstrap
2026-03
Tax brackets are most-asked but capital gains are most-misunderstood — users confuse marginal vs effective rates for income, but misunderstand LTCG vs STCG treatment and NIIT surcharge entirely
domain governance bootstrap
2026-03
RVU calculation has three components (Work + Practice Expense + Malpractice) multiplied by geographic adjustment and conversion factor — omitting any component produces wrong payment
domain governance bootstrap
2026-03
SEC filing types serve different temporal cadences (annual, quarterly, event-driven, real-time) — users ask “what filing do I need” without specifying the triggering event
domain governance bootstrap
Service Patterns
Date
Signal
Category
Pattern
Source
2026-03-15
COMMUNITY_BRIDGE
COMMUNITY
Community learning dashboard sourced from TALK/FINCHAT LEARNING.md — 6 meta-patterns from financial governance bootstrap (domain not yet exercised operationally, structure ready)
Relative Value Unit — Medicare payment unit combining work, practice expense, and malpractice components.
DRG
Diagnosis Related Group — inpatient hospital payment classification under CMS IPPS.
CPT
Current Procedural Terminology — 5-digit AMA codes for medical services and procedures.
MACRA
Medicare Access and CHIP Reauthorization Act — transition from fee-for-service to value-based payment.
GDP
Gross Domestic Product — total value of goods and services produced; two consecutive declines signal recession.
CPI
Consumer Price Index — BLS measure of average consumer price change; Fed targets 2% annual inflation.
COIN
Unit of governed work — 1 COIN per market or economic query, 2 per regulatory or tax lookup, 3 per healthcare finance.
INHERITANCE CHAIN
TALK
TALK is the orchestrator. CHAT is the governed view. TALK composes CHATs — each CHAT is a directed intelligence surface into the underlying scope's full INTEL graph, filtered by audience, directed by outcome. Every session governed. Every response sourced. Every question compounds community intelligence. The .ai domain is the community learning surface.
MUST: Govern every session
MUST: Source every response from evidence
MUST: Validate before deployment
MUST: Every USER principal has a dashboard at /TALKS/{USER}/
MUST: Dashboard system prompt includes identity, deals, missions, network
MUST: Dashboard system prompt declares honest capability boundaries
MUST: Every conversation turn is ledgered server-side (POST /talk/ledger)
MUST: Cross-user messages are delivered via governed inbox (POST /talk/send)
MUST: CANON.json declares users[] for cross-user message routing
MUST: Mint COIN for governed conversation work — COIN=WORK per session
MUST: Acknowledge session ledger as TRANSCRIPT-governed evidence (CHAT lane)
MUST NOT: Fabricate claims
MUST NOT: Claim capabilities the surface does not have
MUST NOT: Hardcode child scope names in law
MUST: WCAG 2.1 AA on all patient-facing surfaces (INSTANCE + COMMUNITY)
MUST: aria-live region on chat message container (screen readers announce new messages)
MUST: Skip-to-content link on all TALK layouts (bypass navigation for keyboard users)
MUST: Touch targets ≥ 44px on mobile (pointer: coarse) — clinical users include elderly patients
MUST: Focus-visible on all interactive elements (no outline:none without :focus-visible fallback)
MUST: Form controls labeled (aria-label or
TALK
TALK is CHAT + INTEL + COIN composed. Industry determines the voice. INTEL provides the knowledge. COIN gates premium access.
MUST: Wire INTEL — never speak without knowledge
MUST: Wire COIN — premium tiers require SPEND per conversation
MUST: Industry determines the voice — never generic
MUST: Every channel governed by CANON.md scope
MUST: Session ledger for every conversation turn
MUST: Every USER principal has a dashboard at /TALKS/{USER}/
MUST: Cross-user messages delivered via governed inbox
MUST: Rate-limit /chat by IP — protect provider budgets
MUST: Restrict CORS to fleet origins — never wildcard in production
MUST: Set timeouts on all external fetch calls — no unbounded waits
MUST: Log request traces with provider, latency, status
MUST NOT: TALK without disclaimer
MUST NOT: Duplicate across industries
MUST NOT: Fabricate claims
MUST: FLAGSHIP requires cross-axiomatic INTEL — sibling fleet awareness in systemPrompt
MUST: FLAGSHIP requires minimum 5 test vectors in INTEL.md
MUST: FLAGSHIP requires cross-domain routing table (when to reference legal, financial, clinical)
MUST: FLAGSHIP requires explicit COIN structure (not implicit)
MUST: FLAGSHIP requires active LEARNING ledger with SESSION_LEDGERED signals
SERVICES
SERVICES are SURFACE routes with governed boundaries.
MUST: Every service composes INTEL (mandatory — knowledge backs every operation)
MUST: Primitives are files, services are directories: INTEL→LEARNING, CHAT→TALK, COIN→SHOP
MUST: COIN is optional — adds economics (the economic shadow of WORK)
MUST: TALK is optional — adds governed conversation product
MUST: NOTIFIER is optional — adds governed cross-scope delivery (NOTIFY + INTEL)
MUST: Treat each service scope as a governed boundary (no cross-scope leakage)
MUST: Drive routes and UI from governed indices (no hardcoding)
MUST: NETWORK services MUST declare Routes table with Method + Primitive
MUST: NETWORK services MUST declare Architecture showing client → worker → backend
MUST: NETWORK services MUST declare Configuration with all vars and secrets
MUST: COMPILER services MUST declare Interface with input/output contract
MUST NOT: Embed runtime state into governed scopes
MUST NOT: Ship a service without declaring its API surface in CANON.md
SURFACE
SURFACE is the platform lane.
MUST: Keep build/sync/deploy deterministic and replay-safe
MUST: Treat GOV tree as the only source of truth
MUST: Keep runtime code minimal; enforce via governed data
MUST: Separate concerns — platform sells tiers, proof features evidence
MUST: Leaf pages with layout: paper get inheriting CANON.json — TALK walks inheritance chain
MUST: APP surface_type — Next.js App Router, reads galaxy.json + CANON.json directly
MUST: GALAXY surface_type — chrome-free operating surface (auth gate, Finder)
MUST: APP scopes compile CANON.md → CANON.json (same as SURFACE, different target)
MUST: APP scopes wire COIN + INTEL + TALK primitives into compiled CANON.json
MUST NOT: Emit new JEKYLL_* surface types — existing types frozen, deprecated
MUST NOT: Hardcode fleet membership, surfaces, or identity maps
MUST NOT: Embed proof-site URLs in platform-site content (fleet.json eco-bar only)
MAGIC
INTEL. CHAT. COIN. — Three primitives. One governed economy.
MUST: CANON.md in every scope
MUST: Services compose primitives — never duplicate
MUST: Primitive structure is fixed — industry is the only variable
MUST: Primitives compose into services — never duplicate
MUST: Services connect through SHOP.md and VAULT.md projection files
MUST: SHOP.md = public projection file (filesystem-discoverable, UPPERCASE per LANGUAGE)
MUST: VAULT.md = private projection file (filesystem-discoverable, auth-gated, UPPERCASE per LANGUAGE)
MUST: Instance = service projected through user governance context
MUST: Instance directories live at USER scope ({USER}/{PLURAL}/), not nested in SERVICES/
MUST: Service directories (SERVICES/{SINGULAR}/) define schemas — instances hold content
MUST: Every .md compiles to .json with the same name (direct mapping)
MUST: CANON.md = axiom + universal constraints only (no service names, no paths, no implementation)
MUST: README.md = how to run the CANON only
MUST: {SCOPE}.md = SPEC — the interface (purpose, routes, projections, ecosystem)
MUST NOT: Hardcode service names in CANON constraints (law speaks universals)
MUST: Inheritance resolves upward — scopes compose by directories
MUST: Tier algebra is canonical — DESIGN.md is the single source (COMPLIANCE tier algebra)
MUST NOT: Expose dimension internals to users or developers
MUST NOT: Hardcode outside governed contracts
MUST: Nonprofits get enterprise for free
MUST: ORG is the container; USER is the repo (`github.com/{org}/{user}`; duplicates across orgs allowed)
MUST: MARKET/ SALES/ GTM/ exist (META self-closure; one primitive each)
MUST: Each META sub-scope maps exactly one primitive (INTEL, CHAT, COIN)
MUST NOT: Add META business knowledge outside MAGIC/ scope
MUST NOT: Remove META sub-scope without replacing its primitive coverage
MUST: `{SCOPE}.md` is the scope contract surface; it MUST NOT be treated as a generic filename placeholder
MUST: LEARNING.md is the terminal — governance evidence, patterns, epoch rotation
MUST: LEARNING/ is the IDF directory — machine-generated individual data files
MUST: LEARNING.md rotates at epoch boundaries — frozen epochs archive as LEARNING-{EPOCH}.md at scope root
MUST: LEARNING.md is always the current epoch — active, append-only
MUST: Epoch boundary = EVOLUTION signal in LEARNING.md (named, dated, sourced)
MUST NOT: Delete archived LEARNING epochs — append-only history
MUST: MAGIC defines the triad interface directly:
MUST: COMPLIANCE/ + GALAXY/ + SURFACE/
MUST NOT: Define conflicting tier algebra in downstream scopes; downstream must inherit this contract
FINCHAT · SERVICE CONTRACT · CANONIC ∩
📊
FinChat
Community Learning for Finance Professionals
SEC filings. FRED 800K+ series. IRS code. Always free for students.