Task “Read chapter” + 25, rule 2/remaining/3. Expected: Prepare 2, Focus 20, Reflect 3.
Account-free · client-side · no storage · no network
Study Sprint Interaction Lab
Configure one transparent rule, run normal and missing-input cases, inject a controlled state bug, and trace what the browser did. This lab is a course-owned full-credit route when an own-app or coding environment is unavailable.
2. Observe the result
Initial state
Commit an expected result before running a test.
| Stage | Current evidence |
|---|---|
| Input | No run yet. |
| Event | No run yet. |
| Validate | No run yet. |
| Rule | No run yet. |
| State | No run yet. |
| Output | No run yet. |
Three required cases
Predict first. Run second. Record expected and actual separately.
Blank Task + 25. Expected: linked Task message, focus Task, preserve 25, render no plan.
After 15 minutes, change to 45. Expected: new 2/40/3 result replaces the old result without duplication.
Architecture boundary
This lab demonstrates local intelligence only.
Required Topic 9 route. Browser input, event, transparent transformation, state, and output. No network or secret.
Concept only. Adds a network request, response/status checks, source questions, CORS (the browser rule that lets a page read another site’s data only when that site allows it), downtime, and new privacy decisions.
Not a Topic 9 build. A private key never belongs in browser-delivered code; an approved server-side boundary would be required.