Files
prometeu-runtime/docs/vm-arch/STORAGE_QUALIFICATION.md
bquarkz dcf6561ea7
Intrepid/Prometeu/Runtime/pipeline/head This commit looks good
refactor(vm)!: remove publication and logical guard opcodes
Remove INDEX_GUARD, ARRAY_CHECK_LENGTH, STORAGE_PUBLISH and FIELDS_PUBLISH
from decoding, metadata, tooling, verification and execution. Keep ARRAY_LEN
and overlap-safe ARRAY_COPY with complete-group ownership and early charging
of calculable copy work, including refused attempts.

Update specifications, producer handoff, qualification evidence and lessons.
Share collection test support and remove redundant Copy clones for Clippy.

Validation: make ci-domains passed with 1,095 workspace tests, five separately
executed debugger socket tests and all 15 unchanged coverage domain gates.
VM release, resource diagnostics and layer/quality suites also passed.

BREAKING CHANGE: PBX using opcodes 0xA7, 0xA8, 0xAA or 0xAB is rejected,
including unreachable instructions. Consumers must adapt their emission and
collection algorithms or operational guarantees.
2026-10-23 23:37:56 +01:00

64 lines
3.3 KiB
Markdown

# Storage ISA qualification
This record qualifies the working-tree delivery over baseline `69ad1931de1e12e59c2268f94aa906aed114fb6d` on
macOS-27.0.1-arm64-arm-64bit-Mach-O with `rustc 1.98.1 (48a229cea 2026-09-01)`. The baseline commit alone does
not contain the changes. No new provider revision is claimed. Source/test/spec
SHA-256 fingerprints and exact test commands are stored in
[the qualification manifest](storage-qualification.json).
## Delivered behavior
Encodings 0xA7/0xA8/0xAA/0xAB are unsupported at real instruction boundaries,
including dead code. ARRAY_LEN stays 0xA4 and ARRAY_COPY stays 0xA9. The
[copy contract](../specs/runtime/02-vm-instruction-set.md#typed-array-range-copy)
defines strict ranges, complete groups/owners, snapshot overlap and precharged
4+2*N*W work for calculable counts, including receiver/range/scratch refusal.
No replacement publication, guard or transaction was introduced.
## Verification
`make ci-domains` passed: formatting, workspace Clippy with warnings denied,
workspace tests/all features, all five debugger socket tests, LLVM coverage,
coverage ownership audit and all 15 unchanged domain gates.
| Run | Passed | Ignored |
| --- | ---: | ---: |
| Workspace/all targets/all features | 1095 | 13 |
| Debugger sockets (explicit ignored selection) | 5 | 0 |
| LLVM coverage/workspace/all features | 1095 | 13 |
| VM release | 400 | 2 |
| VM diagnostics checkpoint | 407 | 2 |
| Layer and quality suites | 19 | 0 |
The diagnostics checkpoint preceded test-only fixture import/Copy cleanup; the
final all-features workspace and coverage runs include diagnostics on final code.
No identity/hash semantic change was made. Default ignored measurement probes,
audio probes and packaged-installation smoke remain explicit exclusions. The
five debugger socket tests were executed separately and passed; sandbox-local
binding had first been denied, so the complete successful gate ran with approval
outside the sandbox. Coverage gates were not lowered or skipped.
Independent bytecode and serialized PBX tests prove decoder/admission rejection
without treating immediate/data bytes as instructions. VM tests cover cost/fault
precedence, frame temporary floors, empty and overlapping ranges, native and
multislot groups, aliases, scratch quota and allocation refusal, late source-group
failure, operand/destination preservation, native owners and roots through GC,
zero budget, overshoot and successful-step accounting.
Overflow defense uses synthetic widths to exercise checked multiplication and
addition. It does not imply such widths are accepted Registry layouts. Internal
corruption tests are labeled separately from admitted-program evidence. There
are no JavaScript/Lua engines or frontend fixtures in this qualification.
Local full logs and the domain audit are under `target/qualification/storage/`;
the manifest records their digests. Generated logs/LLVM output are reproducible
local evidence, not a runtime or SDK API.
## Consumer boundary
The [producer handoff](collection-producer-handoff.md) describes required compiler
emission and SDK algorithm/contract changes. Existing consumer evidence still
qualifies its original provider only. Compiler/SDK migration, provider pin/catalog
import, installed resources and normal/optimized source conformance require
consumer-owned delivery and are not claimed here.