Editorial draft • Security review required
Security architecture and operating boundaries
This overview describes documented safeguards. It is not a security certification, penetration-test result, availability commitment, or guarantee for every host and plugin stack.
Documented safeguards
Controls built into the workflow
Capability-scoped writes
Every guarded write checks WordPress capabilities, strict schemas, sanitization, and returns actionable errors.
Application Passwords
Authentication uses WordPress credentials supplied through environment variables; secrets must not enter files, logs, fixtures, or prompts.
Draft-first policy
New pages, products, and media do not publish automatically; global changes and restore actions have separate confirmations.
Auditability and stale-plan protection
Plans are fingerprinted, current state is re-read, and reversible change sets or revisions support reviewed recovery paths.
Release evidence
Checksums and a CycloneDX SBOM support artifact review; signature and update-channel policy still depend on the selected release process.
WordPress ownership
Kitten avoids a required hosted content proxy and delegates ACF, SEO, multilingual, forms, and WooCommerce data to their authoritative providers.
Still required
Each deployment needs its own threat, privacy, hosting, plugin, backup, and incident review.
Target-specific testing must cover access, secrets, provider behavior, logs, retention, dependencies, headers, backups, restore, monitoring, and ownership. Do not interpret this page as production approval.