The cap table doesn't create events — it listens to them. Click a source module below to trace how platform activity flows through the transaction ledger into investor positions.
Every platform event maps to a specific transaction type. The cap table inherits fields from the source record and computes derived values to update investor positions.
| Platform Event | Source Module | Transaction Type | Fields Inherited | Fields Computed | Position Effect |
|---|---|---|---|---|---|
| LP commits to deal | Deals / Commitments | Subscription | investorName, entityType, unitClass, committedAmount, units, unitPrice, adminFee, subscriptionDate | ownership% | +committed |
| Fee assessed (mgmt or transfer) | Deals / Commitments | Fee | feeType, feeAmount, investorName, relatedTransactionId | — | audit trail only |
| GP issues capital call | Capital Calls | Capital Call | callNumber, callDate, callAmount per LP, dueDate | running called total | +called, −uncalled |
| LP pays capital call | Payments | Capital Call (status update) | paymentDate, paymentMethod, paymentAmount | — | status → Settled |
| GP distributes returns | Distributions | Distribution | distributionDate, distributionAmount per LP, distributionType | running distributed total | +distributed |
| NAV update posted | Fund Admin | Valuation | valuationDate, navPerUnit, totalNav | per-unit values | updates NAV/unit |
| GP adjusts a record | Manual | Adjustment | propertyName, previousValue, newValue, reason | — | varies by field |
| Interest transferred | Deals (Secondary Offering) | Transfer | seller, buyer, units, pricePerUnit, tradeDate | ownership rebalance | −seller, +buyer |
Step through the lifecycle of Apex Growth Fund III to see how transactions accumulate on the ledger and roll up into investor positions over time.