discussion framework migration

README.md

@@ -32,7 +32,7 @@ PROMETEU is the machine. The VM/runtime is one subsystem inside that machine.
 Authoritative documents:
 
 - [`docs/runtime/virtual-machine/ARCHITECTURE.md`](docs/vm-arch/ARCHITECTURE.md) is normative for VM/runtime invariants.
-- [`docs/runtime/specs/README.md`](docs/specs/README.md) describes the broader PROMETEU machine, hardware model, and fantasy console context.
+- [`docs/runtime/specs/README.md`](docs/specs/runtime/README.md) describes the broader PROMETEU machine, hardware model, and fantasy console context.
 - Supporting material under `docs/` may expand, explain, or propose changes, but it must not silently collapse the whole machine into the VM layer.
 
 ---

docs/specs/runtime/02-vm-instruction-set.md

@@ -12,7 +12,7 @@ It is intentionally narrower than the broader machine specs:
 - verifier boundary;
 - relationship between the VM and adjacent specs.
 
-For the bytecode-level instruction contract, see [`../virtual-machine/ISA_CORE.md`](../vm-arch/ISA_CORE.md).
+For the bytecode-level instruction contract, see [`../virtual-machine/ISA_CORE.md`](../../vm-arch/ISA_CORE.md).
 
 ## 1 Scope
 
@@ -67,7 +67,7 @@ Each frame:
 
 ## 4 Instruction Families
 
-The public VM instruction surface is documented at the bytecode level in [`../virtual-machine/ISA_CORE.md`](../vm-arch/ISA_CORE.md). At the machine/spec level, the instruction families are:
+The public VM instruction surface is documented at the bytecode level in [`../virtual-machine/ISA_CORE.md`](../../vm-arch/ISA_CORE.md). At the machine/spec level, the instruction families are:
 
 - execution control:
   - `NOP`, `HALT`, `JMP`, `JMP_IF_FALSE`, `JMP_IF_TRUE`, `TRAP`, `FRAME_SYNC`

docs/specs/runtime/README.md

@@ -19,9 +19,9 @@ Belongs in `docs/runtime/specs/`:
 Does not belong in `docs/runtime/specs/` as the primary canonical source:
 
 - internal architectural invariants of the VM/runtime:
-  [`../virtual-machine/ARCHITECTURE.md`](../vm-arch/ARCHITECTURE.md);
+  [`../virtual-machine/ARCHITECTURE.md`](../../vm-arch/ARCHITECTURE.md);
 - bytecode-level ISA:
-  [`../virtual-machine/ISA_CORE.md`](../vm-arch/ISA_CORE.md);
+  [`../virtual-machine/ISA_CORE.md`](../../vm-arch/ISA_CORE.md);
 - pedagogical guides and learning material:
   [`../learn/README.md`](../runtime/learn/README.md);
 - agendas, proposals, and plans:
@@ -87,8 +87,8 @@ In the current state, no chapter under the active `docs/runtime/specs/` root is
 ## Authority Model
 
 - `docs/runtime/specs/` defines the PROMETEU machine and its external execution surfaces.
-- [`../virtual-machine/ARCHITECTURE.md`](../vm-arch/ARCHITECTURE.md) remains the canonical authority for internal VM/runtime invariants.
-- [`../virtual-machine/ISA_CORE.md`](../vm-arch/ISA_CORE.md) remains the authority for the bytecode ISA.
+- [`../virtual-machine/ARCHITECTURE.md`](../../vm-arch/ARCHITECTURE.md) remains the canonical authority for internal VM/runtime invariants.
+- [`../virtual-machine/ISA_CORE.md`](../../vm-arch/ISA_CORE.md) remains the authority for the bytecode ISA.
 - When a chapter here touches the VM, it may complement but must not contradict the canonical VM/runtime architecture.
 
 ## Rules for Future Chapters

docs/vm-arch/ARCHITECTURE.md

@@ -9,7 +9,7 @@ Scope boundary:
 - PROMETEU itself is a fantasy handheld / fantasy console with a broader machine model, firmware model, cartridge model, and virtual hardware surface.
 - This document does not define the whole PROMETEU machine.
 - This document defines the VM/runtime subsystem that executes bytecode inside that machine.
-- For broader machine-level framing, see [`../specs/README.md`](../specs/README.md).
+- For broader machine-level framing, see [`../specs/README.md`](../specs/runtime/README.md).
 
 Document roles: