3.0 KiB
3.0 KiB
Commitments
Track future-facing memory: promised follow-ups, unfinished loops, timed checks, and restart points.
| Date | Commitment | Trigger / Due | Owner | Status | Next Action |
|---|---|---|---|---|---|
| 2026-08-12 | Validate migration, TLS, permissions, and readiness against the real Alibaba Cloud RDS instance. | Before the first production rollout | Deployment owner | Open | Back up RDS, provision roles/CA/network access, then execute the SQL files manually. |
| 2026-08-12 | Keep each workload at one replica until generated assets use OSS or another shared store. | Before raising replicas | Deployment owner | Open | Configure and validate external object storage. |
| 2026-08-12 | Harden the runtime image to non-root after writable paths are designed. | Security hardening follow-up | Application owner | Open | Define ownership for runtime and settings paths, then update Docker/ACK security context. |
| 2026-08-12 | Implement ADR-003 only after executable compatibility contracts exist. | Before starting the Go migration | Application owner | Completed | Contracts exist under contracts/; Go implementation merged 2026-08-14. |
| 2026-08-14 | Build the Go workload deployment artifacts: container image, ACK Deployment/Service manifests, and Ingress routing that sends page/static paths to Next.js and /api, /uploads, /generated-results to Go. |
Before the first production deployment | Application owner | Completed | backend/Dockerfile, deploy/ack/go-api.yaml, and the split Ingress are merged (2026-08-14); remaining work is image build/push and cluster dry-run validation. |
| 2026-08-14 | Initialize the production schema by manually executing database/migrations/0001_initial_schema.sql, then 0002_generation_lifecycle_fencing.sql, then the application-role grants. No migration Job pod is deployed. |
Before the first Go/Web rollout | Deployment owner | Open | Run the SQL as the migration role against RDS and verify the application-role grants with the readiness checks. |
| 2026-08-14 | Configure ZHINIAN_BOOTSTRAP_ADMIN_PHONE / ZHINIAN_BOOTSTRAP_ADMIN_PASSWORD / ZHINIAN_BOOTSTRAP_ADMIN_NAME for the first Go startup; the process creates the first super administrator exactly once. |
First Go startup | Deployment owner | Open | Provide strong bootstrap credentials through the deployment Secret/ConfigMap. |
| 2026-08-14 | Validate the Go backend against non-production RDS, real OSS, provider credentials, and external Webhooks before the first production rollout. | Before the first production deployment | Deployment owner | Open | Stand up non-production RDS/OSS and run the contract and recovery suites against the Go binary. |
| 2026-08-14 | Confirm the public /api/v1 support promise for external consumers. |
Before the first production deployment | Product owner | Open | Product decision on which v1 endpoints and behaviors are guaranteed for partners. |
Use
Record only commitments that should affect future sessions. Routine next steps can stay in 30-worklog/current-state.md.