← ACT V4 DoorDEVELOPER HUB · HYBRID CCKDOCUMENTED CANDIDATES ≠ INSTALLED CAPABILITIES

CCK THAT / HYBRID CCK / WORDPRESS ECOSYSTEM

The living capability atlas.

Understand exactly what a field, component, engine, and visual face is made of. Follow the molecule → cell → bones → muscle → skin → follicles. Then bind the proposed function to an observed REST endpoint before staging any design.

77Field and component candidates

24Plugin / engine / face candidates

0Live capabilities verified in this atlas

Every table cell opens the corresponding anatomy layer. Provider capability and plugin version must be independently checked on your WordPress installation.

Find a building block Provider Kind

Vendor candidate items. Select a cell for configuration, environment, expected outcome, and a local specimen.
Source / Field	Molecule	Cell	Bones	Muscle	Skin	Follicles

EXISTING SOURCE · HISTORICAL SITE READBACK

Fourteen WordPress environments, not one imaginary installation

Reuses the October 23, 2026 read-only WP-CLI inventory from the existing source repository. Choose an environment to inspect recorded plugin versions and activation states. This is a historical source projection, not a new scan and not evidence of REST endpoint availability.

WordPress host and container Find installed slug

Recorded WP-CLI plugin status, version and environment; no live proof
Plugin slug	Recorded version	Recorded status	Live REST proof

DIRECT-TO-PROOF TEACHING

How to shape an idea into an executable site.

Do not start in Elementor or a form designer. Start with the site’s installed capabilities and discover the real data and operations.

1. Inventory the real installation.
Read installed/activated plugin names and versions with authorized WordPress administration. Read GET /wp-json/, GET /wp-json/wp/v2/types, GET /wp-json/wp/v2/taxonomies and authorized plugin inventories. Record detected routes and schemas, never assumed ones.
2. Separate Engine, Face, and Mixed.
Engine owns CRUD, business rules, events, policies, storage or services. Face owns templates, presentation, motion and visual controls. A mixed plugin gets separate engine and face responsibilities. ACT V4 never silently takes over their owners.
3. Identify the concept and its anatomy.
Name the Concept, Features, Modules, Nodes, fields, entities, relations and owner. Inspect all six layers: molecule, cell, bones, muscle, skin and follicles. Confirm field type, storage, validation, access and rendering settings.
4. Bind EACH function to a REST operation.
For every proposed action, record HTTP method, exact observed route, parameter schema, request/response shape, principal, scopes, permitted writes, error states and proof. If there is no appropriate REST route, use an authorized WordPress extension/adapter proposal. Do not pretend CLI-only or a visual widget counts as REST.
5. Verify conditions and a real example.
Write environment prerequisites, dependencies, licensing, plugin settings, security and consent, data ownership and expected outcome. Demonstrate a realistic sample interaction before any claim of live success.
6. Stage through Hybrid CCK and Automata.
Build an API-backed CCK passport and adapter, validate CRUD/REST contract parity, acquire approvals for protected effects, then project components into ACT V4 Design DNA. The source owner keeps source authority.
7. Witness and record.
Inspect the actual installed Web and native faces, test denied and allowed actions, verify read-after-write, rollback, provenance and version. Record exact endpoints and receipts. A mock field or test screenshot never turns status green.

Try the mapping worksheet

Write one idea and proposed route. The worksheet exports a planning draft only; it never sends a request.