Why do we call the source files for POL (SRC) "scripts"?

Java is a virtual machine. The files written in Java source code are called "programs"

I'm old enough to remember when Pascal was implemented by the University California San Diego running in a virtual machine. The Pascal source files were called "programs". Later "Borland software" created Turbo Pascal which was able to compile Pascal source code to native x86 programs but originally the source was compiled to pseudo-code.

POL is a virtual machine and eScript compiles to pseudo-code that the Core executes just as Java and the early version of Pascal.

So I propose that we drop the "script" moniker and start using "program" to describe an eScript source file.

I disagree
"Scripts" is a more exact word to describe what we produce to feed to POL than "program"
And it easily and readily point you to what they are
A program is something already compiled

So then the source files for the POL Core would be considered scripts? A C++ source listing is a script? An assembly code file is a script? Any of those examples aren't "programs" until they are compiled or assembled?

I don't think programmers would agree with that assessment.

A BASIC source file that is run on a BASIC interpreter is called a programme even though it isn't compiled. Though I would say that is closer to a script because it doesn't need to be compiled to run, like the batch language or sh files.