Setyenv · Docs
  • English
  • Spanish
  • Chinese
  • Japanese
  • Arabic
  • German
  • French
  • Hindi
  • Indonesian
  • Italian
  • Dutch
  • Portuguese
  • Russian
  • Turkish

Glossary

Definitions of every term used across this documentation. If a concept needs more than a paragraph it gets its own page under Concepts — this page is for one-line lookups.

A

Activation The process of binding a license key to a specific WordPress site, counted against the license's site limit.

Agent In WP-PFAgent: an instance of the natural-language interface that sits on top of WP-PFWorkflow's REST API and can build / run / inspect / fix workflows from sentences.

Agent loop The multi-turn conversation where the agent calls a tool, sees the result, decides whether to call another, etc., until it has either answered the user or needs human confirmation.

B

BYOK (Bring Your Own Keys) The model where you supply your own credentials to LLM providers (OpenAI, Anthropic, etc.) rather than going through Setyenv's billing. WP-PFAgent is BYOK-only.

C

Connection Stored credentials a workflow uses to talk to a third-party service. Connections are encrypted at rest with AES-256-GCM and the raw value is never returned by the REST API.

D

DLQ (Dead Letter Queue) Where outgoing webhook payloads land when delivery fails after the configured retries are exhausted. Inspectable from the Workflow admin.

E

Entity In WP-PFManagement: a user-defined record type with fields, forms and a list view. Roughly equivalent to a custom post type but with proper field types and queryability.

Execution One run of a workflow, end to end. Has a timeline of nodes visited, inputs and outputs at each step, and a final status (success, failed, partial).

F

Fingerprint (site fingerprint) A SHA-256 hash of home_url + a server-side salt. Used to uniquely identify an installed WP without sending the URL in cleartext on every API call.

I

Idempotency lock Mechanism that prevents the same trigger event from kicking off the same workflow twice. Implemented as a row in wp_pfw_idempotency keyed on (workflow_id, event_hash).

N

Node A single step in a workflow. Each node has a type (trigger, condition, action), inputs, outputs and a category in the node library. There are 119 built-in nodes across 16 categories.

P

Per-site token The HMAC-signed credential the portal issues at activation. Used by the plugin to authenticate every subsequent call to the portal without re-sending the license key.

R

Replay Re-run a past execution from any node in its timeline. Used for debugging or for recovering from a downstream service that was temporarily down.

Reconciler (Management) A planner that diffs a desired entity schema against the current one and produces an idempotent set of CREATE / ALTER / DROP operations. Supports dry-run.

S

Side-effect confirmation gate (Agent) The mandatory checkpoint where the agent stops and asks the user to confirm before performing any action that writes, sends or deletes. Off by default for read-only operations.

Slot One activation count against a license's site limit. An x5 license has 5 slots.

T

Telemetry Daily structural heartbeat from each licensed install. Plugin version, WP version, PHP version, error count. No workflow, conversation or entity content is ever sent.

Tool (Agent) A typed function the agent can invoke. Currently 19 tools, each mapping to a verb on WP-PFWorkflow's REST API (list, build, run, inspect, fix).

W

Workflow A directed graph of nodes that runs when a trigger fires. Stored as a custom post type (pfw_workflow) so you can use WP's versioning, search and revisions.