Astricode Ops

Astricode Ops brings essential WordPress operations together in one clear administrative workspace.

Its workflow is built around five principles:

• Analyze what is happening.
• Explain the findings.
• Protect critical data.
• Act through controlled operations.
• Verify the result.

Astricode Ops prioritizes explicit actions, technical evidence, safeguards, and reversible workflows wherever the operation supports them.

Site health and diagnostics

• Unified operational dashboard.
• WordPress and PHP requirement checks.
• Database, cron, filesystem, locking, and WebP diagnostics.
• Clear health scores based on real installation data.
• Detection of technical conditions that require attention.

Registration protection and user intelligence

• Registration firewall for native and third-party registration routes.
• Risk scoring based on structural and behavioural signals.
• Repeated-offender detection and IP blocking.
• User audits with reasons and risk distribution.
• Manual protection for legitimate accounts.
• Safeguards for administrators, privileged roles, active users, authors, and users connected to site content.
• Controlled manual and automatic cleanup workflows.

Database operations

• Database size and health analysis.
• Table optimization with measured results.
• Inspection of WordPress options and autoloaded data.
• Inspection of post metadata and plugin tables.
• Protected previews and controlled exports.
• Manual protection of critical records.
• Reversible quarantine for supported option, metadata, and table operations.
• Integrity verification before restoration.
• Explicit restoration and permanent purge workflows.

WebP automation

• Incremental JPG and PNG conversion.
• Automatic background batches.
• Configurable quality, frequency, and batch size.
• Preservation of every original image.
• Conversion of WordPress-generated image sizes.
• Coverage, activity, savings, skipped-file, and failure metrics.
• Manual execution and pause controls.

Activity logs

• Registration blocking records.
• User cleanup activity.
• WebP conversion results.
• Database operation records.
• Limited log retention to avoid uncontrolled growth.

Important safety notes

• Create and verify a full backup before performing database or user cleanup operations.
• Database quarantine is an additional recovery mechanism, not a replacement for backups.
• Original JPG and PNG files are preserved during WebP conversion.
• User cleanup includes safeguards, but every site has a different data model and should be reviewed before automation is enabled.
• Deactivation removes scheduled tasks and execution locks while preserving configuration, statistics, quarantine records, and logs.
• Removing the plugin files does not automatically delete persisted data.
• When WP-Cron is disabled, the server must execute wp-cron.php through a real scheduled task.

1. Upload the astricode-ops folder to the /wp-content/plugins/ directory.
2. Activate Astricode Ops from the WordPress Plugins screen.
3. Open Astricode Ops > Diagnostics.
4. Run the technical diagnostic before enabling automated operations.
5. Review the Dashboard and configure only the automation your site needs.

Does Astricode Ops delete the original JPG or PNG files?

No. It creates WebP alternatives alongside the original files and WordPress-generated image sizes.

Can I deactivate the plugin without losing its configuration?

Yes. Deactivation removes scheduled execution and locks, but keeps the stored configuration, statistics, quarantine records, and logs.

Does Astricode Ops automatically delete users after activation?

No. Automated cleanup must be configured explicitly. The plugin also applies role, activity, content, manual-protection, and current-user safeguards.

Is reversible quarantine a replacement for a database backup?

No. Quarantine adds a controlled restoration path for supported operations, but a verified external backup remains essential.

Why does the diagnostic inspect the uploads directory?

WebP conversion requires write access to the current and historical upload folders containing the physical image files.

What happens when WP-Cron is disabled?

Astricode Ops reports the condition. A real server cron task must execute WordPress cron regularly for automated batches to continue.

1.0.5

• Adds the formal extension contract required by Astricode Ops Pro.
• Exposes the versioned Free/Pro extension API and core-ready lifecycle contract.
• Keeps Astricode Ops Free functionality and public compatibility unchanged.

1.0.4

• Prepared the stable Astricode Ops package for public distribution.
• Added registration firewall traceability to the Dashboard.
• Added counters for native registration, custom forms, REST API, AJAX, wp_insert_user, registration_errors, user_register, and recent-user consistency checks.
• Added the last detected registration route, blocking layer, score, username, and email domain without storing the complete email address.
• Fixed duplicate IP penalization during post-registration safeguards.

1.0.3

• Expanded registration protection to third-party forms and integrations.
• Added consistency checks for recently created accounts.
• Centralized automatic spam-user removal and event traceability.

1.0.2

• Added separate pre-registration and post-registration risk thresholds.
• Added an immediate safeguard for unequivocally malicious newly created accounts.
• Preserved administrator, WP-CLI, cron, privileged-role, and explicitly allowed registrations.

1.0.1

• Unified registration protection with the complete user risk engine.
• Added protection for registration flows using wp_insert_user().
• Added firewall consistency diagnostics.

1.0.0

• First stable release of the original production-tested architecture.
• Included health diagnostics, registration protection, user auditing, database operations, reversible quarantine, WebP automation, and activity logs.
• Preserved conservative cleanup rules and persistent data during deactivation.

Older development history is preserved in the project documentation.