A workshop makes three promises:
| Registration | Entry | Follow-up |
|---|---|---|
| Sign in with Google; collect no password. | Allow entry while the session is valid, even before email confirmation. | Send a confirmation message. |
Chainable Stories, also called USaT, connects a product promise to the Rust contracts that enforce it.
| A change arrives | What should change? | What should stay? |
|---|---|---|
| Require confirmation before entry. | The entry rule. | Google identity and the owed message. |
| Replace the identity provider's network client. | How verification runs. | Who may register and enter. |
Read at your own pace. Predict an outcome before opening Worked discussion. Open Engineering depth for code. Choose a reading path, or continue to the next lesson.
Use private notes or your own notebook. The workshop is a fictional example; its policies belong to the example.
Engineering Depth
A story is a compile-time abstraction. The compiler checks the selected relationships. Each registration still supplies real input and resources at runtime.
The code examples come from the complete Rust reference. Its small in-memory model makes the relationships visible.
Your Reflection
A participant enters, then closes the browser. What does the workshop still owe?
Saved in this browser. Export a copy before changing devices.
Worked Discussion
The confirmation message remains owed. Entry and delivery can proceed independently under this policy. The workshop must retain the pending work after the browser leaves.