Script Library
A script isn't a loose file on a server. It's a first-class record with a stable key, a version, and permissions — organized, controlled, and optionally kept in Git, like the rest of your code.
A first-class record
Each script carries a stable key you reference it by, a type that decides how it runs, a source, a version, and flags for whether it's enabled and whether it's public. Its input and output can even be described up front.
Versioning
Change a script's source and its version bumps. That version is what the compile cache keys on, so an edit quietly invalidates the old compiled copy and the next run picks up the new one — no stale bytecode lingering around.
Sourced from Git
A script can live in a repo. Attach it to a file in a script project, and a push updates its source automatically — the repo becomes the source of truth, and the next push overwrites whatever's in the platform.
scripts/welcome.bosca.ktsPermissions
Scripts use the same group-based permissions as everything else on the platform, so access to a powerful script is as controlled as access to the data it touches.
See the script and its source.
Change the source and settings.
Run it, or call its endpoint.
Grant access and control the script.
Keep exploring