docs(discussion): close atomic Registry delivery for PLN-0176 step 36
This commit is contained in:
@@ -188,4 +188,4 @@ The verifier statically checks bytecode for structural safety and stack‑shape
|
||||
|
||||
The [Program Registry contract](../specs/runtime/02c-program-registry-and-pbx-v1.md) defines immutable image-owned Type/Function metadata linked by dense IDs. Descriptors are native metadata outside guest GC; nominal identity does not depend on names. Stack/local execution retains Value, while typed storage uses resolved aligned layouts. PBX v1 is the sole target format; publication requires full bounded validation. Callable/closure/coroutine typed integration awaits its separate contract and must preserve existing behavior until then.
|
||||
|
||||
`ValidatedProgramImage::load` publishes a shared image only after bounded decoding, native binding and Registry verification; `VirtualMachine::from_image` creates sessions that consume its typed signatures, constants and conversion instructions. Production `initialize` and the existing example generators still await coordinated migration with the callable contract. The [producer handoff](registry-producer-handoff.md) documents schema, input IDs and named-argument order, while [layout evidence](registry-layout-evidence.md) records reproducible load/access/GC measurements and the current publication boundary.
|
||||
`ValidatedProgramImage::load` publishes a shared image only after bounded decoding, native binding and Registry verification; `VirtualMachine::from_image` creates sessions that consume its typed signatures, constants and conversion instructions. The independent Registry delivery is closed. Production `initialize` and the existing example generators remain pending integration in AGD-0055's future plan, after its callable contract is accepted. The [producer handoff](registry-producer-handoff.md) documents schema, input IDs and named-argument order, while [layout evidence](registry-layout-evidence.md) records reproducible load/access/GC measurements and the current publication boundary.
|
||||
|
||||
@@ -92,6 +92,12 @@ The native fixture stores one session-imported 13-byte String in both a String f
|
||||
|
||||
## Publication boundary
|
||||
|
||||
The sealed v1 image, bounded verifier, typed direct calls, Dynamic/reference execution, metered native strings and structured host diagnostics have executable evidence. Production `VirtualMachine::initialize` still uses the old loader, and existing generators still emit version 0. Their coordinated migration must preserve existing closures and awaits AGD-0055's callable contract; the producer handoff records that dependency. The whole plan and final publication audit remain in progress.
|
||||
The sealed v1 image, bounded verifier, typed direct calls, Dynamic/reference execution, metered native strings and structured host diagnostics have executable evidence. Production `VirtualMachine::initialize` still uses the old loader, and existing generators still emit version 0. Their coordinated migration must preserve existing closures and awaits AGD-0055's callable contract; the producer handoff records that dependency.
|
||||
|
||||
These measurements cover bounded layout/load/access/ownership/GC behavior. Representative-game capacity and headroom belong to AGD-0060; coordinated long-run stress belongs to AGD-0059. No external compiler implementation, cross-host stress acceptance, regenerated production PBX smoke or complete workflow closure is claimed by this report.
|
||||
The independent Registry delivery was closed by the user's scope correction on
|
||||
2026-10-08. Production activation and its final audit are received as future-plan
|
||||
suggestions in AGD-0055, with targets and acceptance in the permanent handoff.
|
||||
They remain pending; the callable proposal is unaccepted. This delivery no longer
|
||||
waits for another agenda's closure.
|
||||
|
||||
These measurements cover bounded layout/load/access/ownership/GC behavior. Representative-game capacity and headroom belong to AGD-0060; coordinated long-run stress belongs to AGD-0059. No external compiler implementation, cross-host stress acceptance, regenerated production PBX smoke or final production activation is claimed by this report.
|
||||
|
||||
@@ -14,6 +14,30 @@ migration and both regenerated runtime examples remain pending. Existing closure
|
||||
receivers need the separate AGD-0055 contract; none of the four accepted Registry
|
||||
categories may be used as a provisional closure type.
|
||||
|
||||
On 2026-10-08 the user closed the independent AGD-0061 / PLN-0176 delivery and
|
||||
required each plan to be atomic to its originating agenda. Coordinated activation
|
||||
and its producer/example audits were handed to AGD-0055 as suggestions for its
|
||||
future plan. The Registry delivery ends without requiring that agenda to close
|
||||
first. The final v1-only target remains normative; integration below is unexecuted.
|
||||
This scope correction does not accept a callable proposal.
|
||||
|
||||
| Original Registry steps | Pending integration owned by AGD-0055 |
|
||||
| --- | --- |
|
||||
| 09 / 14 | Switch production initialize to the sealed strict v1 factory; retire old decoder and unchecked entry points while preserving approved callable behavior. |
|
||||
| 19 | Complete image/constant provenance on migrated production entry points using the delivered ledgers and native retention domains. |
|
||||
| 24 / 25 | Route production loads through bounded Registry verification; remove the old verifier while adding the callable contract's checks. |
|
||||
| 28 | Audit structured load/runtime/native diagnostics through the final active loader and hosts. |
|
||||
| 29 / 30 | Migrate producers/fixtures, regenerate dummy-boy and stress-console PBX files, and execute both through the active runtime. These generators are ordinary programs sharing the production consumer being migrated. |
|
||||
| 31 / 32 | Add migrated producer/example/callable evidence to this handoff and the existing conformance matrix. |
|
||||
| 35 | Audit final coordinated publication, legacy removal, traceability and migrated workspace/examples. |
|
||||
|
||||
AGD-0055 records concrete targets and acceptance for this handoff. Its future plan
|
||||
follows its own accepted decision and reuses the Registry foundation. Guest
|
||||
collection operations stay with AGD-0054, new strings/bytes/save with AGD-0057,
|
||||
coordinated stress with AGD-0059 and representative-game headroom with AGD-0060.
|
||||
The [delivery lesson](../../discussion/lessons/DSC-0058-program-registry-type-and-function-metadata/LSN-0059-registry-boundaries-and-owned-values.md)
|
||||
explains published mechanisms and the scope correction.
|
||||
|
||||
The external Studio handoff targets are the build-pipeline
|
||||
`backend/bytecode/BytecodeModule.java` and `backend/irvm/IRVMIntrinsicRegistry.java`,
|
||||
compiler-core `source/tables/IntrinsicTableReader.java`, PBS
|
||||
|
||||
Reference in New Issue
Block a user