suppose a round is raising Series AA shares, or Series Seed shares.
the cap table would define a price per share, and there would be a certain number of shares shown in the amount_raised row.
the preemptive waiver template would describe the eligibility to participate, in terms of number of shares.
suppose the user wants to switch the instrument to convertible notes.
the user (in v1) would have to manually delete the number-of-shares, and the price-per-share, etc, from the cap table.
then the preemptive waiver template would describe eligibility in terms of amount of money instead of amount of shares.
but if the end-user forgets to make the necessary changes to the cap table, the preemptive waiver document comes out looking really weird.
it would be nice if, in v2, the change-of-security-type operation correctly updated all these fiddly bits so the preemptive_waiver template automatically produces the right output.
suppose a round is raising Series AA shares, or Series Seed shares.
the cap table would define a price per share, and there would be a certain number of shares shown in the amount_raised row.
the preemptive waiver template would describe the eligibility to participate, in terms of number of shares.
suppose the user wants to switch the instrument to convertible notes.
the user (in v1) would have to manually delete the number-of-shares, and the price-per-share, etc, from the cap table.
then the preemptive waiver template would describe eligibility in terms of amount of money instead of amount of shares.
but if the end-user forgets to make the necessary changes to the cap table, the preemptive waiver document comes out looking really weird.
it would be nice if, in v2, the change-of-security-type operation correctly updated all these fiddly bits so the preemptive_waiver template automatically produces the right output.