v4: init.4th and the ACL at call; the F18 ADR, ABI and artifact layout; ADR step 3 tasks 1-3 (mkf18a) #198

Open
rajames wants to merge 52 commits from StarForth-v4.0.0 into master
Showing only changes of commit 913b74a631 - Show all commits
+4 -3
View File
@@ -143,9 +143,10 @@ stock." Ruled "One train per capsule" (§1).
- **There is no declaration in the source.** The host tool computes each exported word's stack effect
from its compiled code, by static analysis of the F18 opcodes, and records it in the artifact. The
proofs check it. Comments stay comments.
- **Open within it (2c):** a word whose effect depends on its data (a loop, a branch that leaves
different depths, `EXECUTE`) has no fixed count. What the tool records for such a word is a question
of its own, asked again now that each capsule is a train.
- **2c, ruled 2026-11-19: "Refused as an export".** A word whose effect depends on its data (a loop
leaving a count of values, branches that leave different depths, `EXECUTE`, a `DEFER`red word) has no
fixed count. It cannot be exported by an engine: it stays internal to its train, or is restructured.
Every export has a fixed effect, which the tool derives and the build fails without.
3. **What a capsule carries:** an artifact alone, or the artifact and its source (provenance, ADR §3.1)?
4. **Imports by capsule hash:** a hash pins one exact build. Is an import of an older build of the same
capsule a mismatch, or is the name of the capsule enough with the stack effect checked?