Work journal, auth + the mobile app
v0.3releaseThe first pillar is live. You can write in Flexmywork.
The journal. Write an entry, edit it, delete it, and file it as work, project or learning. That is the whole feature, deliberately. It is the source of truth every later pillar reads, so it had to be boring and correct before it was allowed to be clever.
Signing in. Magic link or Google. There are no passwords anywhere in the product, so there is nothing to reset, nothing to stuff, and no hashes to leak.
One-line summaries. Each entry gets a single-sentence summary from Claude Haiku, so a long entry is still scannable in a list six months from now. The 160-character limit is enforced in code after the model answers, not merely requested in the prompt. A model asked politely for brevity will sometimes decline. A length check will not.
Row-level security. Every table is default-deny, keyed to the signed-in user. The database decides who may read a row, not the application, so a query with a forgotten filter returns nothing rather than someone else's journal. It is tested in both directions with pgTAP: the owner reads their rows, a stranger reads zero.
The site. flexmywork.com, the blog, and this changelog.
Mobile. An app for iOS and Android sharing the same logic layer as the web app: the same queries, the same validation schemas, the same rules. Only the screens are written twice, on purpose.
Tests. Unit tests, end-to-end flows in Playwright, and the database policy tests, all running in CI.
Where this actually stands: it is early. One pillar of four is built. The journal is solid, everything around it is thin, and there are edges nobody has found yet because not enough people have used it.
Next is the master resume, assembled from the entries you have logged, and ATS-clean PDF export. No dates on those. They ship when they are right.