Cortex Architecture
Parallel data layer and execution models.
Shooio Cortex is not a theme. It is a structural enhancement layer designed for WordPress, operating strictly out-of-band.
1. The Parallel Constraint
We adopt a strict isolation policy regarding the native `wp_posts` tables. Modifying the underlying taxonomy of a CMS to force-fit business logic is an architectural anti-pattern.
Cortex builds an independent, parallel data dimension. E-commerce relationships, point systems, and behavioral event logs sit within dedicated, normalized relational structures.
2. Generation-based Invalidation
Classic cache purging through string matching scales poorly. Cortex uses a Generation-based invalidation mechanism.
const key = `entity:user:${userId}:gen:${generation}`;
When an aggregate root mutates, its corresponding generation integer undergoes an atomic `INCR`. All reads bind to this generation. Invalidation complexity becomes O(1) instantly, entirely skipping global Redis `KEYS` scans.
3. Hydration & Plugin Deflation
WordPress environments bloat because of isolated plugin networks executing overlapping queries.
Cortex centralizes the resolution. It hydrates domain objects exactly once per request lifecycle. Extension models interface with Cortex's memory pool, completely suppressing redundant external queries.