Getting Started
Authoring
Access Control
Reference
Examples
@norbital-ai/pod
@norbital-ai/pod
@norbital-ai/pod is the filesystem compiler, authoring SDK, runtime, application shell,
and Vite integration for tenant workspaces. Core is the reference host, not a Pod dependency.
What Pod owns
- Filesystem compiler — role discovery, validation, generated modules, and local types
- Vite plugin — Svelte, Tailwind, server/client builds, migrations, and DDL
- Collection runtime — SQL compilation, policy evaluation, approvals, and remotes
- Application shell — generated app loaders and typed client access
- Facility ports — database, files, AI, notifications, and secrets
Author → Build → Run
- Author — one declaration per recognized
src/**filesystem role - Build —
vite buildruns the Pod plugin to synchronize, check, and emit.norbital/dist/ - Run — the host provisions the tenant database and serves the immutable bundle
One generated root
Pod writes diagnostics, build output, generated modules, role types, migration history, and one
generated TypeScript config under .norbital/. Only .norbital/migrations/ is committed.
What the host owns
A host supplies concrete facilities and operational isolation:
- Tenant database pools, object storage, model APIs, and credential storage
- Sandboxed builds and immutable artifact storage
- DDL validation, migration application, bundle serving, authentication, and billing
Workspace source declares requirements, never secret values. Client code cannot access private runtime facilities.
Core plugins
Workspace Studio (browser editing and Checkpoints releases) and Agent are Core-only plugins. Pod provides the build and runtime boundaries those plugins consume.
Workspace boundaries
- No SvelteKit dependencies, routes,
+pagefiles, orsvelte.config.* - No authored assembly registries or generated declarations
- No direct credentials, host internals, or custom bundling scripts
- No duplicate base CSS or Tailwind integration