ZhenSkill Platform Protocol

Skill publishing must enter through developer-controlled routes. Submission actions are expected to verify authentication, developer registration state, and commercial eligibility before a paid listing can go live.

The protocol goal is to prevent public listing changes from bypassing the developer lifecycle or moderation boundary.

Moderation and platform review are the control plane for marketplace quality. A listing should only be publicly discoverable when its operational and commercial state is consistent with policy.

Any legacy route that can bypass review or subscription validation should be treated as out of protocol and corrected at the API layer.

Payment events must be preserved end-to-end without mutating signed payloads. Verification, order updates, entitlement activation, and delivery should be traceable as a single chain.

For paid packages, fulfillment is complete only when the buyer has an active entitlement and the delivery route enforces that entitlement at request time.

When a route exposes commercial resources publicly, allows unauthorized publishing, or breaks signed callback verification, the issue is treated as a blocking operational defect.

The response sequence is contain, patch, redeploy, retest, and update the evidence trail so the operational state is visible to future maintainers.

Any route or UI that represents a promised production capability should be deployed with a matching regression check. Documentation, public navigation, and evidence records should be updated in the same change window when the capability affects acceptance status.