plans: task 3 ruling, flags after the : name

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_017RzZgrf7V7Zk2iczBXDRbm
This commit is contained in:
Claude
2026-11-19 19:41:42 +00:00
parent a1b26eacaf
commit 9b114fff83
@@ -229,3 +229,7 @@ this is a measure of the analysis, not an interface.
1. **Exports: "`: NAME` words, no headers"** (2026-11-19). Every `:` word with a fixed effect is exported,
named by its `:` name. A train's source lays no dictionary entry: placement makes the entries (`ABI.md`
§5, step 4, as written). Asked because a `header` in the code would make each entry twice.
2. **Flags: "After the name, like header"** (2026-11-19). The flags follow the `:` name, as they follow
`header` today: `: PLUS inline + ;`, `: [ immediate ...`. The ACL defaults come the same way, as
`pinned` and `mode N`. `text.c` records them and lays nothing in the code. In-line also decides how the
tool derives the word's effect (§9).