Overview
A commitment record connects an allocator with a fund; some source records instead describe reported fund positions and must be labeled accordingly.Field groups
- Commitment context
Field reference
SOURCE_DEPENDENT describes availability; access is a separate product/rights boundary. Null means unknown, not false or zero.Allocator
Field ID:commitment.allocator. Group: Commitment context.
The allocator organization associated with the fund record.
Evidence / dates: Use only the source or event date actually recorded; record modification is not verification.
Limitation: Not the manager or the fund itself.
Fund
Field ID:commitment.fund. Group: Commitment context.
The fund named in the commitment or reported-position record.
Evidence / dates: Use only the source or event date actually recorded; record modification is not verification.
Limitation: A shared fund does not establish a personal relationship.
Manager
Field ID:commitment.manager. Group: Commitment context.
The related fund manager where recorded.
Evidence / dates: Use only the source or event date actually recorded; record modification is not verification.
Limitation: Manager identity remains distinct from fund identity.
Record meaning
Field ID:commitment.record_kind. Group: Commitment context.
Whether the source describes a commitment or a reported fund position.
Defined values: commitment, reported_position; null when unknown.
Evidence / dates: Use only the source or event date actually recorded; record modification is not verification.
Limitation: Do not collapse these into allocations, ownership, mandates or current appetite. Unknown meaning requires review.
Recorded amount
Field ID:commitment.amount. Group: Commitment context.
Recorded amount in the stated currency.
Evidence / dates: Use only the source or event date actually recorded; record modification is not verification.
Limitation: Some filing-derived amounts are reported positions, not original commitments. Missing is unknown, not zero.
Amount currency
Field ID:commitment.currency. Group: Commitment context.
Recorded native currency.
Evidence / dates: Use only the source or event date actually recorded; record modification is not verification.
Limitation: No normalization or implied FX conversion.
Commitment date
Field ID:commitment.commitment_date. Group: Commitment context.
The commitment date where separately recorded.
Evidence / dates: Use only the source or event date actually recorded; record modification is not verification.
Limitation: Do not manufacture it from a reporting year or publication date.
Reporting year
Field ID:commitment.reporting_year. Group: Commitment context.
Year of the source reporting period where recorded.
Evidence / dates: Use only the source or event date actually recorded; record modification is not verification.
Limitation: Not the original commitment date, current mandate or last verification.
Relationships to other entities
Allocator, fund and manager are separate entities. The date of commitment is distinct from the reporting year. A commitment is not an asset-class allocation, company ownership, generic investment event or current mandate.institutional-investor
Fictional request brief, entities, sources, values and dates. This is a documentation example, not a live HTTP response or customer result. Missing dates remain null.Current availability: Reviewed bounded request. Execution: Manual / scoped. Automated invocation: Not currently available. API endpoint: None. MCP execution: None.
- Input
- Result
- Evidence
A research brief for human scope review, not an API payload.