Funding Database Responsibilities

Why This Exists

This document defines conceptual database responsibilities for the Funding Domain.

It does not define SQL implementation, final schemas, migrations, or storage technology.

Owner

The owner is the Chief Product Officer and Enterprise Architect.

Business Value

Clear persistence responsibilities make funding needs, assessments, applications, risks, repayments, and recommendations auditable and reusable.

Conceptual Tables Or Collections

Conceptual table or collection	Responsibility
funding_needs	Funding needs and source context.
funding_products	Funding product catalogue.
funding_partners	Funding partner profiles and supported products.
working_capital_assessments	Assessment records and readiness scores.
eligibility_assessments	Product and partner eligibility assessments.
funding_recommendations	Recommendation records and rationale.
funding_applications	Application workflow state.
cash_flow_risks	Cash-flow risk records.
repayment_schedules	Repayment plans.
repayment_entries	Individual repayment status records.
funding_audit_log	Funding changes and workflow audit.

Indexing Considerations

Future implementation should consider indexes for FundingNeedId, OrganizationId, ContractWorkspaceId, product type, partner ID, application status, risk level, repayment due date, and recommendation decision.

Ownership Rule

Funding storage is canonical for funding workflow state. It must not become the canonical store for organization financial profile facts, contract facts, marketplace display state, or intelligence reasoning.