Matter Stack Review Activities
Matter Stack Review Activities
Technical boundaries. This activity traces a user action from joining and trust through the request, reply, and visible outcome, with failure cases and a release check. It assumes the team can supply a consistent device identity, time, and action record; it does not execute the trace or determine which actions a particular device supports or permits.
Write one user action as a trace. Name the device, its shared home, the target function, the person allowed to act, and the result the user should see. Then follow join, trust, session, request, device path, reply, and visible outcome. Keep the same time and device identity across each record.
Test a wrong device path, a missing feature, an expired session, a lost reply, a repeated request, and a sleeping device that wakes late. Check that a rejected action is clear and safe. Being able to reach a device does not prove that the action is allowed or supported.
Use a short release check. Can the team name the action? Does each step keep the same device and time? Does a denied act stay safe? Can a second person repeat the trace? Is each open gap owned? If any answer is no, stop and repair the record.