Local AI Search readiness
Review robots.txt, sitemap, llms.txt, and eligible public content without requiring a Kairoseth account.
Prepare WordPress and WooCommerce for AI Search with a local-first workflow: analyze public signals, select content, generate deterministic llms.txt, and publish only when the administrator chooses to.
Stable public release 0.5.1 is available and verified on GitHub. WordPress.org validation and publication continue as a separate external process.
Local capabilities work without a Kairoseth account. External support is optional, explicit, and separate from the Free product.
Review robots.txt, sitemap, llms.txt, and eligible public content without requiring a Kairoseth account.
Generate a deterministic proposal from selected public content and review it before publishing.
Include public WordPress content and supported public WooCommerce product awareness.
Compare before writing and verify the public result with SHA-256 after publication.
Keep state and operations scoped per site to avoid mixing context across sites.
The Free product works locally; external support starts only after an explicit administrator action.
The workflow prioritizes human control, determinism, and compare-before-write behavior.
Check public readiness signals and eligible content.
Choose which public content belongs in the proposal.
Review deterministic llms.txt output and its hash before publishing.
Write only after an explicit administrator action.
Read the public result back and confirm it matches the expected content.
Loading the support surface does not contact Kairoseth. An external request starts only after an explicit click, and the user decides what additional information to send.
Kairoseth separates identity, organization scope, product roles and product capabilities. A login route, browser state or AI response never becomes an authorization boundary by itself.
Customer resources and access are resolved inside an active organization context rather than treated as global account state.
Owner, Admin and Member authority is assigned per product. Organization membership alone does not automatically grant every product.
Sensitive access, policy and capability decisions remain authoritative on the server instead of trusting client UI state or model output.
Capabilities that can act are introduced behind explicit grants, staged gates and audit rather than implied autonomy.
Review the customer-facing policies that define privacy, security reporting, acceptable use and the current legal operating framework.
You can download and install the verified GitHub release today. Future WordPress.org availability will be announced only after real directory approval.