Selected work

SplitFlow

Keep changing shares and payment claims in review.

A group expense changes as people opt out, question a share or say they have already paid. The organizer needs to see what is agreed and what still needs a decision before fronting the money.

Let code decide the amounts

Language helps draft a proposal. Typed calculation code handles item eligibility, KRW rounding and settlement balances. Splitting ₩10,000 three ways must still produce ₩10,000: ₩3,334 + ₩3,333 + ₩3,333. The remainder is assigned consistently.

Ask again when a share changes

Opting out of an item changes what the remaining participants owe. Recalculation moves the proposal into reconfirmation, so an earlier acceptance cannot approve a different amount. The review shows exclusions, individual shares and unresolved responses together.

A disputed claim still needs review

The dashboard makes an unresolved payment claim an organizer action. The readiness check originally caught claimed payments but missed disputed ones. The readiness fix and regression cases include both states, alongside conflicting claims, changed shares and rounding. A claim can no longer disappear from the readiness check just because it was disputed.

Demo scope

The interactive prototype uses local state and simulated participants. It demonstrates the agreement workflow and calculation guards; it does not verify bank transfers or move real money.

02Receipt-to-Form