RunsLab run · 11 November 2026, 00:56 UTC
Products that depend on each other
When one product depends on another, is the dependency declared, are breaking changes refused, and is the dependent told what changed?
15/15 passed1 h 34 min
Setup
- Chains
- Satsuma lab chain
- RoleHome
- KeptLab, not retained
- RoleProving
- KeptLab, not retained
- Users
- UsersSynthetic
- Model
- Claude Opus
- ModeLive and replayed
- Operator seat
- SeatBy delegate
- Unattended
- Yes: nobody was watching to step in
- Time
- 1 h 34 min · ended 02:30 UTC
Checklist 15 items
Every item, unless its row says otherwise
- ChainLab
- UsersSynthetic
Products that depend on each other
14/14 passed
Pass14 items passedShow them
PassAn auction that depends on an escrow is proposed, refused once for naming an unpublished interface, approved, built and deployed1 of 1 attempts
- DecisionsLive model
PassAn auction built by the system settles its sales into an escrow it depends on1 of 1 attempts
- DecisionsLive model
- escrow0x977b6573CCC8aC42e78a52177f6Fb0c8477A60C2Satsuma lab chain, not retained
- auction0x61aeB57a362a3327cc8b45d86ABAead4f18E2200Satsuma lab chain, not retained
- settledEventsFromTheAuction.0 · block 1,9760x7b1863824dae195e8c4a30cbb306e35092b11343b15f2ff9da1d1c53d8643135Satsuma lab chain, not retained
- declaredIn · block 3990xb8d442044206da205666f5633b3e4c8377c9112c50a9513725081ff3a036263aSatsuma lab chain, not retained
PassWhen the escrow is frozen, the decision names the product that depends on it1 of 1 attempts
- DecisionsLive model
- acknowledgments.0 · block 2,0470x77cc74addba5f08d019c3f140bf072936fe8acf89e6c010e1860ad31a731fef7Satsuma lab chain, not retained
- freezeTx · block 2,0970xe8287789b1c85d45cc4d1e909b8fe6baaf0d5f53f4efe6e05ba46d212d8cd899Satsuma lab chain, not retained
PassThe dependent product is told of the freeze1 of 1 attempts
- DecisionsLive model
PassA request from a dependent is recorded as evidence, not applied as a change1 of 1 attempts
- DecisionsLive model
PassA sale on the auction reaches the escrow across the two chains1 of 1 attempts
- DecisionsLive model
PassA change that would break a dependent is refused, a compatible change passes, and a breaking one passes once the dependent's move is recorded1 of 1 attempts
- DecisionsLive model
PassA build that relies on an unpublished version of another product's interface is refused before anything is submitted1 of 1 attempts
- DecisionsLive model
PassA build that uses another product without declaring it is refused on every attempt1 of 1 attempts
- DecisionsLive model
PassThe refusal names the file and the interface at fault1 of 1 attempts
- DecisionsLive model
PassThe refused build is abandoned1 of 1 attempts
- DecisionsLive model
PassNo product is registered from the refused build1 of 1 attempts
- DecisionsLive model
PassNo interface is published from the refused build1 of 1 attempts
- DecisionsLive model
PassNo dependency is recorded from the refused build1 of 1 attempts
- DecisionsLive model
Lineage to the objective
1/1 passed
PassThe record of objectives and products holds the dependency1 of 1 attempts
- DecisionsLive model
What this proves
- Whether, in this run, the gates on dependencies refused what they should and let through what they should, and whether the dependent was told.
What it does not
- Behaviour with more than two products in a dependency.
- The model's own judgment beyond the calls that were live.
What broke, what was fixed
The record of this run does not say whether a person stepped in, so it does not count as a run without repairs.
Cost in tokens
Not recorded: this run has no chain-derived scorecard.
Archived evidence
The lab chains this run used were reset afterwards and are not retained, so nothing here links to an explorer. The record below is the archived copy.
- Scorecard
- None archived.