feat(registry): checkpoint PLN-0176 foundations and validated partial integrations

This commit is contained in:
2026-10-07 17:49:46 +01:00
parent 01fab56cc6
commit 126a9e50e7
63 changed files with 8499 additions and 1462 deletions
+7 -6
View File
@@ -8,7 +8,7 @@ The organization here is intentionally flat. The taxonomy is conceptual, not str
## Scope Boundary
Belongs in `docs/runtime/specs/`:
Belongs in `docs/specs/runtime/`:
- the technical contract of the PROMETEU machine;
- virtual hardware and its peripherals;
@@ -16,7 +16,7 @@ Belongs in `docs/runtime/specs/`:
- cartridge, asset, and load surfaces;
- the VM-to-host ABI.
Does not belong in `docs/runtime/specs/` as the primary canonical source:
Does not belong in `docs/specs/runtime/` as the primary canonical source:
- internal architectural invariants of the VM/runtime:
[`../virtual-machine/ARCHITECTURE.md`](../../vm-arch/ARCHITECTURE.md);
@@ -25,7 +25,7 @@ Does not belong in `docs/runtime/specs/` as the primary canonical source:
- pedagogical guides and learning material:
[`../learn/README.md`](../runtime/learn/README.md);
- agendas, proposals, and plans:
`docs/runtime/agendas/` and `docs/runtime/pull-requests/`.
`discussion/workflow/agendas/`, `discussion/workflow/decisions/` and `discussion/workflow/plans/`.
## Organization Rules
@@ -70,7 +70,7 @@ worker-owned RGBA8888 frame production and host-owned native upload/present.
- `historical`: archived material; not the authority for new implementation work.
- `pedagogical`: teaching material; does not define the technical contract on its own.
In the current state, no chapter under the active `docs/runtime/specs/` root is purely `historical`. If historical material appears, it must not compete with the primary normative surface.
In the current state, no chapter under the active `docs/specs/runtime/` root is purely `historical`. If historical material appears, it must not compete with the primary normative surface.
## Current Chapter Map
@@ -80,6 +80,7 @@ In the current state, no chapter under the active `docs/runtime/specs/` root is
| [`02-vm-instruction-set.md`](02-vm-instruction-set.md) | VM subsystem overview | normative |
| [`02a-vm-values-and-calling-convention.md`](02a-vm-values-and-calling-convention.md) | VM values and calling convention | normative |
| [`02b-vm-function-values-and-closures.md`](02b-vm-function-values-and-closures.md) | VM closures and function values | normative |
| [`02c-program-registry-and-pbx-v1.md`](02c-program-registry-and-pbx-v1.md) | Registry, typed storage, PBX v1 and quotas | normative |
| [`03-memory-stack-heap-and-allocation.md`](03-memory-stack-heap-and-allocation.md) | VM memory model | normative |
| [`04-gfx-peripheral.md`](04-gfx-peripheral.md) | virtual hardware: graphics | normative |
| [`05-audio-peripheral.md`](05-audio-peripheral.md) | virtual hardware: audio | normative |
@@ -100,7 +101,7 @@ 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.
- `docs/specs/runtime/` 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.
- When a chapter here touches the VM, it may complement but must not contradict the canonical VM/runtime architecture.
@@ -124,7 +125,7 @@ A topic should be created as a `spec` + `learn` pair when:
In those cases:
- `docs/runtime/specs/` defines the contract;
- `docs/specs/runtime/` defines the contract;
- `docs/runtime/learn/` explains the why, the intuition, and the examples;
- the spec should point to the pedagogical companion near the top;
- the pedagogical guide should point back to the canonical spec.