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
SURFACE_BUILD
GOV
FINCHAT community learning surface built — 8 community learning cards sourced from TALKS/FINCHAT meta-patterns (marginal vs effective rate, LTCG vs STCG, FRED vintage dates, RVU components, SEC filing cadence, healthcare finance bridge, disclaimer, filing triggers)
GOV
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 community learning fleet. 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
SERVICES
SERVICES compose primitives — INTEL + CHAT + COIN. Every service governed. Every scope discovered.
MUST: Maintain TRIAD integrity (CANON.md + VOCAB.md + README.md)
MUST: Treat SPEC as scope identity (`{SCOPE}` directory), not as a file
MUST: Every SERVICE scope include ROADMAP.md, COVERAGE.md, LEARNING.md, and `{SCOPE}.md` as governed content surfaces
MUST: Discover SERVICE scopes from filesystem only (no manual catalog)
MUST: Keep http:// and magic:// on the same namespace (transport differs, scope path matches)
MUST: CANON.md = axiom + universal constraints (no service names, no paths, no implementation)
MUST: README.md = how to run the CANON (nothing else)
MUST: {SCOPE}.md = SPEC — the interface (purpose, routes, projections, ecosystem)
MUST: SHOP.md = public projection file (per scope, filesystem-discoverable)
MUST: VAULT.md = private projection file (per scope, filesystem-discoverable)
MUST: Runtime implementation remains under ~/.canonic; this workspace is governance-first
MUST NOT: Hardcode service names in CANON constraints (law speaks universals)
MUST NOT: Define ungoverned terms outside VOCAB.md
MUST NOT: Treat `{SCOPE}.md` as SPEC identity
MUST NOT: Move architecture/lifecycle into README
MUST NOT: Leak private projections to public surfaces
MUST NOT: Maintain duplicate mapping tables outside generated manifest outputs
MUST NOT: Add runtime jargon to governance contracts
MUST: Ledger-consuming services declare source ledgers, scope filters, and closure gates
MUST: Learning governance remains live — closure claims require fresh DISCOVER → GENERATE → RELINK evidence
hadleylab-canonic
HADLEYLAB ships software. Every app, book, paper, deal, and patent is PROOF that MAGIC works. COIN = WORK. LEARNING = COMPUTE.
MUST: Every app, book, paper, deal, or patent is evidence of MAGIC
MUST: All scopes inherit canonic-canonic/CANONIC.md governance
MUST: All users governed under USERS/ via SERVICES/USER
MUST: Cross-index INTEL across users (INTEL.md)
MUST: Shared events propagate to ALL affected user dashboards
MUST: Maintain governance workspace purity (.md files only)
MUST: Ledger all COIN (validated work) through MAGIC 255
MUST: Compile all INTEL from governed sources
MUST: Keep frontend/runtime implementation under ~/.canonic (hidden runtime)
MUST: Surface governed TALK, Library, and SERVICES scopes (no orphan content)
MUST: Derive nav labels from governed scope names (no hardcoded strings)
MUST NOT: Publish without governance (CANON.md required)
MUST NOT: Duplicate primitives — compose from INTEL, CHAT, COIN
MUST NOT: Silo intelligence inside a single user when multiple are affected
MUST NOT: Expose VAULT contents outside NDA scope
MUST NOT: Store runtime artifacts in governance workspace
canonic-canonic
SPEC is governance. `canonic-canonic/` is the spec root.
MUST: Keep this repo governance-only (.md/.pdf)
MUST: Publish workspace mapping in CANONIC.git (no hardcoded repo lists)
MUST: Preserve three primary lanes: FOUNDATION, INDUSTRIES, MAGIC
MUST NOT: Commit runtime artifacts here (runtime belongs in ~/.canonic/)
MUST: Sell MAGIC tiers — the product, not the proof (proof is hadleylab-canonic)
MUST NOT: Embed beta-test app URLs in platform page content
FINCHAT · SERVICE CONTRACT · CANONIC ∩
📊
FinChat
Community Learning for Finance Professionals
SEC filings. FRED 800K+ series. IRS code. Always free for students.