plans, ARTIFACT.md: task 3 ruling, capabilities declared, then checked
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_017RzZgrf7V7Zk2iczBXDRbm
This commit is contained in:
@@ -241,3 +241,9 @@ this is a measure of the analysis, not an interface.
|
||||
is named with hash 0 and resolved by name in the node's dictionary at placement. Exact-hash imports
|
||||
(`ABI.md` choice 4) hold between artifact trains only. Asked because a capsule today is one file, and
|
||||
the nucleus is 16 blobs.
|
||||
5. **Capabilities: "Declared, then checked"** (2026-11-19). v4 has no port opcode: a port is an address,
|
||||
reached through A, B or P, whose values are data, so which words touch ports cannot be derived. A word
|
||||
declares what it needs after its name, like its flags: `ports`, `request N`. The tool records the
|
||||
declaration. Where it can see a port or a request, it fails the build if the declaration is missing:
|
||||
a literal port address put into A or B, or a kernel request with a literal number. What it cannot see
|
||||
is the declaration's. This changes `ARTIFACT.md` choice 4's "the tool derives it from the code".
|
||||
|
||||
Reference in New Issue
Block a user