JbigDeaL

Loading

Sample Page

Alpha52 is complete and built from the real Alpha51 package.

Alpha52 — Strategy Runtime Executor Engine

Alpha52 upgrades all five registered strategy executors to controlled runtime capability:

  • Unload

  • Conditional loading

  • Deferred execution

  • Interaction loading

  • Scope narrowing

They operate only through signed, expiring, exact-page verification URLs. Ordinary visitors, normal scans, and published rules remain unchanged.

Exact-page verification

Every eligible manifest now receives two links:

Baseline
Candidate

The Baseline URL preserves the page’s original enqueue and execution behavior.

The Candidate URL validates:

  • Manifest ID

  • Candidate hash

  • HMAC token

  • Expiration time

  • Exact page URL

  • Exact executor version

  • Exact strategy and handles

A manifest cannot execute on another page or after the signed URL expires.

Conditional Loading Executor

During a signed Candidate request, the executor prevents the selected handles from loading on that exact page.

This provides controlled testing for plans such as:

/sample-page/
→ conditionally skip WooCommerce layout CSS

It does not create a public conditional rule.

Scope Narrowing Executor

The scope-narrowing executor applies the candidate only to the exact verified page URL.

It can test whether a globally loaded stylesheet, such as wc-blocks, can be limited more narrowly without treating every Static Page as equivalent.

Deferred Execution Executor

For selected JavaScript handles, Alpha52 adds defer only during the signed Candidate visit.

It does not change dependency registration or permanently edit script files.

This enables controlled verification of plans involving handles such as:

  • sourcebuster

  • order-attribution

Interaction Loading Executor

Selected scripts can now be removed from the initial request and loaded after the first safe user interaction:

  • Pointer interaction

  • Keyboard input

  • Touch

  • Scroll

A five-second fallback loads the asset even if no interaction occurs, preventing the candidate from leaving the functionality unavailable indefinitely.

Evidence isolation

Alpha52 verification requests are marked as controlled strategy traffic.

They are excluded from:

  • Trusted production observations

  • Fingerprints

  • Component trends

  • Opportunity learning

  • Page evidence maturity

This prevents verification candidates from teaching the intelligence engines that their modified asset set is normal production behavior.

Runtime safety

Every candidate remains protected by:

  • Anonymous candidate visits

  • Exact URL matching

  • Exact page UUID matching

  • Runtime-contract preservation

  • Required-feature preservation

  • Automatic expiry

  • No-cache response headers

  • Explicit rollback operations

  • Manual publication authority

Alpha52 does not automatically publish any conditional, defer, interaction, or scope-narrowing rule.

Qualification integration

Alpha49 now recognizes the new runtime executors as available.

Stable, evidence-qualified strategies can advance to:

Ready for controlled strategy verification

Strategies with insufficient page observations remain in:

Needs more evidence

Dashboard updates

The Alpha52 panel now shows:

  • Five runtime-capable executors

  • Compiled reversible manifests

  • Manifests ready for signed verification

  • Baseline and Candidate buttons

  • Exact-page strategy and handles

  • Candidate status

  • Rollback availability

All 116 PHP files passed syntax validation, Composer autoloading was confirmed, and the ZIP passed archive-integrity testing.