Roadmap

AIWikis.org is the public dogfood site for source-governed AI memory. This roadmap turns changelog entries, lessons, recommendation adjustments, source-sync evidence, and handoff state into a practical work queue.

AIWikis does not replace UAIX.org, LLMWikis.org, Protocol5.com, or ɩ.com / JustAnIota.com. UAIX.org remains canonical for UAI-1, AI Memory, Project Handoff, Agent File Handoff, validator, conformance, and support boundaries. LLMWikis.org remains the handbook source for LLM Wiki structure and governance. Protocol5.com remains the Protocol5 parent brand and UAI .NET implementation package source. ɩ.com / JustAnIota.com remains the compact-message tooling, public-site identity, and implementation-memory source. AIWikis applies and preserves source memory from all four without absorbing their authority.

Current

• File-backed Markdown pages render public AIWikis content without WordPress Page seeding.
• The public structure now starts from task routes: /start-here/, /search/, /topics/, /source-map/, /files/, /reports/, /contact/, and /browser/.
• The /search/ route searches packaged route records, aliases, tags, descriptions, source metadata, and bounded previews without depending on WordPress Page seeding.
• Home, Start Here, and AIWikis Memory and Site Structure now explain the public page, generated evidence, source-side wiki, and raw archive layers before readers hit dense file lists.
• The /uaix/, /llmwikis/, /protocol5/, and /justaniota/ route split exposes public source summaries, UAI system files, demonstrations, provenance, global file indexes, concept pages, and reports.
• Transparent source-file sync preserves current source files under data/sources/, normalized comparison text under data/normalized/, and hash history under data/hashes/source-file-history.jsonl.
• The Intake Outcome Ledger records what happened to processed dropped files, what changed, what was deferred or blocked, and where reviewed documentation lives.
• The Deep Cognitive Archive separates public pages, compact .uai handoff packets, and slower source-side reasoning memory.
• The local Project Handoff export loop proves that selected reviewed wiki nodes and current .uai state can produce a compact handoff packet for release evidence.
• AIWikis tracks the UAIX AI Memory Package Wizard as a source-authority-preserving example of generated memory operating files: system profile, receiver brief, startup packet, overlay JSON, optional LLM Wiki memory plan, and protocol choices for source authority, evidence, conflict, risk, and rollback.
• Reviewed source memory guides for UAIX.org, LLMWikis.org, Protocol5.com, and ɩ.com / JustAnIota.com now explain what each source owns, how AIWikis preserves it, when to update it, and which authority or support claims remain out of scope.
• The Cross-Site Memory Atlas and Source Memory Operations Playbook now make authority routing, artifact ownership, evidence flow, archive consolidation, source sync, handoff export, and package-ready documentation maintenance explicit.
• The Memory Coverage Matrix and Claim Boundary Register now show which source domains are covered, partially covered, source-only, or blocked, and which claims AIWikis can safely make.
• Source-Site Outcome Routing now closes the gap between source-repository staged work and AIWikis public visibility: staged work remains staged until an explicit AIWikis routing pass records what changed.
• The 2026-05-01 source-site report preservation manifest now proves the original UAIX and LlmWikis processed archive files were copied into raw memory with checksums, rather than relying only on summaries or staged artifacts.
• The 2026-05-03 UAIX recent-work sweep now preserves current wizard setup URL, Agent File Handoff, optional LLM Wiki, roadmap, agentic-system, deploy-check, and processed-intake state with a 23-file checksum manifest.
• Generated source-file pages were refreshed after the UAIX recent-work sweep and now need to carry the JustAnIota source split so the local /uaix/, /llmwikis/, /protocol5/, /justaniota/, /files/, /concepts/, and report evidence views include the right source ownership.

Next

• Deploy the refreshed package artifacts before expecting live https://aiwikis.org to expose the local /uaix/, /llmwikis/, /protocol5/, /justaniota/, /files/, /concepts/, /reports/, /intake-outcome-ledger/, and /roadmap/ route truth.
• Review the staged LLMWikis integration package and decide which drafts should be promoted into LLMWikis public handbook pages, which should remain roadmap items, and which should stay blocked pending vendor/source verification.
• Run a live accessibility, Search Console, and Core Web Vitals pass after the refreshed package is deployed so public task routing and stale hash-route cleanup can be checked against production behavior.
• Keep generated AIWikis source-file pages synchronized after future UAIX, LLMWikis, Protocol5, or AIWikis source changes so evidence pages catch up without turning AIWikis into the authority.
• Keep AIWikis source-file pages synchronized after Protocol5 UAI .NET Hub changes so generated pages show current route contracts, package artifacts, compatibility mirrors, and authority boundaries without turning AIWikis into the Protocol5 source.
• Promote the UAIX wizard dogfood lesson into an AIWikis checklist for projects that combine compact UAI memory packets with optional LLM Wiki long memory.
• Tighten report pages so source-file inventory, changed files, duplicate resolution, generated explanations, broken links, and final content map are easier for humans to act on.
• Add a public-safe deployment-readiness note that distinguishes local package truth from live-site drift without exposing credentials or local paths.

Later

• Decide whether AIWikis should publish a downloadable public source manifest or keep source records exposed through pages, reports, and REST routes only.
• Decide whether the local Project Handoff export should remain release evidence or become a narrow public-safe download after source authority and support boundaries are reviewed.
• Expand graph-backed wiki nodes only after public page quality, source labels, and review boundaries stay stable under package checks.
• Evaluate whether some public pages should be generated from reviewed source-side wiki nodes, while keeping raw archives out of public HTML.
• Add dated child pages for large future intake outcomes if the rolling Intake Outcome Ledger becomes too dense.
• Create stronger live-route checks after deployment so local package truth, generated route inventory, discovery routes, and public pages stay aligned.

Blocked Or Out Of Scope

• No hosted upload/import validator until UAIX publishes public tooling, fixtures, and validation behavior for that support claim.
• No automatic repository writes or automatic LLM Wiki sync from AIWikis until source authority, review gates, privacy, rollback, and operator ownership are proven.
• No automatic AIWikis publication from source-site Improvement processing; cross-site staged outcomes need explicit routing, review, checks, and deployment.
• No claim that source-site report information is safely retained when only summaries or staged artifacts exist; raw original preservation needs a manifest with counts and checksums.
• No SDK, CLI, certification, endorsement, or UAIX conformance claim from AIWikis package generation or source-file display.
• No live deployment, DNS change, production overwrite, or WordPress admin assumption from this workspace.
• No raw archive publication unless material is converted into reviewed public summaries.

Promotion Rules

An item can move from later to next when it has a reviewed source, a named owner or trigger, a safe public boundary, and a targeted check.

An item can move from next to current when the local workspace has the source files, public page or package behavior, handoff state, and test evidence needed to make the claim true.

An item stays blocked when it would imply authority, automation, certification, deployment, or data exposure that AIWikis does not currently support.

Reading Path

• Start Here for the reader path.
• UAIX.org Source Memory Guide, LLMWikis.org Source Memory Guide, Protocol5.com Source Memory Guide, and JustAnIota Source Memory Guide for detailed source-system memory.
• Cross-Site Memory Atlas for source ownership, artifact ownership, evidence flow, and claim routing.
• Source Memory Operations Playbook for maintenance workflow.
• Source-Site Outcome Routing for the gap between source-site staged work and AIWikis public changes.
• Memory Coverage Matrix for coverage status and update triggers.
• Claim Boundary Register for safe, source-routed, dogfood, planned, and blocked claims.
• Source Map for source boundaries.
• Intake Outcome Ledger for recent dropped-file outcomes.
• Lessons Learned for implementation evidence.
• Recommendation Adjustments for accepted, proposed, rejected, and open recommendation changes.