These milestones come only from Talebound's documented future notes. No speculative detours, no gamified shortcut systems — just the next pieces already on record.
Documented milestones
First milestone
Finish the live-domain rollout and real browser verification so Talebound can welcome visitors on its documented public home.
Source: docs/architecture/production-deployment.md — “Production domain” and “What must still happen on the real VPS”.
Next stop
A future login option already named in the planning notes, alongside the existing Google OAuth and magic-link flow.
Source: plan.md — “Out of scope (Full App, deferred): ... Apple Sign In”.
Further along
Protect the live road a little better once Talebound is out in the world, without changing the slow-letter heart of the product.
Source: docs/architecture/production-deployment.md — “Not yet in scope: rate limiting, WAF... separate future phases”.
Packing carefully
Documented future deployment work includes moving production secrets into a manager and putting a real backup-and-restore plan behind the scenes.
Sources: docs/architecture/production-deployment.md — “secret manager, backups”; plan.md — single-VPS note calling for a basic backup/restore plan from day one.
Keeping watch
Future operational visibility is already called out so Talebound can be watched over as it grows beyond a single quiet launch.
Source: docs/architecture/production-deployment.md — “monitoring — separate future phases”.
