LESSON 01 OF 03 · WRITTEN GUIDE
Map data and permissions
A prototype may use sample data and device-local storage. A real multi-user product must decide who owns each record and who can read or change it. Those decisions need to be enforced on the server, not just hidden in the interface.
Make it practical
Map each record, its owner, who can read it, and who can modify it. Label sample data and local-only behavior. Before adding accounts, write an acceptance check showing that one user cannot access another user’s records.
TRY THIS PROMPT
Review this product data map. Identify missing ownership and permission rules. Distinguish interface visibility from server enforcement. Do not generate a production authentication system from assumptions.
Check your work
Can every record be tied to an owner or explicit shared rule? Are private values kept out of client code? Are authorization checks part of the implementation plan?
Use the output as a draft. Compare it with the brief, inspect the work, and keep the decisions you can explain.