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. |
The method gives these promises an executable shape: Chainable + Composable Traits as Stories with Telescopic Organization, historically called USaT.
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 the reader's private notes or your own notebook. Bring your exercises to your human reviewer. This 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?
Notes are browser-local. Export a copy to keep them; they are not submitted or judged.
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.