Technical Reference
Catalyst Finance: Technical Reference and Integrations
Review the technical, data, lifecycle, validation, and integration contract for Catalyst Finance.
Catalyst Finance · Technical Reference
Governed financial workspaces, assumptions, drivers, statements, cash flow, budgets, scenarios, sensitivity, stress, valuation, capital, risk, review, export, and decisions.
Purpose
This reference summarizes the functional contract, record expectations, lifecycle, validation, export, compatibility, integration, privacy, and release-review requirements for Catalyst Finance.
Prerequisites
- Current release notes and repository documentation
- A test environment
- A backup and rollback plan
- Access to product health or package checks
- The synthetic all-feature sample
Sample data
This article uses a fictional Resilient Community Retrofit Program. The files contain one demonstration row for every documented feature, so each capability can be tested without private or production data.
Download CSV feature examples · Download JSON workspace example
Preview
| # | Feature | Sample action | Expected result | Classification |
|---|---|---|---|---|
| 1 | Model Workspace | create CF-RETROFIT-001 | a persistent finance workspace | synthetic-demo |
| 2 | Assumption Register | record tariff, grant, discount-rate, and project-life assumptions with sources | a traceable assumption set | synthetic-demo |
| 3 | Revenue and Cost Drivers | model square footage, kWh, tariff, maintenance, and implementation timing | driver-based projections | synthetic-demo |
| 4 | Three-Statement Model | connect income statement, balance sheet, and cash flow | integrated statements and balance checks | synthetic-demo |
| 5 | Cash Flow | schedule project payments, financing, operating savings, and maintenance | periodic cash flows | synthetic-demo |
The downloadable files include all 16 feature rows.
Technical contract
Canonical identity
| Field | Value |
|---|---|
| Product slug | catalyst-finance |
| Product name | Catalyst Finance |
| Verified version | 1.4.0 |
| Content pack | 1.0.0 |
| Default article state | draft |
| Human review | required |
Functional surface
| Capability | Sample operation | Expected artifact |
|---|---|---|
| Model Workspace | create CF-RETROFIT-001 | a persistent finance workspace |
| Assumption Register | record tariff, grant, discount-rate, and project-life assumptions with sources | a traceable assumption set |
| Revenue and Cost Drivers | model square footage, kWh, tariff, maintenance, and implementation timing | driver-based projections |
| Three-Statement Model | connect income statement, balance sheet, and cash flow | integrated statements and balance checks |
| Cash Flow | schedule project payments, financing, operating savings, and maintenance | periodic cash flows |
| Budget and Forecast | compare actual, budget, forecast, and variance | variance tables and explanations |
| Scenario Management | create downside, base, and upside assumption sets | scenario-specific statements and metrics |
| Sensitivity | vary tariff growth, savings realization, cost, and discount rate | a sensitivity table or chart |
| Stress Testing | apply a 20% cost overrun and delayed grant | liquidity and recovery effects |
| Valuation | calculate project NPV under the documented cash-flow timing | a valuation with explicit assumptions |
| Capital Structure | combine grant, debt, equity, and repayment terms | a funding structure and obligations |
| Risk Register | connect contractor, tariff, funding, and performance risks to mitigations | a finance risk record |
| Evidence and Sources | link assumptions to tariffs, contracts, studies, and historicals | a source-linked model |
| Review and Approval | record preparer, reviewer, exceptions, and approval state | a human-controlled review trail |
| Exports | produce statements, scenarios, model JSON, and audit bundles | portable inspectable files |
| Decision Studio Handoff | attach the reviewed scenario comparison to DS-RETROFIT-001 | a typed handoff with model version |
Core record fields
- Stable record or artifact ID
- Product and schema version
- Created and updated time
- Owner or responsible role
- Lifecycle or review state
- Source and provenance
- Units, period, geography, classification, or audience where applicable
- Validation findings and uncertainty
- Privacy and publication boundary
- Export or handoff integrity metadata
Lifecycle
Use a human-controlled lifecycle such as draft → review → approved/published, with revise, superseded, archived, withdrawn, failed, and recovered states where appropriate. Automated analysis may recommend; it must not silently approve, publish, or create private cases.
Validation
- Required-field and type checks
- Identifier and relationship checks
- Unit, period, geography, method, and classification compatibility
- Product and schema compatibility
- Source, evidence, and provenance completeness
- Permission, privacy, and publication-boundary checks
- Deterministic checksum or fingerprint validation for portable artifacts
Integrations
- Decision Studio
- Catalyst Data
- Workbench
- Knowledge Library
- Platform Core
Send the minimum required fields through a typed contract. Preserve source product, destination, schema, artifact ID, review state, provenance, consent or privacy boundary, and receipt. Private Contact and Engagement records never belong in public support or research artifacts.
Release review
- Confirm interface, service, manifest, package, and schema versions.
- Validate the all-feature sample.
- Run product tests and integrity checks.
- Test one export and each supported handoff category.
- Document breaking changes and migration path.
- Update Last Verified Version before publishing this article.
Expected output
- A complete feature contract
- A validated synthetic export
- A compatibility decision
- A documented integration receipt
- A release-integrity report
Verification
- Product slug, version, schema, and IDs agree.
- Every documented feature maps to an actual interface, command, route, or record.
- The sample files produce the stated artifacts.
- Integrations preserve provenance and privacy.
- Migration, rollback, support, and release documentation are current.
Responsible use
This is not investment, accounting, tax, or legal advice; consequential financial decisions require qualified review and authoritative records.