Everything I could decide myself is decided. What's left needs
you. Each one has a recommendation from Fable — if you agree, pick it and
press Done. "I'm not sure" is a real answer and becomes work for me.
You don't need to open the session — pressing Done sends your answer back and it picks up.
1Two different things are both scheduled first. Ruling D-0909-3 moves the read-side isolation work into the early phases, baked in from day one. Separately, the first signed external client asked whether renewals could come first. Both change what the team builds in week one, in different directions. Which goes first?
In plain terms. Which comes first: the isolation work, or renewals for the new client? You ruled that isolation should be baked in from day one and moved into the early phases. Separately the first client who signed asked if we could do renewals first, and Fede said he was looking into it. Both were said in the same week and both claim week one. Doing isolation first means the new client waits for the feature they asked about; doing renewals first means we keep building on rows that a brand-new company can still read across.
Fable recommends: Isolation first, renewals after It is your own ruling and the harness shows 21 of 22 correct-behaviour cases still failing today, so every feature built before it is built on rows the wall does not yet protect, and the first client is also the cheapest moment to have the wall already standing Tried first, unsuccessfully: I did not decide this. Both statements are yours or your co-founders' from this week, and they conflict on ordering rather than on substance, so there is no row I can write that satisfies both. I checked the plan for an existing order and it prices the isolation work in the early phases without accounting for a client-requested workflow arriving ahead of it.