docs(certification): align sharing eligibility and dedicated fallback (#138)

Co-authored-by: Hermes Agent <[email protected]>
2026-11-03 22:32:27 +08:00 · 2026-09-29 00:50:44 +08:00
parent 8da464933a
commit a87f896a91
9 changed files with 15 additions and 15 deletions
@@ -3,7 +3,7 @@ title: "Certified plugins and stateless components"
 description: "Why certified plugins share workers and how to implement stateless-v1 components."
 ---

-A **Certified Plugin** badge grants a specific immutable plugin artifact eligibility for cross-tenant shared execution. Installations of the same artifact digest may share one Worker, one `BasePlugin` object and one instance of each component. Each installation contributes only lightweight configuration, authority and lifecycle context. “Each component” means one instance for every declared component manifest across EventListener, Tool, Command, KnowledgeEngine, Parser, Page and Runner.
+A valid trusted certificate on the exact downloaded plugin artifact grants eligibility for cross-tenant singleton Worker execution in LangBot Cloud. A marketplace **Certified Plugin** badge alone does not prove that the downloaded ZIP passes verification or that a live Worker is shared. Installations of the same artifact digest may share one Worker, one `BasePlugin` object and one instance of each component. Each installation contributes only lightweight configuration, authority and lifecycle context. “Each component” means one instance for every declared component manifest across EventListener, Tool, Command, KnowledgeEngine, Parser, Page and Runner.

 ## Declaration

@@ -16,7 +16,7 @@ execution:
  componentModel: stateless-v1
 ```

-Both fields are required. The declaration is an application, not approval: advisory source review, explicit human approval and a signature over the exact artifact remain mandatory.
+Both fields are required. The declaration is an application, not approval: authenticated artifact-bound advisory source review, explicit human approval and a valid trusted signature over the exact artifact remain mandatory. Advisory review is an internal prerequisite, not an intermediate certification tier.

 ## Stateless component contract

@@ -55,4 +55,4 @@ Shared initialization has no tenant config, so this reads empty/stale data or fa

 ## Legacy compatibility

-Legacy source and unsigned packages remain compatible on dedicated Workers. In OSS, packages without a trusted `stateless-v1` v2 certificate stay dedicated according to admission policy. Cloud can reject packages that do not meet its certificate policy before installation; existing installations are not proof of new eligibility. Changing only the manifest does not satisfy certification review.
+Legacy source and unsigned packages remain compatible on dedicated Workers, including unsigned Cloud installs. There is no dedicated certification or dedicated signature. Cloud must reject malformed, forged, untrusted or legacy signed certificates lacking the `stateless-v1` claim; they are not unsigned fallbacks. OSS ships without a built-in certification issuer public key, supports one Workspace and does not support configuring a key to enable shared-certified execution. Existing installations and a marketplace badge are not proof of shared Worker placement. Changing only the manifest does not satisfy certification review.
@@ -84,7 +84,7 @@ If your release is designed for certification, declare both `execution.sharedRun

 LangBot Space checks the exact submitted package, runs an advisory code review, and requires a human approval before a Certified Plugin badge can be issued. Certification is bound to the reviewed package version and checksum. Keep workspace configuration, storage, credentials, logs, and background work scoped to the active installation. Do not rely on mutable process-global state.

-If the review finds that the release cannot meet these requirements, publish it as a normal dedicated plugin and address the findings in a later immutable version. See [Certified Plugins](/en/plugin/certified-plugins) for user-visible behavior.
+If the review finds that the release cannot meet these requirements, submit an unsigned normal dedicated plugin and address the findings in a later immutable version. There is no dedicated certification or intermediate certification tier. See [Certified Plugins](/en/plugin/certified-plugins) for user-visible behavior.

 <img width="600" src="/images/zh/plugin/dev/plugin_submission.png" />

@@ -4,7 +4,7 @@ title: "LangBot Plugins"

 LangBot is composed of various internal components such as Large Language Model tools, commands, messaging platform adapters, LLM requesters, and more. To meet extensibility and flexibility requirements, we have implemented a production-grade plugin system.

-Plugins are managed uniformly by the Plugin Runtime. Most plugins use a dedicated runtime; a reviewed release may be shown as a [Certified Plugin](/en/plugin/certified-plugins) and use the Certified Plugin allowance in LangBot Cloud.
+Plugins are managed uniformly by the Plugin Runtime. Most plugins use a dedicated runtime; a release with a valid artifact-bound certificate may qualify for [cross-tenant shared execution](/en/plugin/certified-plugins) in LangBot Cloud. Review alone is not certification.

 <img width="600" src="/images/zh/plugin/dev/plugin_system_arch.png" />