Npcink Cloud Addon

Npcink Cloud Addon connects a local WordPress site to npcink-cloud .

It stores the Cloud Base URL and Cloud API Key, parses Cloud-issued keys, signs runtime requests, probes health, reads Cloud entitlement summaries, and can upload metadata-only plugin behavior events after explicit administrator opt-in.

It does not execute WordPress writes, approve proposals, own billing truth, or manage prompts, routers, presets, workflow/task queues, scheduler truth, or workflow engines. Its observability buffer is only a bounded delivery buffer for monitoring metadata and is not Core audit, proposal, execution, billing, or workflow truth.

For media derivative jobs, local host code may pass the read-only npcink-abilities-toolkit/build-media-derivative-cloud-request ability output and a short TTL source artifact descriptor to the addon for signed Cloud dispatch. The addon requires verified Cloud settings, rejects credential-bearing ability payloads, and returns proposal-ready data with final_write_owner=local_wordpress_host . Final review, recording, replacement, rollback, and WordPress writes remain in the local host/Core approval path.

For plugin monitoring, the addon may upload operational metadata such as plugin slug/version, event kind, status, timing, error code, route, proposal id, ability id, correlation id, and counters. It must not upload prompts, generated content, article body content, media bytes, raw request or response payloads, provider credentials, Cloud API secrets, passwords, cookies, nonces, Authorization headers, database names, table names, or filesystem paths. Customer-journey monitoring is limited to supported editor steps such as generation started, succeeded, failed, retried, accepted, saved, or abandoned. It does not send raw WordPress user or post IDs, email addresses, URLs, DOM data, or free-form error messages. Uploads are authenticated to the configured Cloud site, so they may be associated with that site; they are not used for advertising, individual user scoring, or automatic WordPress content changes. During a bounded invited-user observation window, the site operator may add one opaque cohort identifier so Cloud summaries can exclude earlier technical test events. The identifier must not encode an editor, account, site, article, prompt, or content identity.

External Services

This plugin connects to the Npcink Cloud service configured by the site administrator through the Cloud Base URL setting.

The plugin contacts the configured Cloud service after Portal authorization and connection verification, or when an administrator uses the advanced recovery form with a Cloud Base URL and API key. A local Npcink component may also explicitly use the Cloud runtime client.