A program can ask where it came from

SWI osWhereAmI hands back the path the program was loaded from, on the
same terms as osArgument, and Libraries/path.asm joins a name to the
place another thing is in. Between them an application can find its own
assets: ask where you are, then pathBeside that and the file's name.

The answer FOLLOWS THE PROGRAM AND NOT THE PERSON, which is the whole
point and the reason the working directory could not serve. A program's
assets are relative to the program and its arguments are relative to
whoever ran it, and cwd can only be one of them - setting it to the
program's own would mean "Play mytune.tune", typed by somebody in their
own directory, looked in Play's.

It is made absolute before the program starts, because the path the
search settled on may be a bare name: a program found where somebody was
standing is named by the word that was typed, and a bare name means the
working directory - which a program is entitled to move out of. Worked
out once, at the start, since where a program came from is a fact about
its start and cannot change afterwards.

Joining is a LIBRARY and not a service. A service that opened a file
relative to the program would need a twin for every file operation there
is - read, save, info, block, start, write, done, delete, rename - while
one service handing back a path composes with all of them.

---- And the root's own path was "//" ----

Found by the first caller that asks. shellPath prepends a separator in
front of whatever string it is given, so being handed the separator
itself wrote two of them. Nothing saw it while the only caller was the
prompt, which asks where it is only when that is not the root. It is
handed an empty string now, and cosmosWhere runs a program from the root.

Where.sbx exists to be run rather than read, and is on the test disk
twice: at the root, where it is found by the bare word typed, and in
/Apps, where it is found by a path that already says where it is.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01E2JrLzFvuFX9fgi1LDRjrW

Tests/makedisks.sh

@@ -105,6 +105,15 @@ for i in 1 2 3 4 5 6 7 8; do "$TOOL" put "$DISKS/sbfs.img" "filler$i.txt" >/dev/
 "$ROOT/Assembler" -I "$ROOT/Programs/CosmOS/Source" \
     "$ROOT/Programs/CosmOS/Apps/Say.asm" -o "$WORK/Say.sbx" >/dev/null
 "$TOOL" put "$DISKS/cosmos.img" "$WORK/Say.sbx" >/dev/null
+# Where.sbx says where it was loaded from, and where a name would be beside it. TWO COPIES
+# on purpose, which is the whole test: the one at the root is found where you are standing
+# and is named by the bare word that was typed, so the system has to work out what that word
+# meant; the one in /Apps is found by a path that already says where it is. Both have to come
+# out saying the same kind of thing, and the /Apps one has to go on saying it from a
+# directory that has no copy of its own.
+"$ROOT/Assembler" -I "$ROOT/Programs/Libraries" -I "$ROOT/Programs/CosmOS/Source" \
+    "$ROOT/Programs/CosmOS/Apps/Where.asm" -o "$WORK/Where.sbx" >/dev/null
+"$TOOL" put "$DISKS/cosmos.img" "$WORK/Where.sbx" >/dev/null
 # Break.sbx stops itself twice and shows what the registers were each time. It needs no disk
 # of its own: it only prints.
 "$ROOT/Assembler" -I "$ROOT/Programs/CosmOS/Source" \
@@ -227,6 +236,7 @@ python3 -c "open('twoblocks.txt','w').write('the second disk, at length. ' * 20)
     "$ROOT/Programs/CosmOS/Apps/Copy.asm" -o "$WORK/Copy.sbx" >/dev/null
 "$TOOL" put "$DISKS/cosmos.img" "$WORK/Copy.sbx" /Apps/Copy.sbx >/dev/null
 "$TOOL" put "$DISKS/cosmos.img" "$WORK/Say.sbx" /Apps/Say.sbx >/dev/null
+"$TOOL" put "$DISKS/cosmos.img" "$WORK/Where.sbx" /Apps/Where.sbx >/dev/null
 # A SCRIPT in the system's place, which is the one thing on this disk that is fetched from
 # drive 0 a block at a time WHILE it runs. Its own name carries the drive in front of it,
 # and resolving a name like that moves the machine to that drive - so a script started from