On a conventional system these are three separate things: an init that starts the machine, a supervisor that keeps services alive, and a shell that gives you a prompt. Each one grew its own configuration language, and each one has to be taught about the other two. asc is all three, so there is nothing to teach and nothing to keep in sync.
Commands are words
There are no dash-flags anywhere in the system. Commands are plain English, in the order you would say them, because an option that reads as a word cannot be misremembered as a letter.
Privilege is a question, not a password
Anything privileged raises a prompt on screen that you approve or deny while it is happening. There is no password to type into a pipe, no cached credential and no setuid helper collection — the request crosses one socket and you answer it.
Not POSIX, on purpose
asc does not implement a POSIX shell and does not try to. Scripts written for one will not run, which is the point: the compatibility surface is the thing that forces every other decision. Nothing in the system image depends on a shell, so there is no bash, no busybox and no coreutils to keep.
- One program to start the machine, supervise it and drive it.
- No configuration language — services are declared, not scripted.
- No shell dependency anywhere in the boot path.