Limitations
The current Node SDK and persistent Core transport are beta test infrastructure. They are not approved for production traffic or financial effects.
Not implemented
- No production Node endpoint, production customer traffic, or live wrapper dispatch.
- No general partner self-provisioning or production credential distribution.
- No SDK-owned secret storage, binary evidence upload, result review, payment, or settlement.
- No claim that pooled assignment supplies fairness, public worker eligibility, or earning eligibility.
- No automatic promotion of a local node into public worker supply.
Adapter status
J3 and 1M use the same Node lifecycle while keeping their browser engines, sessions, and product-specific decisions local. These examples demonstrate the adapter boundary in test mode; they do not enable production Node traffic.
Safe use
- Use local tests or an explicitly supplied isolated staging base URL.
- Keep credentials, browser sessions, proxies, private graphs, and customer data outside SDK payloads.
- Require explicit local authorization before execution.
- Fail closed on cancellation, revocation, or authorization errors.
- Keep application provisioning credentials out of customer-PC bodies.
Deployment boundary: publishing this documentation does not deploy the SDK, a Node runtime, wrapper traffic, or any financial operation.