FSO Learning

What-If Cases

Two Stores Both Have Record 7

A compatible type does not identify the same version or resource.

Case Established fact Attempted substitution
A Work belongs to store A, record 7. Send its handle to store B, record 7.
B The reviewer approved version 7. Publish version 8 under that approval.

The values have compatible types. Identify the missing relationship in each case.

Engineering Depth

The reference checks the actual workshop instance:

if !Arc::ptr_eq(&self.workshop.identity, &self.session.workshop) {
    return Err(EntryFailure::ForeignSession);
}

A proposal story would also retain the approved version or digest. Check it when publishing, using the current stored record. CS-06.

Your Reflection

What would you bind in the state? What would you recheck after a human delay?

Worked Discussion

A needs the same store instance and record. B needs the exact reviewed content. A new source observation can be valid later input if it identifies the original work; a replacement proposal needs its own decision.

Navigate