# Tasks Work in order. Finish a task's check before starting the next. 1. **Set up the project.** Pick the stack, add the database from the `database` input, a migration tool and a test runner. Check: an empty test run passes and the app answers on a health route. 2. **Create the schema.** Add the tables in `design.md`, leaving out the ones for options that are off. Check: migrations run from empty, and a test proves a second owner in one workspace is rejected by the database. 3. **Sign in (R1).** Build the method in the `sign_in` input, sessions, sign-out and the attempt limit. Check: the R1 acceptance tests pass. 4. **Workspaces (R2).** Create, list and switch. Check: the R2 acceptance tests pass. 5. **The permission gate.** Build the request flow from `design.md` and the matrix as data. Check: a table-driven test covers every cell of the matrix, including the non-member row. 6. **Notes (R7) and isolation (R5).** Build the sample resource on top of the gate. Check: the R5 and R7 acceptance tests pass. 7. **Invitations (R3).** Email invitations, revoke, accept, and invite links if `invite_links` is on. Check: the R3 acceptance tests pass with emails captured in memory. 8. **Members and roles (R4).** Member list, role changes, removal, leaving and ownership transfer. Check: the R4 acceptance tests pass. 9. **Audit log (R6).** Only if `audit_log` is on. Check: the R6 acceptance tests pass. 10. **Interface (R8).** Build the pages, using the person's `app_name` and `workspace_noun`. Check: every page can be used with a keyboard alone and at 360 pixels wide. 11. **Finish.** Write the README and run the whole test suite. Check: every item under "Definition of done" in `spec.md` is true.