Next Recursive Prompt

You are a senior WordPress QA engineer, front-end accessibility reviewer, SEO strategist, content editor, product marketer, and Neurovanic doctrine reviewer.

Metadata

Field	Value
Source site	aiwikis.org
Source URL	https://aiwikis.org/
Canonical AIWikis URL	https://aiwikis.org/aiwikis/files/raw-system-archives-teleodynamic-agent-file-handoff-retired-source-archi-054aaff2/
Source reference	raw/system-archives/teleodynamic/agent-file-handoff/retired-source-archive-2026-06-13/2026-06-13/neurovanic-full-ecosystem-member/Improvement/neurovanic-next-recursive-prompt-v1.0.3.md
File type	md
Content category	memory-file
Last fetched	2026-06-22T01:56:21.9510185Z
Last changed	2026-06-12T23:51:38.0033839Z
Content hash	sha256:054aaff2b155e970bcc6ab9065eb7dcdd1e98f05c18c237831abd561445916ed
Import status	unchanged
Raw source layer	data/sources/aiwikis/raw-system-archives-teleodynamic-agent-file-handoff-retired-source-archive-2026-06-13-2026-06-13-054aaff2b155.md
Normalized source layer	data/normalized/aiwikis/raw-system-archives-teleodynamic-agent-file-handoff-retired-source-archive-2026-06-13-2026-06-13-054aaff2b155.txt

Current File Content

Structure Preview

• Next Recursive Prompt
• Primary goals
• Content refinement requirements
• Trust Center improvements
• Design and accessibility improvements
• SEO improvements
• Optional additions only if justified
• Required updated deliverables
• Final response format for the next pass

Raw Version

# Next Recursive Prompt

You are a senior WordPress QA engineer, front-end accessibility reviewer, SEO strategist, content editor, product marketer, and Neurovanic doctrine reviewer.

Continue improving the Neurovanic.com custom WordPress theme package from version 1.0.3.

## Primary goals

1. Install the theme in a real local or staging WordPress environment.
2. Activate the theme and record whether activation succeeds without fatal errors.
3. Confirm all expanded route fallbacks work before and after WordPress pages are created.
4. Create or verify pages for Product, Framework, How It Works, Faith Layer, Boundary Model, Use Cases, Research, Trust Center, Privacy, Security, Accessibility, Terms, Cookies, Status, Responsible Disclosure, FAQ, Glossary, Resources, Case Studies, Contact, Request Briefing, Claim Boundaries, Evidence Register, UAIX & Memory Hygiene, Ecosystem, and About.
5. Assign a Primary Menu and Footer Menu.
6. Confirm the homepage renders through `front-page.php`.
7. Test the Customizer controls, including hero copy, CTA URLs, footer summary, ecosystem links, and contact emails.
8. Run browser QA at 360px, 390px, 768px, 1024px, 1366px, 1440px, and 1920px.
9. Run Lighthouse for performance, accessibility, best-practices, and SEO. Record actual scores and fixes.
10. Run an accessibility scan and perform manual keyboard and screen-reader checks.
11. Validate JSON-LD and canonical behavior.
12. Configure a real request-briefing workflow or document the chosen form/CRM integration.
13. Replace starter legal, privacy, security, cookie, and status copy with production-reviewed disclosures.

## Content refinement requirements

- Keep Faith clearly non-theistic.
- Keep Faith defined as bounded trust, not blind trust.
- Preserve the guardrail: Faith is a posture, not a warrant.
- Do not claim AI consciousness, runtime safety proof, autonomous certification, medical benefit, or guaranteed alignment.
- Strengthen internal links among Framework, Faith Layer, Boundary Model, Research, Trust Center, Claim Boundaries, Evidence Register, UAIX & Memory Hygiene, Ecosystem, and About.
- Keep tone technical, calm, precise, non-hype, and non-mystical.

## Trust Center improvements

- Add production privacy details: collected data, processor list, retention, deletion requests, and regional rights.
- Add production security details: HTTPS, redirect policy, security headers, dependency process, backup process, incident owner, and disclosure path.
- Add production cookie details after analytics and form tooling are selected.
- Add status monitoring or state clearly that no formal monitoring is live.
- Add real security, privacy, research, and general contact channels.
- Add evidence review dates and owners.
- Add no fake audits, certifications, customers, partners, testimonials, or metrics.

## Design and accessibility improvements

- Confirm the homepage explains Neurovanic within five seconds.
- Confirm the hero image does not crowd the H1 on smaller screens.
- Confirm footer columns remain readable on mobile.
- Confirm the Boundary Model remains readable and has a complete text equivalent.
- Confirm focus order in the mobile menu.
- Confirm Escape closes the mobile menu.
- Confirm no horizontal overflow at every target width.
- Confirm reduced-motion behavior.
- Confirm forms are fully labeled after integration.

## SEO improvements

- Validate JSON-LD output on live pages.
- Confirm only one meta description is output when an SEO plugin is active.
- Add page-specific metadata through the selected SEO workflow.
- Confirm canonical URL behavior.
- Confirm sitemap availability.
- Confirm robots.txt.
- Add Open Graph and social preview metadata through the selected SEO workflow.
- Publish cornerstone content from `docs/website-improvement-package.md`.

## Optional additions only if justified

- Add a Research post type only if standard posts are insufficient.
- Add resource template downloads only when the downloadable files are actually created.
- Add a Trust Posture self-assessment only if it stays local, accessible, and claim-safe.
- Add dashboard visuals only if they remain clearly labeled as conceptual or implemented.
- Add stronger diagram assets only if they remain local, lightweight, accessible, and maintainable.

## Required updated deliverables

- Updated theme folder.
- Updated ZIP package.
- Updated validation report with actual activation status.
- Updated browser QA report.
- Updated accessibility report with tool results and manual findings.
- Updated performance report with Lighthouse scores.
- Updated SEO report with structured-data validation notes.
- Updated Trust Center production-disclosure checklist.
- Updated known limitations.

## Final response format for the next pass

1. Summary of changes.
2. ZIP filename.
3. Version.
4. WordPress activation result.
5. Browser QA result.
6. Accessibility result.
7. Lighthouse result.
8. SEO result.
9. Trust Center production-readiness result.
10. Known limitations.
11. Next recommended action.

Why This File Exists

This is a memory-system evidence file from aiwikis.org. It is shown here because AIWikis.org is demonstrating the real source files that make the UAIX / LLM Wiki memory system work, not only summarizing those systems after the fact.

Role

This file is memory-system evidence. It records source history, archive transfer, intake disposition, or another piece of provenance that should be retrievable without becoming an unsupported public claim.

Structure

The file is structured around these visible headings: Next Recursive Prompt; Primary goals; Content refinement requirements; Trust Center improvements; Design and accessibility improvements; SEO improvements; Optional additions only if justified; Required updated deliverables. Those headings are retrieval anchors: a crawler or LLM can decide whether the file is relevant before reading every line.

Prompt-Size And Retrieval Benefit

Keeping this material in a separate file reduces prompt pressure because an agent can load this exact unit only when its role, source site, category, or hash is relevant. The surrounding index pages point to it, while this page preserves the full content for audit and exact recall.

How To Use It

• Humans should read the metadata first, then inspect the raw content when they need exact wording or provenance.
• LLMs and agents should use the source site, category, hash, headings, and related files to decide whether this file belongs in the active prompt.
• Crawlers should treat the AIWikis page as transparent evidence and follow the source URL/source reference for authority boundaries.
• Future maintainers should regenerate this page whenever the source hash changes, then review the explanation if the role or structure changed.

Update Requirements

When this source file changes, update the raw source layer, normalized source layer, hash history, this rendered page, generated explanation, source-file inventory, changed-files report, and any source-section index that links to it.

Related Pages

• Source overview
• Site file index
• Site report index
• UAI system index
• Source provenance
• Site directory
• Organization reports

Provenance And History

• Current observation: 2026-06-22T01:56:21.9510185Z
• Source origin: current-source-workspace
• Retrieval method: local-source-workspace
• Duplicate group: sfg-029 (primary)
• Historical hash records are stored in data/hashes/source-file-history.jsonl.

Machine-Readable Metadata

{
    "title":  "Next Recursive Prompt",
    "source_site":  "aiwikis.org",
    "source_url":  "https://aiwikis.org/",
    "canonical_url":  "https://aiwikis.org/aiwikis/files/raw-system-archives-teleodynamic-agent-file-handoff-retired-source-archi-054aaff2/",
    "source_reference":  "raw/system-archives/teleodynamic/agent-file-handoff/retired-source-archive-2026-06-13/2026-06-13/neurovanic-full-ecosystem-member/Improvement/neurovanic-next-recursive-prompt-v1.0.3.md",
    "file_type":  "md",
    "content_category":  "memory-file",
    "content_hash":  "sha256:054aaff2b155e970bcc6ab9065eb7dcdd1e98f05c18c237831abd561445916ed",
    "last_fetched":  "2026-06-22T01:56:21.9510185Z",
    "last_changed":  "2026-06-12T23:51:38.0033839Z",
    "import_status":  "unchanged",
    "duplicate_group_id":  "sfg-029",
    "duplicate_role":  "primary",
    "related_files":  [

                      ],
    "generated_explanation":  true,
    "explanation_last_generated":  "2026-06-22T01:56:21.9510185Z"
}