docs(runicnpc): stage 9c built, the staging drill (D317, D318, D319) #326

wtclaude · 2026-10-07T06:33:42Z

wtclaude commented

2026-10-07 06:33:42 +00:00

What & why

Phase 9c of runicnpc/PLAN.md stage 9, the staging drill, as built and run on 2026-10-06/07. It adds three decisions from this phase:

	Decision
D317	While Oxide's staging build is behind Rust's, the drill waits up to three days without opening an issue, then reports "Oxide has not caught up". "Behind" is measured: `tools/fieldlist --oxide-behind` counts the members Rust declares that Oxide's patched assembly lacks. Public/public is 0; staging/staging was 482 (later 488), and that pair dies at boot.
D318	The drill works only in the seven days before each monthly forced wipe (the first Thursday), not nightly. This narrows D308. In the org lead's words: "once a month about a week ahead to give lead time to fix it if it breaks but don't need it nightly".
D319	The staging rig is a 3500 map (seed 1234) at 8 GB. Stage 5's five fights need a 280 m line of navmesh 300 m from every monument, and the smaller maps have none. Spots with the line at 300 / 250 / 200 m: 2000/1234 0/53/70; 3000/1234 0/0/8; 3000/981448696 0/0/6; 3500/1234 5/14/26. This amends D307.

runicnpc/PLAN.md:
- the D317–D319 rows;
- D307 and D308 point to them;
- a "9c built" section: the proofs, the rig, the key, Oxide's lag, the manifest as a build's name, the job, and what was checked.
runicnpc/INSTALL.md: the drill runs in the week before each forced wipe.

Companion PR

runicnpc-rust#15 (into edge): the workflow, tools/drill/, --oxide-behind, and harness 0.7.2.

How it was tested

Docs only. Every number comes from a run named in the section:

the local static runs;
five public rehearsals;
CI run 16 on the runner;
the field probe on built navmesh, measured again after stray loops spoiled one round (noted in the section).

Checklist

I have read CONTRIBUTING.md.
The change builds and existing tests/checks pass locally.
I have added or updated tests/docs where it makes sense.
My commits are reasonably scoped with clear messages.

AI-assisted contributions (required)

No AI tools were used to produce this contribution.
AI tools were used. Tool(s): Claude Code (Claude Opus 5.5). I have reviewed and understand
every change, and take responsibility for it. AI-authored commits are
marked with a Co-Authored-By / Assisted-By trailer.

License

I agree that my contribution is licensed under this project's license
(GNU GPL v3.0 or later), and I have the right to contribute it.

🤖 Generated with Claude Code

https://claude.ai/code/session_01E14m6SuuY6i1vASFeGDBeY

## What & why Phase 9c of `runicnpc/PLAN.md` stage 9, the staging drill, as built and run on 2026-10-06/07. It adds three decisions from this phase: | | Decision | |---|---| | D317 | While Oxide's staging build is behind Rust's, the drill waits up to three days without opening an issue, then reports "Oxide has not caught up". "Behind" is measured: `tools/fieldlist --oxide-behind` counts the members Rust declares that Oxide's patched assembly lacks. Public/public is 0; staging/staging was 482 (later 488), and that pair dies at boot. | | D318 | The drill works only in the seven days before each monthly forced wipe (the first Thursday), not nightly. This narrows D308. In the org lead's words: "once a month about a week ahead to give lead time to fix it if it breaks but don't need it nightly". | | D319 | The staging rig is a 3500 map (seed 1234) at 8 GB. Stage 5's five fights need a 280 m line of navmesh 300 m from every monument, and the smaller maps have none. Spots with the line at 300 / 250 / 200 m: 2000/1234 0/53/70; 3000/1234 0/0/8; 3000/981448696 0/0/6; 3500/1234 5/14/26. This amends D307. | - **`runicnpc/PLAN.md`:** - the D317–D319 rows; - D307 and D308 point to them; - a "9c built" section: the proofs, the rig, the key, Oxide's lag, the manifest as a build's name, the job, and what was checked. - **`runicnpc/INSTALL.md`:** the drill runs in the week before each forced wipe. ## Companion PR runicnpc-rust#15 (into `edge`): the workflow, `tools/drill/`, `--oxide-behind`, and harness 0.7.2. ## How it was tested Docs only. Every number comes from a run named in the section: - the local static runs; - five public rehearsals; - CI run 16 on the runner; - the field probe on built navmesh, measured again after stray loops spoiled one round (noted in the section). ## Checklist - [x] I have read [CONTRIBUTING.md](CONTRIBUTING.md). - [x] The change builds and existing tests/checks pass locally. - [x] I have added or updated tests/docs where it makes sense. - [x] My commits are reasonably scoped with clear messages. ## AI-assisted contributions (required) - [ ] No AI tools were used to produce this contribution. - [x] AI tools were used. Tool(s): `Claude Code (Claude Opus 5.5)`. I have reviewed and understand every change, and take responsibility for it. AI-authored commits are marked with a `Co-Authored-By` / `Assisted-By` trailer. ## License - [x] I agree that my contribution is licensed under this project's license (**GNU GPL v3.0 or later**), and I have the right to contribute it. 🤖 Generated with [Claude Code](https://claude.com/claude-code) https://claude.ai/code/session_01E14m6SuuY6i1vASFeGDBeY

wtclaude added 1 commit 2026-10-07 06:33:44 +00:00

docs(runicnpc): stage 9c built, the staging drill (D317, D318, D319) f865226755

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01E14m6SuuY6i1vASFeGDBeY

whitlocktech merged commit 93e60b71d3 into main

2026-10-07 06:43:52 +00:00

whitlocktech deleted branch docs/runicnpc-stage9c

2026-10-07 06:43:53 +00:00

whitlocktech referenced this issue from a commit

2026-10-07 06:43:54 +00:00

Merge pull request 'docs(runicnpc): stage 9c built, the staging drill (D317, D318, D319)' (#326) from docs/runicnpc-stage9c into main

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: RunicGateway/docs#326