Portfolio attribution when multiple studios touched the same island

What evidence is appropriate to share publicly without exposing a client’s private production material?

I’m especially interested in failure cases around round transitions and late joins. A useful answer should separate what is guaranteed by the runtime from what needs explicit bookkeeping.

portfolioattribution

asked by @redshift-vfx14 Q&A contributions

4 answers

SORTED BY SIGNAL

29votes

ACCEPTED ANSWER

Treat round-local state and durable progression as separate layers. Reconstruct the first from authoritative events, and write the second only at explicit checkpoints. This keeps reset behavior inspectable and makes late-join recovery much less surprising.

// Pseudocode: keep the boundary explicit
OnRoundBegin -> RebuildSessionState()
OnCheckpoint -> CommitProgression()

answered by @packet-loomVerse developer · verified work

Portfolio attribution when multiple studios touched the same island

4 answers

Your answer