Package support policy#
Pulse 1.0.0-beta.6 publishes one synchronized 19-package release set. Publication does not make every package an application-author SDK: the support tier and listed entry points define the release promise.
| Package on npm | Guide | Support tier | Install directly | Release promise |
|---|---|---|---|---|
@pulse-compute/runtime | Guide | Canonical application surface | Yes | Supported application authoring and execution contract. |
@pulse-compute/pulse | Guide | Canonical application surface | Yes | Supported conventional application, project-configuration, and schema-authoring contract. |
@pulse-compute/cli | Guide | Canonical application surface | Yes | Supported Beta workflow and project-configuration contract. |
@pulse-compute/provider-fastly | Guide | Supported provider/extension surface | Yes | The listed entry points are supported for the Beta; all other exported subpaths are implementation-only. |
@pulse-compute/grip | Guide | Supported provider/extension surface | Yes | The package root has bounded JavaScript and Native HTTP-framing realization plus configured Node/Fastly broadcast; /pulsewasm remains compatibility-only. |
@pulse-compute/assets | Guide | Supported provider/extension surface | Yes | The package root is the supported JavaScript API and canonical Native authoring surface, including bounded embedded Assets bytes on their qualified targets. /pulsewasm remains a compatibility subpath; manifest/compiler subpaths are toolchain integration. No application binary inspection is exposed. |
@pulse-compute/crypto | Guide | Supported provider/extension surface | Yes | The package root supports bounded verification and request-owned exact-text digests; provider, manifest/compiler and Native integration subpaths remain toolchain-only. |
@pulse-compute/jwt | Guide | Supported provider/extension surface | Yes | The package root supports provider-neutral verification and bounded HS256/ES256/RS256 signing; provider and compiler integration subpaths are not application APIs. |
@pulse-compute/entities | Guide | Supported provider/extension surface | Yes | The package root and first-party JSON-RPC adapter are supported Beta contracts; compiler integration subpaths remain toolchain-only. |
@pulse-compute/s3 | Guide | Supported provider/extension surface | Yes | The package root supports head, getText, getBody and putText on Node Native, Node JavaScript and Fastly Native. getBody returns bounded opaque binary responses with the documented HTTP subset. Fastly JavaScript is ineligible. Provider and lowering subpaths are toolchain-only; live origin acceptance is separate. |
@pulse-compute/wasm-build-support | Guide | Implementation/transitive surface | No | Internal release-set interface; exported modules may change with compiler implementation needs. |
@pulse-compute/wasm-compiler | Guide | Implementation/transitive surface | No | Internal compiler interface; no application-author compatibility guarantee. |
@pulse-compute/wasm-guest-link | Guide | Implementation/transitive surface | No | Internal first-party prebuilt guest-link interface synchronized with the compiler; no application-author or third-party guest compatibility guarantee. |
@pulse-compute/wasm-contracts | Guide | Implementation/transitive surface | No | The provider toolchain contract is versioned and supported for the Beta; other protocol and proof interfaces remain internal. |
@pulse-compute/wasm-host-runtime | Guide | Implementation/transitive surface | No | Internal compiler/runtime interface synchronized with this release set. |
@pulse-compute/wasm-library-kit | Guide | Implementation/transitive surface | No | Internal package-lowering interface synchronized with this release set. |
@pulse-compute/provider-node | Guide | Implementation/transitive surface | Yes | The /server export is an explicit supported-entry-point exception within this implementation package: finite production HTTP for explicit Node Native and JavaScript builds. Forwarding, generated output, transforms, S3-body bindings and blob-specific production qualification remain separate. /toolchain serves the CLI; all other provider subpaths remain internal. |
@pulse-compute/wasm-runtime-core-as | Guide | Implementation/transitive surface | No | Internal code-generation interface synchronized with this release set. |
@pulse-compute/wasm-schema-json | Guide | Implementation/transitive surface | No | Internal schema compiler interface synchronized with this release set. |
Tier definitions#
Canonical application surface#
Fully documented and supported as the Pulse application authoring or workflow contract.
Supported provider/extension surface#
Documented entry points are supported; implementation and toolchain subpaths are explicitly excluded.
Implementation/transitive surface#
Installable as part of the synchronized release set. Only explicitly listed supported entry points carry their stated compatibility guarantee; all other interfaces are internal.
Reading package READMEs#
Every packed README begins with a generated status block covering audience, direct-install guidance, supported entry points, and stability. An export that is not listed in that block is not automatically a supported application-author entry point.
Extension and provider boundary in 1.0.0-beta.6#
Pulse supports the documented package-owned assets and GRIP facades and the documented Fastly provider entry points. Their implementation demonstrates the internal contract, but 1.0.0-beta.6 does not expose a general third-party plugin registry:
- lowerer manifests are accepted only from trusted first-party release packages;
- arbitrary external lowerer discovery and execution are not supported;
- provider selection is limited to
node,fastly, and compile-onlynone; - adding a new lowerer or provider currently means changing and testing the synchronized Pulse release set.
Documentation may explain lowering and the internal contract, but it must not promise that an external npm package can self-register a lowerer or provider. A future public plugin API requires an explicit trust model, discovery, version negotiation, security policy, and compatibility contract.
Installed documentation#
@pulse-compute/runtime ships its canonical API reference and Beta scope. @pulse-compute/cli ships the public documentation hierarchy, CLI/config/diagnostic references, bounded compatibility material, and runnable example sources. Package README links must resolve either inside their own tarball or to an exact-version hosted Pulse documentation URL.