Read-only sources
Attestations, ledgers, alerts, and statements enter through scoped references and hashes.
OpenIBank
Financial AI is useful only when it is bounded. Hermon Finance should work with read-only data, risk controls, audit receipts, approval gates, and explicit denial of settlement execution, unauthorized trading, credential exposure, and compliance bypass.
Financial operators, compliance teams, treasury analysts, product builders, and model-risk reviewers.
Thesis
This domain hub is designed for two jobs at once: educate serious users and create better training direction for Hermon adapters. The same vocabulary appears in tutorials, demos, eval rubrics, and model output contracts.
Architecture Map
Hermon Finance prepares analysis packets. OpenIBank and MapleAI control data scope, approvals, audit receipts, and no-settlement defaults.
Attestations, ledgers, alerts, and statements enter through scoped references and hashes.
The model summarizes risk, thresholds, evidence gaps, and escalation recommendations.
Policy checks enforce read-only access, risk controls, human approval, and no settlement.
Receipts preserve sources, assumptions, reviewer state, and safe no-action outcomes.
Research Questions
How can an AI model assist finance without giving personalized investment advice or moving funds?
What fields prove a finance proposal is read-only, auditable, and reviewable?
How should AML/KYC triage separate summarization from regulated decisions?
How should model-risk management handle adapters that improve but still fail one operational field?
Core Concepts
The model may summarize, compare, flag, classify, and prepare review packets. It should not execute settlement, trades, transfers, or irreversible account changes.
Treasury monitoring means liquidity thresholds, issuer exposure, reserve attestation freshness, redemption pressure, exception queues, and escalation paths.
Every consequential recommendation should record input hashes, data sources, policy version, risk summary, approval state, and no-action or rollback state.
Hermon Finance should support operations, compliance, and explainability. It should avoid personalized investment advice and regulated decisions without human review.
Tutorial Series
Each lesson includes foundations, applied architecture, a lab prompt, evaluation checks, and an output contract that can become training data or demo validation.
What Hermon Finance may do, what it must not do, and how to encode that boundary.
Open lessonHow a finance model can support reserve monitoring without taking over treasury authority.
Open lessonHow Hermon Finance can help compare ledgers, statements, and attestations while preserving auditability.
Open lessonHow to support compliance review without auto-clearing regulated cases.
Open lessonHow OpenIBank should evaluate, document, and promote finance adapters.
Open lessonHow Hermon Finance, Maple AI OS, and OpenIBank can form a governed financial operating stack.
Open lessonIndustrial Map
Stablecoin reserve monitoring, attestation checks, issuer concentration, liquidity scenarios, and escalation thresholds.
OpenIBankLedger-to-bank matching, exception triage, statement comparison, and evidence packet preparation.
OpenIBankRead-only summarization of alert context, missing evidence, risk factors, and review queue routing.
OpenIBankEvaluation packs, refusal tests, adapter promotion records, and documented limitations for regulated operations.
OpenIBankReading Map
Regulatory context for AI risk, operational resilience, and financial-sector supervision.
Financial Stability Board: The Financial Stability Implications of Artificial IntelligencePolicy context for AI governance, vendor concentration, model risk, and financial stability.
Use the tutorials as user education, data-generation prompts, eval design, and demo scenarios for the next Hermon adapter cycle.