docs: record first-deployment model and manual schema initialization
This commit is contained in:
1 parent
ff055c972d
commit
ca019abb14
14 files changed
+124
-62
No files matched your search
@@ -0,0 +1,47 @@
|
||||
# Task: Record first-deployment model and manual schema initialization
|
||||
|
||||
## Identity
|
||||
|
||||
- Task ID: 20260814-deploy-model-reconcile-9b4c2e7f
|
||||
- Mode: Integration
|
||||
- Branch: main
|
||||
- Worktree: /Users/brother7/Documents/AI/NianAIGC
|
||||
- Base commit: ff055c972de50f34ac6eabf3e977610949482bba
|
||||
- Owner: dsh
|
||||
- Status: Ready for Integration
|
||||
|
||||
## Scope
|
||||
|
||||
- Apply two human decisions from 2026-08-14 to canonical memory and deployment documentation:
|
||||
1. There is no production cutover: the first production deployment runs the ADR-003 split topology (Next.js frontend + Go backend) directly; no legacy production instance, no Node Worker in production.
|
||||
2. Schema initialization is executed manually with the versioned SQL files; the ACK migration Job pod is not deployed.
|
||||
- Related: the first super administrator is created from `ZHINIAN_BOOTSTRAP_ADMIN_*` configuration at Go startup (implemented in task `20260814-go-bootstrap-admin-6e2b7d9c`); legacy account import is not required.
|
||||
|
||||
## Intent And Constraints
|
||||
|
||||
- Keep the versioned-SQL discipline (RDS-002); only the execution mechanism changes from the one-shot Job to manual execution.
|
||||
- Do not claim any production validation that has not happened.
|
||||
- Keep the migration Job manifest on disk, marked deprecated, for optional future automation.
|
||||
|
||||
## Outcome
|
||||
|
||||
- Added `DEP-001` to the decision index; moved `ACK-001` to Superseded Decisions; amended `RDS-002` execution detail; updated the ADR-003 status to "first production deployment pending".
|
||||
- Rewrote `current-state.md` Current Focus, Next Recommended Steps, Open Questions, and Risky Areas around the first-deployment model; recorded `ff055c9` under Integrated Through.
|
||||
- Updated `system-overview.md`, `module-map.md`, and `data-flow.md` to describe the split-topology first deployment and manual schema initialization.
|
||||
- Updated `commitments.md` (dropped cutover obligations; added Go deployment artifacts, manual schema init, bootstrap config, and first-rollout validation commitments) and `business-rules.md` (manual schema execution rule; removed the moot cookie-compatibility question).
|
||||
- Updated deployment guidance in `docs/DEPLOYMENT.md`, `README.md`, and `README.zh-CN.md` to manual SQL execution and config-driven bootstrap; marked `deploy/ack/migration-job.yaml` deprecated with a header comment.
|
||||
|
||||
## Verification
|
||||
|
||||
- `check_project_docs.py` and `check_doc_drift.py --task-id 20260814-deploy-model-reconcile-9b4c2e7f` pass.
|
||||
- `npm run deploy:check` passes with the deprecated manifest comment in place.
|
||||
|
||||
## Follow-ups
|
||||
|
||||
- Build the Go workload deployment artifacts (image, manifests, Ingress split) for the first production deployment.
|
||||
- Execute the manual schema initialization and role grants against the real RDS before the first rollout.
|
||||
- Decide whether to delete the deprecated `migration-job.yaml` later.
|
||||
|
||||
## Promotion Candidates
|
||||
|
||||
- None beyond what this integration task already applied.
|
||||
Reference in new issue
Block a user