Snapshots and loan events remain separate records. The latest applicable snapshot anchors the carrier policy-loan balance on its effective date; a draw, repayment, or Current Balance correction records what changed and why. Historical draw rows can preserve original and current-remaining amounts without moving that carrier balance.
Event First, Then Snapshot
You record a $5,000 repayment through Log repayment. The Banking Ledger gains a Loan Repayment entry and the tracked loan balance decreases by $5,000.
When a later snapshot records the carrier's balance, Policy Stack reconciles the persistent carrier account through an append-only adjustment. If a nearby event already explains the change, Policy Stack can avoid asking about it again.
Snapshot First, Then Follow-Up
You record the carrier snapshot before recording the $5,000 repayment. The snapshot anchors the balance. If Policy Stack detects the decrease, the follow-up records the repayment and its draw assignment without applying the balance decrease again.
If the follow-up is skipped, no repayment record or draw assignment is created. The carrier balance and snapshot history are still preserved.
No Double Application
Policy Stack checks whether the snapshot already reconciled the account. A follow-up either applies a new event once or records only the characterization and draw assignment. The same draw or repayment is never applied twice. A nominal rise is recorded as capitalized interest, not as a new draw.
Correcting a Tracked Balance
Editing the latest applicable snapshot updates the carrier anchor through a reversal-and-reapply correction. Editing a backdated snapshot changes history without overwriting a newer carrier balance. Correct the applicable draw or repayment record when its characterization is wrong.