M4 — Release and Support v0.1 Beta: Admin and Issuing

SOW Deliverable(s): D5a, D5b — Deployment Package (release scripts, deployment instructions, artefacts) Requirement source: SOW Appendix 2 milestone table; Appendix 3 (Deployment/validation acceptance basis)

Tasks

ID	Task	SOW Ref	Requirement Clarity	Dev Status	Task File
M4-01	v0.1 Beta release package & deployment (Admin + Issuing, from M2/M3 scope)	D5a	✅	🟡 Live on a single AWS EC2 instance (Docker Compose + Caddy, auto-TLS via DuckDNS) as of 2026-08-17 — client-testable now, but this is a dev/staging-style deployment, not yet the formal ECS/Elastic Beanstalk production target	M4-01-v01-beta-release-package-deployment.md
M4-02	Beta bug-fix / support cycle for v0.1	D5b	✅	⚪	M4-02-beta-bugfix-support-v01.md

Notes

M4 is a release/deployment milestone, not a new feature-build milestone — its content is entirely "package and ship what M2/M3 built." As of 2026-08-17 the app is actually deployed and reachable (curorec.duckdns.org, docs at docs-curorec.duckdns.org) on a single EC2 instance running the full stack via docker-compose.server.yml (Caddy reverse proxy/TLS, Postgres, Redis, backend, frontend, docs) — enough to unblock client testing. Whether this single-instance EC2 setup is the final production target or a stepping stone to a managed AWS service (ECS, Elastic Beanstalk) is still an open decision or worth explicit sign-off.