Module Creator
Platform limits, security, and review
Design inside a fail-closed host boundary and know which checks happen before code can run.
Fabled owns authority
- Packages describe contributions; Fabled owns production React renderers and authoritative adapters.
- Context is filtered to declared slot fields and granted capabilities. A service provider cannot lend extra authority to a consumer.
- Signed projections bind account/campaign scope, generation, releases, permissions, and compatibility to pinned public keys.
- Unknown keys, bad signatures, rollback/equivocation, stale generations, digest mismatches, revocation, or unavailable tiers fail closed.
- Disabling or replacing a generation disposes contributions; core product recovery remains available.
Package safety
The CLI uses exact schemas and catalogs, bounded JSON traversal, canonical locale rules, safe relative paths, declared hashes and byte lengths, deterministic archives, and strict ZIP parsing. Validation and inspection never execute worker, WebAssembly, automation, frame, or effect content.
External origins must be explicit HTTPS origins without paths, query strings, or credentials. The network.fetch.declared capability is currently unavailable, so declaring an origin does not create network access.
Review is required
Uploads enter quarantine. Automated contract findings are evidence for the reviewer, not a substitute for review. Review considers requested authority, privacy, dependency and service relationships, renderer/action availability, migration safety, support information, and whether the artifact matches the claimed behavior.
Beta and production gates
- The npm package must have a published immutable module-cli-v<version> release before npx can install it.
- Module CLI pairing is backend-gated and defaults off during safe rollout.
- Ingest, catalog administration, installation, resolution, activation, projection, artifact fetch, and command execution are independently deployable backend capabilities.
- The browser runtime additionally requires NEXT_PUBLIC_MODULE_RUNTIME_ENABLED plus a supported protocol version and valid pinned projection keys.
- The source candidate admits reviewed community campaign modules with active ADMIN_GRANT or FREE_ACQUISITION authority; owner, installation, review, signature, compatibility, and policy checks still apply.
- Module Lab is development-only and is evidence, not a production installation path.