Configuration as code

Everything an administrator configures in Sloose can also live in a repository and be pushed with the SDK. Discovery still runs on the server; the bundle is the curation layered on top.

product-config/
  org.json              date format, expression context, AI data policy
  modules.json          which discovered modules are enabled, in what order, with match defaults
  fields/<module>.json  descriptions, formats, aliases, PII flags, default mappings
  libraries/<name>/     manifest.json and src/index.ts
  templates/            optional seeded templates

npx @sloose/sdk validate ./product-config
npx @sloose/sdk push ./product-config --org <org id> --env production

push and diff authenticate with an org API token. An administrator creates one in the widget under Settings → API tokens (or with POST /orgs/:org/tokens), copies the secret once, and stores it as SLOOSE_TOKEN in the CI environment or passes --token. The token is scoped to that one org with the admin role; revoke it from the same screen and every pipeline using it stops.

Validation checks the bundle against the published schemas and against the org’s last discovery, so a field that no longer exists in the CRM fails at push time, not at run time.