A business owner, operator, team lead, or analyst should be able to understand the structure of a file without learning software engineering.
The syntax must be deterministic enough for parsers, validators, linters, and transformations.
Statements should be explicit and semantically narrow so AI systems can interpret intent with minimal ambiguity.
Each keyword should have one clear semantic purpose in the language.
Avoid hidden defaults, invisible transitions, or inferred side effects.
OrgScript should work well in plain text, Markdown, Git diffs, code review, and chat-based workflows.
The language should model operational logic, not general software behavior.
OrgScript must resist drift toward loops, arbitrary functions, and unrestricted programming constructs.
Prefer a compact vocabulary and composable blocks over feature sprawl.
The reference syntax is English. Localization may be added later through controlled language packs, not by loosening the core semantics.