Glossary
One term per concept. The left column is the word this product uses; the
right column lists the words that mean the same thing and are not used, so
a reader searching for either one arrives at the same place. The table is
committed as data in docs/book/canonical-terms.json and a law
holds the book’s own prose to it.
| Term | Means | Not |
|---|---|---|
| deck | the .DATA text a model renders to, and the text an importer reads back. | data file, eclipse file, input file, sim file |
| guard | a named physics or model invariant that refuses a bad model and cites its code. | guardrail, safety net, sanity check |
| import | reading deck text back into semantic objects. | ingest, slurp, suck in |
| keyword | one named block of deck text, the unit the crosswalk is indexed by. | deck tag, directive name, eclipse tag |
| law | a committed test that pins a property the product may not lose. | safety check, tripwire |
| refuse | what the product does to an input it will not accept: raise, naming the rule, the value, and the remedy. | bail out, blow up, choke on, die on |
| render | turning a model into deck text. | dump, serialise out, spit out |
| seed | an authored minimal model you start from and edit. | boilerplate model, starter model, template model |
| spelling | the public call that writes a thing: the answer to “how do I say this in PetroScript?”. | incantation, magic string, the right words |
| worked case | a committed example module whose rendered deck is snapshotted. | demo, sample script, toy example |
PetroScript is licensed under the Apache License 2.0. © 2026 Blauweiss EDV LLC. PetroScript by Blauweiss AI.For AI agents: llms.txt