Athenian Platform Kernel (APK)
product details.
Athenian Platform Kernel (APK) acts as the shared runtime for event-driven workflows, async automation, schema registration, inspection tools, and integration surfaces across Athenian WordPress plugins. It helps teams standardize how connected plugins register data, trigger work, inspect state, and execute background automation while keeping data, permissions, and automation aligned with the broader Athenian Platform Ecosystem.
Athenian Platform Kernel is the low-level orchestration and data-governance layer for the Athenian WordPress and WooCommerce plugin ecosystem. It provides a shared event bus, asynchronous workflow runner, workflow run logs, platform schema registry, REST schema endpoints, optional WPGraphQL helpers, WooCommerce event bridges, and a hybrid-ready must-use plugin shim.
Where Athenian Platform Core acts as the broader commerce and platform service layer, Athenian Platform Kernel is the runtime substrate that helps plugins coordinate safely. Other modules can emit standardized events, register schema fields, inspect platform data, trigger workflows, and delegate downstream actions without creating brittle direct plugin dependencies.
APK is especially useful for complex WooCommerce environments where orders, payments, stock events, AI actions, media approvals, vendor workflows, fulfillment steps, and customer automations need to interact without slowing down checkout or hiding side effects. Events can be queued through Action Scheduler, WP-Cron, or synchronous development mode, and each workflow run can be logged for visibility, debugging, and future audit trails.
For Athenian Platform builds, the Kernel is best positioned as the event-driven operating substrate: the layer that gives the plugin ecosystem a shared language for events, workflow execution, schema definitions, REST/GraphQL inspection, and automation governance.
Event-Driven Runtime
Coordinate Platform Events Without Brittle Plugin-to-Plugin Dependencies
Athenian Platform Kernel gives Athenian plugins a normalized event bus,
async workflow execution, workflow records, conditions, actions, and run
logs so platform automations can be coordinated without blocking checkout,
admin, payment, or API requests.
| Runtime Layer | Operational Value |
|---|---|
| Event Bus | Allows plugins to emit normalized platform events through apk/event instead of directly calling downstream modules. |
| Async Execution | Queues workflow jobs through Action Scheduler when available, WP-Cron fallback, or synchronous mode for development and testing. |
| Workflow CPT | Stores workflow definitions in apk_workflow records with enabled state, trigger event, and JSON workflow specs. |
| Run History | Logs workflow executions, statuses, messages, payloads, and results in the dedicated apk_runs table. |
- Supports built-in triggers such as
order.placed,order.paid,stock.low,media.approved, andai.intent_detected. - Includes built-in conditions such as
always,user.role_in,order.total_gte, andorder.has_shipping_class. - Includes built-in actions such as
log.notice,email.send,webhook.post, andhook.fire. - Uses
hook.fireto delegate side effects to downstream plugins without hard-coding direct dependencies.
Platform Orchestration
Give Athenian Plugins a Shared Automation Backbone
Athenian Platform Kernel adds admin screens, WooCommerce event bridges,
test tools, run visibility, schema inspection, settings, retention controls,
and optional MU helper functions for hybrid platform bootstrapping.
| Platform Surface | Operational Purpose |
|---|---|
| Admin Workspace | Adds Athenian Kernel screens for dashboard status, workflows, runs, data registry, data inspector, settings, and developer test triggers. |
| WooCommerce Bridge | Emits normalized order.placed and order.paid events from WooCommerce order lifecycle hooks. |
| Duplicate Protection | Uses order meta markers such as _apk_emitted_order_placed and _apk_emitted_order_paid to avoid duplicate event emissions. |
| Hybrid MU Shim | Includes an optional must-use shim with helper functions such as apk_is_kernel_active() and apk_emit_event(). |
The difference between plugins and a platform:
APK gives the Athenian stack a shared event contract, workflow runner,
run history, data registry, and inspection layer so modules can coordinate
through governed events instead of hidden one-off integrations.
- Adds a top-level Athenian Kernel admin menu.
- Uses settings for async mode, log retention, max payload size, test tools, public schema access, and GraphQL helpers.
- Limits REST inspection to
manage_optionsand keeps public schema exposure disabled by default. - Builds toward a visual workflow builder, signed webhooks, retry policies, workflow templates, expanded schema definitions, workflow import/export, event catalog screens, Action Scheduler deep links, and WP-CLI tooling.
Athenian Platform Kernel is the low-level orchestration and data-governance layer for the Athenian WordPress and WooCommerce plugin ecosystem. It provides a shared event bus, asynchronous workflow runner, workflow run logs, platform schema registry, REST schema endpoints, optional WPGraphQL helpers, WooCommerce event bridges, and a hybrid-ready must-use plugin shim.
Where Athenian Platform Core acts as the broader commerce and platform service layer, Athenian Platform Kernel is the runtime substrate that helps plugins coordinate safely. Other modules can emit standardized events, register schema fields, inspect platform data, trigger workflows, and delegate downstream actions without creating brittle direct plugin dependencies.
APK is especially useful for complex WooCommerce environments where orders, payments, stock events, AI actions, media approvals, vendor workflows, fulfillment steps, and customer automations need to interact without slowing down checkout or hiding side effects. Events can be queued through Action Scheduler, WP-Cron, or synchronous development mode, and each workflow run can be logged for visibility, debugging, and future audit trails.
For Athenian Platform builds, the Kernel is best positioned as the event-driven operating substrate: the layer that gives the plugin ecosystem a shared language for events, workflow execution, schema definitions, REST/GraphQL inspection, and automation governance.