From c9cc39f4ecf223ee22cb88cd3551bfc9c2468772 Mon Sep 17 00:00:00 2001 From: Claude Date: Thu, 19 Nov 2026 16:17:11 +0000 Subject: [PATCH] ARTIFACT.md: choice 3 ruled, both stack effects recorded and checked Co-Authored-By: Claude Opus 5.5 Claude-Session: https://claude.ai/code/session_017RzZgrf7V7Zk2iczBXDRbm --- docs/v4.0.0/ARTIFACT.md | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/docs/v4.0.0/ARTIFACT.md b/docs/v4.0.0/ARTIFACT.md index 02527c2a..dd35a874 100644 --- a/docs/v4.0.0/ARTIFACT.md +++ b/docs/v4.0.0/ARTIFACT.md @@ -130,7 +130,10 @@ about the format: units each (§4, §6). An import's capsule hash stays the capsule's ID, XXHash64, 2 units (§5), and signing stays Ed25519. The provenance record grows from 12 units to 64, with no reserved units, and verification from 4 to 18. -3. **The return-stack effect:** recorded and checked (§5, unit 4), or the data stack only? +3. ~~The return-stack effect~~ **Ruled 2026-11-19: "Record and check both".** The tool derives the + return-stack effect as it derives the data-stack effect, and records it in unit 4 of each export and + import (§5). Placement, compatibility (`ABI.md` §7, "the same stack effect") and the proofs check + both. 4. **Capabilities:** the port bit plus a list of kernel request numbers (§5, unit 5), or something else? 5. **Endianness for the code cells:** as the golden model stores them (host order), or fixed low-first like the records?