Content Guardian Content Guardian
Navigation
← CGS3 AI Portal Overview Features Architecture & CAS Developer Guide Security Model Testing & QA Matrix User Documentation Downloads (Pending)
CGS3 Portal / WordPress Plugins / Content Guardian
Release Gate Pending Tests 1–18 Mock PASS

Speedlink3 Content Guardian

A manual-only, deterministic WordPress plugin engineering high-reliability content health audits, duplicate detection, and atomic CAS cleanup with zero LLM runtime dependencies.

Speedlink3 Content Guardian
Mock Test Suite
Tests 1–18 PASS
Target Platform
PHP 8.4 & 8.5
Concurrency Defense
Byte-Exact CAS
Runtime Overhead
No External AI API

Why Speedlink3 Content Guardian?

Content operations in modern newsrooms and digital publications often suffer from link decay, duplicated drafts, and unintended promotional injection from third-party automation tools. Standard search-and-replace scripts or cloud-hosted plugins introduce severe vulnerabilities:

The Risk of Unsafe Updates

Direct SQL updates without byte-exact CAS overwrite intervening author changes. If MySQL collation is case-insensitive, subtle UTF-8 differences cause silent corruption.

The Guardian Guarantee

Guardian takes an exact snapshot to post meta before updating. If the backup fails, the update aborts immediately. CAS comparison runs byte-for-byte in binary collation.

Core Architectural Guarantees

1. Guaranteed Recoverable Backup (Fail-Closed)

Every destructive cleanup operation creates a durable post meta backup containing the exact original post_content and timestamp. If add_post_meta() fails, the operation stops with zero database modification.

2. Byte-Exact Atomic Compare-And-Swap (CAS)

Updates use binary-safe collation comparison (WHERE ID = %d AND CAST(post_content AS BINARY) = CAST(%s AS BINARY)). Accents, Unicode case variants, and trailing whitespace differences cannot bypass conflict detection.

3. Owner-Bound Post Locking

During preview and cleanup operations, posts are locked with cryptographic action tokens bound to the specific administrator user ID. Intervening edits trigger an immediate HTTP 409 Conflict.

Local Developer Quick Start

Run the authorization mock test suite under PHP 8.5:

# Run with all errors reported C:\PHP-8.5.12\php.exe -d "error_reporting=-1" .\tests\preview-authorization-tests.php # Expected status: Tests 1–18 PASS (Exit code 0)

System Specifications

  • Target WordPress: 6.2 - 6.6+
  • Target PHP: 8.4 or 8.5 (Strict mode)
  • Database Target: MySQL 8.0+ / MariaDB 10.5+ (InnoDB)
  • Required Extensions: mbstring, pdo_mysql, json
  • External AI Calls: None (100% Deterministic)