Site IntegrityDemonstrated real incidentv1.22.12026-06-28T20:15:00Z

In plain English

This page is part of the technical reference. It keeps the expert detail but starts with a plain-language summary for first-time readers.

Why this matters: AI risk can come from the whole arrangement, not one obvious model.
What to look for: data, memory, routes, adapters, tools, evaluators, updates, and rollback paths.
Technical version below: the expert terminology remains available and is linked through the glossary.

Root Extract Package

Evidence levelDemonstrated real incidentTechnical label: Demonstrated

This release includes a root extract ZIP in addition to the WordPress theme ZIP.

Direct answer

Use the WordPress theme ZIP for WordPress admin upload. Use the root extract ZIP only when the extraction target should receive files directly at its root. The root ZIP intentionally omits the top-level cognivirus/ wrapping folder.

schematic · package deployment

Two ZIPs, two extraction targets.

The theme ZIP contains a top-level folder for WordPress upload. The root ZIP contains files at archive root for direct extraction.

Theme ZIPcognivirus/style.csscognivirus/functions.phpcognivirus/content/

Root ZIPstyle.cssfunctions.phpcontent/

Expected root ZIP shape

style.css
functions.php
index.php
AGENTS.md
app/
content/
docs/
public/
.uai/
.well-known/
robots.txt
sitemap.xml
llms.txt
ai.txt
ai-manifest.json

Deployment caution

Extracting directly into a live root can overwrite files with the same names. Back up the current root first, then verify route behavior after extraction.