Here’s your independent review report as a file:
VNWO v2.9.1 Independent Review
A. Executive Verdict (≤250 words)

The deployed VNWO.com site does not reflect a v2.9.1 release. Machine‑readable files such as vnwo.json, open‑rules.json, claim‑boundaries.json and llms.txt still declare schema version 2.7.1, while many pages show theme versions between 2.0.0 and 2.2.0. Core download links (Markdown charters, PDFs and both ZIP packs) return HTTP 403 or Not Found, leaving no accessible starter pack or example pack. A contact page still contains WordPress boiler‑plate (“Welcome to WordPress…”) and no actual contact information. Schemas advertised under “Machine‑Readable Governance” also return 403, so key AI‑readable artefacts are unreachable.

The site remains a conceptual framework with extensive static guidance, not a turnkey adoption toolkit. It successfully outlines consent, disclosure, memory, endpoint boundaries, repair, exit and claim limits, and it generally uses semantic HTML that should remain functional without JavaScript. However, adoption friction is high due to missing downloads, inconsistent navigation labels, outdated machine‑readable versions, and heavy copy that may overwhelm first‑time visitors. To evolve into a usable toolkit, VNWO must deliver accessible, versioned packs; align machine‑readable and human‑readable versions; correct navigation dead ends; and provide clear contact and maintainer information.

B. Scorecard
Area	Score (0–5)	Justification
First‑visit comprehension	3	The home and Start Here pages explain VNWO’s purpose and core law within the first screen. However, heavy text and repeated claim boundaries make it hard for newcomers to discern whether VNWO is guidance, software or certification.
Navigation and findability	3	A top nav and “More” menu expose many routes, but labels like Start Here, Charter, Open Rules and Templates overlap conceptually. Some pages (Contact) are unfinished and default posts appear. Download links frequently lead to 403s or missing files.
Use‑case clarity	3	Role‑based prompts on the home page help different audiences start. But there is no working example pack and limited demonstration of how to implement the guidance.
Template usability	2	Templates are readable and copyable, but the filtering interface depends on JavaScript and there is no machine‑readable counterpart for many templates; downloads for Markdown/PDF versions are blocked.
Example quality	1	The advertised AI‑moderated community example exists only as a JSON descriptor; the promised ZIP pack is inaccessible. Without a working example, implementers cannot see how pieces fit together.
Starter‑pack readiness	1	Both vnwo‑starter‑governance‑pack.zip and vnwo‑ai‑moderated‑community‑example‑pack.zip return 403, so no starter pack can be downloaded.
Accessibility	3	Pages use semantic headings and skip links, and the Accessibility statement outlines policies. However, there is no live keyboard and screen‑reader testing evidence, and default focus states may be hidden by sticky menus on mobile.
Mobile usability	2	The site is responsive, but the header’s “More” menu can become cramped at 320 px and may not remain entirely within the viewport. Long lists and dense text require excessive scrolling on small screens.
Performance	3	The pages are largely static with minimal JavaScript, but large hero images and numerous icons increase initial load. Blocked resources (403) still cause unnecessary network requests.
Trust and maintainership	2	Maintainer information is buried; the contact page is unfinished. There is no clear editorial process or maintainer identity beyond generic references.
Machine‑readable parity	2	Machine‑readable files exist but use schema version 2.7.1 and are inconsistent with page versions. Many referenced schemas cannot be retrieved due to 403.
SEO/discoverability	3	Titles and headings are clear, but canonical tags are not visible in the text‑only view. The outdated machine‑readable files and blocked downloads reduce search utility.
WordPress maintainability	3	The site uses a custom theme with semantic HTML and no heavy frameworks, which aids maintainability. However, inconsistent versioning, unused download code, and leftover default posts indicate poor release hygiene.
Claim‑boundary discipline	4	Claim‑boundary language is thorough and repeated on nearly every page. However, the repetition crowds out other content and the machine‑readable claim‑boundaries.json still reports an older version.
C. Prioritized Findings
ID	Severity	Category	Verified evidence	User impact	Recommended change	Route/file/selector	Acceptance criteria	Effort	Regression risk
F1	P0	Deployment mismatch	Machine‑readable files list schema version 2.7.1, while pages claim v2.0.0–2.2.0 versions. No page or file shows v2.9.1.	Users cannot trust which version they are reading; maintainers cannot audit changes.	Ensure all pages and machine‑readable files reflect the same version (e.g. 2.9.2) and update schema_version, theme version strings and last_reviewed_utc fields.	All page templates, vnwo.json, open‑rules.json, claim‑boundaries.json, llms.txt, .uai files	All human‑readable pages display consistent v2.9.2; machine‑readable files list schema_version 2.9.2 and updated last_reviewed_utc; version history updated accordingly.	Medium	Medium
F2	P0	Inaccessible downloads	Markdown and PDF Charter downloads, and both ZIP packs, return HTTP 403. Schema files also return 403.	Users cannot obtain the starter governance pack or example; AI readers cannot access schemas; adoption stalls.	Fix file permissions or hosting configuration to allow public read access to /downloads/* and /schemas/*.json. Mirror key artifacts in /downloads/ with stable URLs.	Server configuration; downloads/ and schemas/ directories	Downloads (Markdown, PDF, ZIP packs) and schema JSONs can be fetched without authentication; return correct content types and sizes.	Medium	Low
F3	P0	Unfinished contact page	The Contact page still contains the default WordPress post (“Welcome to WordPress. This is your first post…”) and no contact information.	Destroys credibility; users cannot report issues or request corrections; accessibility feedback path is broken.	Replace placeholder content with a clear contact method (e‑mail, web form or issue tracker) and instructions on what to send; remove default blog post.	contact/ WordPress page	Contact page displays maintainers’ preferred channel (e.g. e‑mail address or link to GitHub) and no default WordPress content.	Low	Low
F4	P1	Missing example pack	The AI‑moderated community example is advertised, but only a JSON descriptor is available; the ZIP is blocked.	Implementers cannot see a working example of how templates, governance change logs and .uai files fit together.	Create and publish a complete example pack with the files listed in the JSON descriptor (actor-disclosure.md, moderation-authority.md, etc.), including filled‑out templates, .uai records, and README explaining context.	Example pack directory and ZIP; examples/ai-moderated-community-example-pack.zip	Download yields a ZIP containing all referenced files, with consistent versioning; README explains how to use them.	High	Medium
F5	P1	Starter pack absent	The starter governance pack cannot be downloaded due to 403 errors.	Builders are unable to bootstrap their own governance files; adoption stalls.	Provide a vnwo-starter-governance-pack.zip containing blank templates, machine‑readable schemas, README, version file and claim‑boundary notes; ensure accessible link.	downloads/vnwo-starter-governance-pack.zip	Downloadable ZIP exists; contains all required templates and machine‑readable files; README explains usage; accessible without login.	High	Medium
F6	P1	Navigation label confusion	Primary navigation includes Start Here, Open Rules, Templates, Charter, File Memory, Exit Rights and others, but many link to overlapping or redundant content.	Users may not understand the difference between Charter and Open Rules or between Open Rules and Templates; cognitive load increases.	Rationalize navigation: use a single Guidance hub with tabs for Charter, Templates, Examples, and Machine‑Readable Files; rename Start Here to Overview or similar; ensure each link provides unique value.	header navigation menu	Updated nav labels reflect user mental model; no redundant pages; testing shows users find needed routes within two clicks.	Medium	Medium
F7	P1	Filter reliance on JavaScript	The template library page uses filters for categories such as charter, disclosure, memory, etc.. Without JavaScript the lists remain visible (progressive enhancement), but there is no accessible announcement or grouping.	Keyboard and screen‑reader users may not know that filtering is available; long lists require excessive scrolling on mobile.	Implement accessible filter controls with ARIA live regions announcing the number of templates found; provide a skip‑to‑templates link; collapse categories into accordions that work without JavaScript.	templates/ page; filter controls	Filters announce changes via aria‑live; template count updates; categories collapsible; works without JS; keyboard users can quickly navigate.	Medium	Medium
F8	P1	Inconsistent template version and machine‑readable pairing	There is no easy way to move from a human‑readable template to its machine‑readable schema or example; many templates lack explicit version, maturity, variables, and related schema information.	Users cannot ensure they are using the latest template or know how to validate their adaptation; AI systems cannot map text to JSON fields.	Add a panel to each template with: version, maturity (draft/recommended/deprecated), last‑reviewed date, editable variables, related schema, and machine‑readable equivalent. Provide links to JSON schema (once accessible) and example.	Each template page and open-rules.json entries	Each template lists version, maturity, variables and a link to the matching JSON schema; machine‑readable JSON includes same metadata; parity matrix passes.	High	Medium
F9	P1	Excessive claim‑boundary repetition	Almost every page ends with multiple paragraphs restating that VNWO does not certify safety, import files, or grant legal status.	The constant defensive copy pushes important guidance below the fold and may annoy readers.	Consolidate claim boundaries in a single banner or footnote at the start and end of each page with a collapsible summary and a link to the full claim‑boundary page.	Global footer or header component	Claim‑boundary notes appear once per page in a compact component; readers can expand for full text; repeated paragraphs removed.	Medium	Low
F10	P1	Outdated .uai memory and release metadata	The version history mentions updating .uai files and release memory, but there is no publicly viewable .uai state or documentation; implementers cannot see how to track changes.	Without release metadata, builders cannot replicate the theme update process or maintain their own governance state.	Publish .uai release files within the starter pack; document how to update them when pages change; include a diff viewer or instructions to diff .uai states across versions.	Starter pack; builder-checklist/, version-history/	.uai files are included in starter pack; documentation explains update process; version history links to .uai diff or instructions.	Medium	Medium
F11	P2	Heavy text and cognitive load	Many pages present large blocks of text without summaries; e.g., Start Here and Open Rules pages list all seven principles and template descriptions sequentially.	Users may become fatigued; they may not find the key action (download) quickly.	Provide bullet‑point summaries at the top; use collapsible sections or accordions; highlight the primary call‑to‑action such as “Download Starter Pack” near the top.	All high‑level pages (home, Start Here, Open Rules)	Each page begins with a concise summary and clear call‑to‑action; longer sections collapsible; readability tests show improved comprehension.	Medium	Low
F12	P2	Incomplete accessibility testing	The Accessibility page promises WCAG 2.2 AA compliance but acknowledges the need for live testing; there is no evidence of tested results.	Without testing evidence, users with disabilities cannot know whether the site truly works; hidden issues may persist (e.g., skip link not functioning, focus trapped in modals).	Add an accessibility testing report summarizing results of automated scans (e.g., axe‑core, Lighthouse) and manual screen‑reader tests; include known issues and planned fixes.	/accessibility/ page; release documentation	Accessibility page lists test results and outstanding issues; includes version and date; updated each release.	Medium	Low
F13	P2	Semantic hierarchy inconsistencies	Some pages use multiple H1 headings or skip heading levels. For example, the Start Here page includes repeated H2s after a collapsed anchor list.	Screen readers may misinterpret structure; search engines may not extract proper outline.	Audit templates to ensure one H1 per page, H2–H4 hierarchy reflecting content structure, and descriptive landmarks; add role attributes for nav and main.	All templates; header and footer	Pages contain one H1; headings follow sequential order; landmarks (nav, main, footer) are present; manual audit passes.	Medium	Low
F14	P2	Dense navigation menu on mobile	At 320 px, the header shows many links and a “More” dropdown. Labels wrap and the menu may extend off the viewport; focus may not return correctly when closing drawers.	Users on small screens may struggle to access deeper links; focus may be lost, harming keyboard users.	Collapse the top navigation into a hamburger menu on small viewports; ensure the menu is scrollable inside, with ARIA labels and focus management; provide skip‑to‑nav link.	Header component; responsive CSS/JS	At 320 px the nav collapses to a single menu button; the menu opens as a drawer with internal scroll; Escape and outside click close it; focus returns to trigger.	Medium	Medium
F15	P2	Missing maintainer and editorial process information	The site references a “maintainer” but no names, roles, or review cadence are provided; the contact page is vague.	Users cannot evaluate trustworthiness or report issues; adoption suffers.	Publish a Maintainers page or section listing names or roles, affiliation, review cadence, and method for raising issues; link it in the footer.	New about/maintainers/ page; footer	Maintainer list published; includes review cadence, contact method, and editorial guidelines; link in footer and machine‑readable files.	Low	Low
F16	P2	Poor internal linking to machine‑readable files	Many pages mention vnwo.json and llms.txt but bury the links at the bottom; some call‑to‑actions do not open the file due to 403.	AI readers may not find the correct file; human users may not know where to obtain machine‑readable guidance.	Place vnwo.json, open-rules.json, and claim-boundaries.json links near the top of the Machine‑Readable Governance page and cross‑link from templates; ensure links work.	/machine-readable-governance/ page and templates	Machine‑readable file links appear in the introduction; clicking them downloads or displays JSON; cross‑links from templates.	Low	Low
F17	P3	Redundant ecosystem descriptions	The Ecosystem page repeats lane descriptions that are already on other pages.	Adds cognitive load; pushes important guidance further down.	Summarize each lane in one sentence and link to the relevant site; hide additional text behind collapsible details.	ecosystem/ page	Lane descriptions condensed into summary bullets with optional expansion; page length reduced; readability improved.	Low	Low
F18	P3	No indicator of version differences across pages	Some pages show theme version 2.0.0 while others show 2.9.0.	Users cannot know which sections were updated and which are outdated.	Add a small banner or note on each page indicating when it was last reviewed and linking to the version history; highlight pages needing updates.	All templates	Each page displays last‑reviewed date and a link to version history; pages updated in the latest release show a “current” badge; outdated pages flagged.	Medium	Low
D. Route‑by‑Route Review
Route	Intended job	Fulfills job?	Strongest element	Main problem	Next change	Evidence
/ (Home)	Quickly explain VNWO’s purpose and direct users to the right entry path.	Partially. The core law and principles are visible and there are role‑based cards, but heavy copy and multiple CTAs compete for attention.	Role‑based “I run a community / I build AI agents” entry points.	No clear download link or summary; claim‑boundary notes repeated; long hero pushes content down.	Add a concise summary with a single “Get Started / Download Starter Pack” CTA; trim repeated claim‑boundary copy; highlight version number.	
/start-here/	Provide a plain‑language introduction and direct users to the first appropriate page.	Mostly. It outlines what VNWO is and the seven principles, but lacks a starter‑pack link.	Step‑by‑step explanation of the core law and principles.	Dense text and multiple nested sections; theme version 2.1.0 indicates outdated content; no quick link to downloads.	Summarize each principle; include a “Download Starter Pack” or “See Example” section; update theme version and machine‑readable metadata.	
/open-rules/	Serve as the template hub and explain rule surfaces.	Partially. Templates are listed with descriptions, but there is no accessible machine‑readable pairing and filter controls rely on JavaScript.	Clear explanation of rule surfaces and purpose.	Filter lacks accessibility and no download of machine‑readable schema; old theme version.	Add accessible filters; include version, maturity, variables and schema links for each template; provide “Download all templates” pack.	
/templates/	(Alias of open-rules?) Provide template library.	Yes – duplicates open‑rules content.	None—redundant.	Duplicate page increases maintenance cost and confuses users.	Redirect /templates/ to /open-rules/ or merge content.	
/machine-readable-governance/	Orient AI readers and link to JSON, schemas and examples.	No. It lists files but many links return 403 and there is no parity matrix.	Clear statement that files are for inspection rather than enforcement.	Files cannot be downloaded; no explanation of version differences; long list of schema names without accessible content.	Fix permissions; add parity matrix comparing human and machine artifacts; show example of converting a template to JSON.	
/file-memory/	Define file‑memory governance and link to UAIX.	Yes regarding principles; no regarding examples.	Clear list of memory rules and dispositions.	Example pack missing; heavy copy; no link to actual .uai schema; theme version 2.0.0.	Provide a downloadable file‑memory template pack; compress bullet lists; update version metadata.	
/agent-disclosure/	Define actor categories and required disclosures.	Yes. The page lists categories (human, assisted, bot, etc.) with definitions and prohibited overclaims.	Comprehensive taxonomy.	Very long list without summary; no machine‑readable counterpart; theme version 2.0.0.	Summarize categories in a table; provide JSON schema for actor profile; add link to machine‑readable file.	
/repair-and-appeals/	Provide repair and appeal guidelines with template.	Mostly. The process and issue types are well defined.	Clear step‑by‑step process and remedy taxonomy.	Download template not accessible due to 403; page is long and may intimidate; theme version 2.8.0 but machine‑readable pack missing.	Provide downloadable repair request template in the starter pack; summarise issue types; update machine‑readable and version metadata.	
/exit-rights/	Explain exit rights and portability.	Partially. Principles are listed but with little guidance on implementation.	Concise bullet list of exit components.	No example or template; no machine‑readable file; short page compared to others; theme version 2.0.0.	Include an exit‑rights template and JSON schema; link to starter pack; align content with more recent pages.	
/claim-boundaries/	Provide canonical allowed and prohibited claims.	Yes. The page lists allowed claims, prohibited claims, and safer replacements.	Detailed safer replacement suggestions and risk analysis.	Page duplicates claim‑boundary content present across the site; there is no direct link to machine‑readable version (403).	Consolidate claim boundaries in one place; fix link to claim-boundaries.json; provide copy‑safe text snippet for reuse.	
/contact/	Provide a feedback path.	No. The page is unfinished and displays default WordPress content.	None.	There is no contact information; default post undermines trust.	Replace with a functional contact method; include guidelines on what to report; ensure accessible form or e‑mail.	
/version-history/	Present changelog with claim‑boundary and machine‑readable impact.	Partially. Version 2.2.0 is documented, but there is no entry for 2.9.1.	Detailed description of changes and claim‑boundary impact.	Outdated; does not match current release; no machine‑readable update; long page with small font.	Add entries for v2.9.0–2.9.2; summarise changes; link to diff of machine‑readable files.	
/privacy/	State data‑collection and cookie policies.	Mostly. The page clearly states what VNWO collects and does not collect.	Transparent description of what is not collected.	Doesn’t mention analytics or monitoring script details; still references unfinished contact path; theme version 2.2.0.	Confirm absence of third‑party scripts; update last reviewed date; link to accessibility and claim‑boundary pages; fix contact link.	
/accessibility/	Describe accessibility goals.	Yes, as a statement of intent.	Acknowledges need for manual testing.	No test results; no link to accessible feedback; theme version 2.2.0.	Publish an accessibility audit; update contact details; include list of known issues; ensure skip link works.	
E. Exact Copy Recommendations
Current wording	Proposed wording	Reason	Affected route	Claim‑boundary check
“Welcome to WordPress. This is your first post. Edit or delete it, then start writing!”	Contact us: To send feedback on VNWO guidance, report an error, request a correction, or suggest improvements, please email [maintainer@example.com] or open an issue on GitHub. Do not include private files or sensitive data.	Remove default WordPress placeholder and provide a real contact path; clarifies not to send sensitive data.	/contact/	Complies with claim boundaries by not implying runtime support.
“Open rules Theme v2.1.0 …” (and similar version strings across pages)	“Theme v2.9.2 • last reviewed UTC: 2026‑06‑18 • static guidance only”	Align version numbers across pages; uses UTC date; maintains “static guidance” boundary.	All pages (footer or metadata line)	Notes static guidance; does not imply certification.
Repeated paragraphs: “VNWO is not a government, certification body, safety proof…” at the end of many pages	Replace with a compact banner: Claim boundary: VNWO publishes static civic guidance for virtual networks. It is not a government, certification authority, runtime agent, file importer, legal advisor, or compliance guarantor. Learn more.	Reduces repetition; still communicates boundaries; links to detailed page.	All pages (footer)	Contains required boundaries; avoids overclaiming.
“VNWO provides static governance guidance and templates. It is not certification, legal advice, or runtime enforcement.” in example JSON	“VNWO publishes static civic guidance and templates. It does not certify safety, provide legal advice, run AI agents, or guarantee compliance.”	Clarify “static civic guidance” and match claim‑boundary language; emphasise not to guarantee compliance.	examples/ai-moderated-community-example.json and other machine‑readable files	Maintains boundaries; clarifies no enforcement.
F. Recommended Release Scope (v2.9.2)

Release objective: Make VNWO.com a trustworthy, downloadable adoption toolkit by aligning versions, repairing broken downloads, and improving navigation and contact paths.

Implementation Items (max 8)
Version and metadata update – Update all page templates, machine‑readable files (vnwo.json, open‑rules.json, claim‑boundaries.json, llms.txt), and .uai state files to version 2.9.2 with current UTC timestamps. Update the version history page accordingly.
Fix download and schema permissions – Configure hosting to allow public read access for /downloads/* and /schemas/*.json. Ensure the Markdown charter, PDF charter, starter governance pack and example pack download correctly.
Populate starter pack and example pack – Create a vnwo-starter-governance-pack.zip containing blank templates (charter, disclosure, memory policy, repair template, exit packet), machine‑readable schema files, .uai release memory, README, license, and claim‑boundary note. Create vnwo-ai-moderated-community-example-pack.zip containing the filled‑out templates described in the JSON example and .uai records. Provide stable download links.
Finish Contact page – Replace placeholder content with a plain‑HTML contact method (e.g., mailto link or link to an issues repository). Add instructions not to send private data.
Navigation and labeling overhaul – Merge /templates/ into /open-rules/ or redirect; rename Start Here to Overview; group open rules, charter and templates under Guidance; shorten top nav for mobile; implement responsive hamburger menu with accessible drawer.
Template metadata panels – Add metadata panels to each template (version, maturity, editable variables, related schema, machine‑readable link). Implement accessible filter controls with ARIA live regions.
Compact claim‑boundary banner – Create a reusable component that displays a concise claim‑boundary message with a link to the full page; replace repeated paragraphs across pages. Add this component to all templates and posts.
Accessibility and testing documentation – Conduct a basic accessibility audit (e.g., using axe‑core and manual keyboard tests). Publish the results and known issues on the Accessibility page. Add instructions for sending accessibility feedback via the Contact page.
v3.0 Backlog
Readiness assessment tool: Provide a checklist or wizard that guides implementers through publishing a VNWO charter, templates, machine‑readable files, and .uai state, with validation for missing elements.
Client‑side pack generator: A simple browser‑based form to populate variables in templates and download a customized starter pack without server processing.
Template variable editor: An in‑browser editor that lists editable variables, ensures correct naming and substitution, and updates the machine‑readable version.
Schema validator: Provide a JavaScript module or online validator that checks JSON examples against VNWO schemas and reports errors.
Claim‑boundary linter: A tool that scans text for prohibited claims and suggests safer replacements based on claim‑boundary rules.
Version‑diff viewer: Publish diff files showing changes between versions of machine‑readable files and templates to aid reviewers.
Implementation gallery: Showcase real or sample governance implementations using VNWO (anonymized if necessary) to inspire adopters.
Framework crosswalks: Provide guidance on integrating VNWO with other governance frameworks (e.g., UAIX, Teleodynamic) without conflating roles.
G. QA and Evidence Plan
Static page and file audit
For each route listed in the review prompt, issue a curl or browser request to verify HTTP status 200 and correct content type.
Confirm that each page displays Theme v2.9.2 and correct last reviewed UTC date.
Check that vnwo.json, open-rules.json, claim-boundaries.json, llms.txt and each schema JSON can be downloaded via curl without 403.
Verify that the starter and example ZIP files download successfully and unzip without errors. Check that they contain the expected files.
Version parity matrix
Build a matrix of human‑readable pages vs machine‑readable files using the updated metadata panels; verify that each template has a matching schema and example.
Use a JSON validator to ensure example files conform to their schemas.
Navigation and responsive tests
Test the site at viewports 1440×900, 1024×768, 390×844, and 320×568 using the computer tool. Ensure no horizontal scroll on pages.
Open the new hamburger menu; check that it stays within the viewport, is scrollable, and can be closed with Escape or clicking outside. Verify focus returns to the menu button.
Accessibility checks
Run automated scans (e.g., axe-core via browser extension or command‑line) on at least the home, Start Here, Open Rules, File Memory, and Templates pages. Document violations.
Manually check skip link operation, heading hierarchy, button vs link semantics, keyboard order, visible focus, and reduced‑motion queries.
Use a screen reader to navigate menus, copy buttons, filter controls, and modals. Record issues.
Performance test
Use Lighthouse on mobile and desktop to capture performance metrics (First Contentful Paint, Total Blocking Time, Largest Contentful Paint). Ensure static resources are properly cached and images are compressed.
Security and privacy check
Verify that no third‑party analytics or tracking scripts have been added inadvertently. Confirm the site does not set non‑essential cookies for unauthenticated users.

Testing should occur on staging before deployment and then again on production after release. Use the same test scripts for regression in future releases.

H. Implementation Handoff

Target version: v2.9.2

Release objective: Align the VNWO site and machine‑readable files to a consistent version, repair all broken downloads, provide usable starter and example packs, improve navigation and claim‑boundary presentation, and publish accessibility test results.

Work items (ordered):

Update version constants and metadata
Files/routes: global functions.php or equivalent theme file; each page template; vnwo.json, open-rules.json, claim-boundaries.json, llms.txt, .uai files.
Replace existing version strings with 2.9.2 and update last_reviewed_utc with the current UTC timestamp (2026‑06‑18). Ensure schema_version matches across files.
Blocker: none.
Resolve download and schema permissions
Investigate server or CDN configuration that returns HTTP 403 for files in /downloads/ and /schemas/ directories. Adjust .htaccess or server rules to allow public read access and correct content types.
Blocker: server configuration access.
Package creation and upload
Assemble vnwo-starter-governance-pack.zip with blank templates, .uai release memory, README and claim-boundary note. Assemble vnwo-ai-moderated-community-example-pack.zip with the example files described in the JSON. Use deterministic ZIP creation to ensure reproducible checksums.
Upload both packs to /downloads/ directory.
Blocker: copywriting and file generation for example pack.
Contact page completion
Edit the Contact WordPress page content: remove default post; insert a contact email or link to an issue tracker; instruct users not to send sensitive data.
Ensure the page uses semantic HTML and accessible form fields if implementing a form.
Navigation overhaul
Consolidate guidance pages under a single menu item (e.g., Guidance). Redirect /templates/ to /open-rules/. Rename Start Here to Overview. Implement a responsive hamburger menu with ARIA labels and keyboard interaction.
Update header templates and CSS accordingly.
Template metadata and filters
Add metadata panels to each template page. Modify open-rules.json entries to include version, maturity, editable variables and related schema. Update the template filtering UI to use accessible controls and announce filter results via ARIA live region.
Write documentation on adding new templates with metadata.
Compact claim‑boundary component
Create a reusable component for pages and posts that displays a concise claim‑boundary statement with a link to /claim-boundaries/. Replace repeated paragraphs at the end of each page.
Test for responsive layout and keyboard accessibility.
Accessibility audit publication
Run automated and manual accessibility tests. Summarize results and publish them on the /accessibility/ page. Add a note that the audit will be updated every release and invite feedback via the Contact page.

Required automated checks:

Unit test verifying that all JSON files contain schema_version: 2.9.2 and last_reviewed_utc within ±1 day of release.
Integration test to fetch each file in /downloads/ and /schemas/ and assert HTTP 200 and correct MIME type.
Lint test ensuring each template page includes a metadata panel and the compact claim‑boundary component.
E2E test for navigation: open site at 320 px, open hamburger menu, navigate to at least three pages via keyboard, close menu, verify focus return.

Required manual checks:

Visual check of each page at 320 px and 1440 px to ensure no horizontal scroll and that the header and claim‑boundary component render correctly.
Manual screen‑reader test for the navigation menu, filter controls, and copy buttons.
Download and inspect starter and example packs; verify they contain expected files and that README is clear.

Deliverables:

Updated theme files and machine‑readable JSONs.
Starter and example ZIP packs.
Updated contact page and navigation menu.
Accessibility audit report.

Unresolved questions:

Does the team have access to server configuration to resolve 403 errors? If not, a hosting support ticket is required.
Who will maintain the example pack and update it with future releases? A named maintainer must be assigned.
Are there any legal constraints around publishing real governance examples that need anonymization?