Developing
This subtree is about how the current workspace is organized and where each class of problem should go first. It does not define gameplay rules. It defines responsibility lines.
Scope
| Question | Read first |
|---|---|
| Which directories in the current instance mean what | Architecture |
| Why the project is still one workspace | Repositories |
| Stage order and delivery gates | Workflow |
| How docs, pack, and runtime split apart | Architecture, then the owning subtree |
Current Responsibility Lines
There is only one integration workspace right now, but the responsibility split is already fixed into three lines:
| Line | Main content |
|---|---|
| docs line | design rules, implementation contracts, workflow, and change records |
| pack line | mod assembly, config, KubeJS, datapacks, and resource overrides |
| runtime line | Forge-side ledger, live runtime, sync, resonance, and recovery |
Directories can coexist for now. Responsibility lines cannot.
Decision Order
When a problem comes up, evaluate it in this order:
- Which directory it actually lives in now.
- Which responsibility line should own it long-term.
- Which subtree should document it.
- Whether the change also affects an entry page or the changelog.
If step two or step three is unclear, do not write the page yet.