docs: reconcile canonical memory with merged Go backend
This commit is contained in:
1 parent
f10cdd9695
commit
eacb4c67de
14 files changed
+171
-57
No files matched your search
@@ -11,7 +11,7 @@
|
||||
|
||||
## Approved Target Flows
|
||||
|
||||
These flows become active only after ADR-003 is implemented:
|
||||
The Go implementation for these flows is merged into `main` under `backend/`; they become active only after the single-writer deployment cutover routes traffic to Go and drains the Node Worker:
|
||||
|
||||
| Flow | Source | Destination | Required behavior |
|
||||
|---|---|---|---|
|
||||
@@ -34,8 +34,8 @@ These flows become active only after ADR-003 is implemented:
|
||||
- Alibaba Cloud ACK resources under `deploy/ack/`.
|
||||
- Internal Worker HTTP endpoint is cluster-internal and blocked from public Ingress routing.
|
||||
|
||||
In the approved target, the internal Worker HTTP endpoint is removed only after the Node Worker is drained and the Go WorkerLoop is verified. It remains part of the current implementation until that cutover.
|
||||
In the approved target, the internal Worker HTTP endpoint is removed only after the Node Worker is drained and the Go WorkerLoop is verified. It remains part of the deployed implementation until that cutover.
|
||||
|
||||
## Last Updated
|
||||
|
||||
2026-08-12
|
||||
2026-08-14
|
||||
Reference in new issue
Block a user