Public plugin API readiness#
Decision: Deferred. No public third-party plugin API is available in this release.
Pulse 1.0.0-beta.1 keeps general plugin discovery and package lowering inside the synchronized trusted release. Provider bootstrap is explicit and exact. The current boundaries are:
- Lowerers: trusted first-party release packages only.
- Providers: explicit package selection through pulse.provider-toolchain.v1; bare host IDs use the @pulse-compute/provider-<id> convention, scoped names are exact, and none is internal; no scanning or self-registration.
Readiness requirements#
| Requirement | Status |
|---|---|
trustModel | Not implemented |
packageDiscovery | Not implemented |
versionNegotiation | Not implemented |
securityPolicy | Not implemented |
compatibilityContract | Not implemented |
isolatedPackageLoading | Not implemented |
The explicit provider toolchain contract does not imply general plugin discovery, isolated loading, or lowerer extensibility. Do not publish a general third-party plugin API design until every readiness requirement is implemented and release-gated.
The machine-readable readiness record and release validation enforce this boundary. Contributor guides explain how to add a first-party lowerer or provider toolchain; neither process uses package scanning or self-registration.
Machine-readable status is published as plugin-readiness.json.