Skip to content

Commit 645ded0

Browse files
author
DavidQ
committed
define remote deployment candidate for authoritative server — PLAN_PR_LEVEL_12_6_REMOTE_DEPLOYMENT_CANDIDATE
1 parent 5e91c8d commit 645ded0

7 files changed

Lines changed: 126 additions & 11 deletions

‎docs/dev/CODEX_COMMANDS.md‎

Lines changed: 2 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,4 @@
11
MODEL: GPT-5.3-codex
2-
REASONING: low
2+
REASONING: high
33
COMMAND:
4-
Finalize APPLY_PR_LEVEL_12_5_SERVER_HOSTING_DOCKER_RUNTIME.
5-
Update docs/dev/roadmaps/MASTER_ROADMAP_HIGH_LEVEL.md markers only.
6-
Do not modify wording or structure.
4+
Prepare minimal remote deployment plan. Single node only. Update roadmap markers only.

‎docs/dev/COMMIT_COMMENT.txt‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1 +1 @@
1-
apply docker runtime for server hosting and validate — APPLY_PR_LEVEL_12_5_SERVER_HOSTING_DOCKER_RUNTIME
1+
define remote deployment candidate for authoritative server — PLAN_PR_LEVEL_12_6_REMOTE_DEPLOYMENT_CANDIDATE

‎docs/dev/reports/validation_checklist.txt‎

Lines changed: 3 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,3 @@
1-
- container builds
2-
- server runs
3-
- client connects
4-
- lifecycle verified
5-
- roadmap updated
1+
- remote host defined
2+
- connectivity defined
3+
- validation steps defined

‎docs/dev/roadmaps/MASTER_ROADMAP_HIGH_LEVEL.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -612,7 +612,7 @@
612612
- [x] replication/client application
613613
- [x] playable real multiplayer validation
614614
- [x] server hosting + Docker containerization
615-
- [ ] promotion/readiness gate
615+
- [.] promotion/readiness gate
616616
- [x] include samples for phase 13
617617

618618
### 3D Execution Dependency Gate

‎docs/pr/BUILD_PR_LEVEL_12_6_REMOTE_DEPLOYMENT_CANDIDATE.md‎

Lines changed: 51 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,51 @@
1+
# BUILD_PR_LEVEL_12_6_REMOTE_DEPLOYMENT_CANDIDATE
2+
3+
## Purpose
4+
Implement a minimal single-node remote deployment candidate for the authoritative multiplayer server runtime.
5+
6+
## Scope
7+
Primary target files:
8+
- `samples/phase-13/1316/server/REMOTE_DEPLOYMENT.md`
9+
- `samples/phase-13/1316/server/docker-compose.remote.yml`
10+
- `samples/phase-13/1316/server/README.md`
11+
- `docs/pr/LEVEL_12_6_REMOTE_DEPLOYMENT_CANDIDATE_CHECKLIST.md`
12+
- `docs/pr/APPLY_PR_LEVEL_12_6_REMOTE_DEPLOYMENT_CANDIDATE.md`
13+
14+
Allowed nearby reads:
15+
- `samples/phase-13/1316/server/Dockerfile`
16+
- `samples/phase-13/1316/server/docker-compose.yml`
17+
- `samples/phase-13/1316/server/networkSampleADashboardServer.mjs`
18+
- `docs/pr/PLAN_PR_LEVEL_12_6_REMOTE_DEPLOYMENT_CANDIDATE.md`
19+
20+
## Required implementation
21+
- Define one remote hosting target model for a single node.
22+
- Define one externally reachable endpoint contract (host/port/protocol).
23+
- Provide repeatable deployment/run steps for a remote VM/server host.
24+
- Provide a minimal validation sequence proving:
25+
- remote server is reachable
26+
- client can connect over internet path
27+
- authoritative session lifecycle is valid remotely
28+
- Keep all deployment guidance minimal and manual-friendly.
29+
30+
## Acceptance criteria
31+
- Single remote instance can be deployed and started repeatably.
32+
- External endpoint is reachable from outside host network.
33+
- Client connection/session is validated over remote endpoint.
34+
- Steps are documented and reproducible.
35+
36+
## Validation
37+
Run only:
38+
- `node --check samples/phase-13/1316/server/networkSampleADashboardServer.mjs`
39+
- `docker build -f samples/phase-13/1316/server/Dockerfile samples/phase-13/1316 -t authoritative-server-remote-candidate`
40+
- `docker compose -f samples/phase-13/1316/server/docker-compose.remote.yml up --build`
41+
- remote connectivity probe to published endpoint
42+
- client remote-connect session check using existing multiplayer validation path
43+
44+
## Non-goals
45+
- no scaling/orchestration
46+
- no infrastructure automation expansion
47+
- no gameplay expansion
48+
- no 3D work
49+
50+
## Working tree rule
51+
If the tree is already dirty, ignore unrelated files and modify only the scoped files for this PR purpose.

‎docs/pr/LEVEL_12_6_REMOTE_DEPLOYMENT_CANDIDATE_PREP.md‎

Lines changed: 42 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,42 @@
1+
# LEVEL_12_6_REMOTE_DEPLOYMENT_CANDIDATE_PREP
2+
3+
## Goal
4+
Prepare a minimal implementation-ready remote deployment plan for authoritative server hosting in single-node mode.
5+
6+
## Single-Node Remote Target
7+
8+
- One remote host (VM or bare server) only.
9+
- One containerized authoritative server process.
10+
- One public endpoint exposed for remote client connectivity.
11+
- No clustering, no failover, no multi-region routing.
12+
13+
## External Connectivity Contract
14+
15+
- Public hostname/IP configured by deploy operator.
16+
- One published service port (default `4310`).
17+
- Health endpoint externally reachable for readiness checks.
18+
- Session endpoint reachable from internet client network.
19+
20+
## Minimal Deployment Steps
21+
22+
1. Provision single remote node with Docker/Compose runtime.
23+
2. Deploy server container artifacts to host.
24+
3. Start single service using remote compose file.
25+
4. Validate health endpoint.
26+
5. Run remote client connection/session check.
27+
6. Stop service and confirm clean shutdown.
28+
29+
## Validation Checklist Targets
30+
31+
- remote node accepts inbound connection on configured port
32+
- health/readiness endpoint responds
33+
- client connects to remote server
34+
- session activation succeeds remotely
35+
- disconnect/shutdown leaves no active runtime residue
36+
37+
## Scope Guardrails
38+
39+
- single-node remote deployment only
40+
- no scaling/orchestration
41+
- no infrastructure automation expansion
42+
- no gameplay or 3D scope change

‎docs/pr/PLAN_PR_LEVEL_12_6_REMOTE_DEPLOYMENT_CANDIDATE.md‎

Lines changed: 26 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,26 @@
1+
# PLAN_PR_LEVEL_12_6_REMOTE_DEPLOYMENT_CANDIDATE
2+
3+
## Purpose
4+
Define minimal remote deployment candidate for authoritative server.
5+
6+
## Scope
7+
- Define remote hosting target (single node)
8+
- Define external connectivity (public endpoint)
9+
- Define deployment + validation steps
10+
11+
## In Scope
12+
- Single remote instance
13+
- Public connectivity test
14+
- Repeatable deployment steps
15+
16+
## Out of Scope
17+
- No scaling/orchestration
18+
- No infra automation expansion
19+
20+
## Acceptance Criteria
21+
- Server reachable remotely
22+
- Client connects over internet
23+
- Session validated remotely
24+
25+
## Roadmap Rule
26+
Markers only [ ] [.] [x]

0 commit comments

Comments
 (0)