Skip to content
aiWikis.org

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 or LLMWikis.org. 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. AIWikis applies both as a working implementation and records what actually happened.

Current

  • File-backed Markdown pages render public AIWikis content without WordPress Page seeding.
  • The /uaix/ and /llmwikis/ 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 and LLMWikis.org 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.

Next

  • Deploy the refreshed package artifacts before expecting live https://aiwikis.org to expose the local /uaix/, /llmwikis/, /files/, /concepts/, /reports/, /intake-outcome-ledger/, and /roadmap/ route truth.
  • Make the generated source-system pages easier to scan by adding short route-level summaries for UAIX public content, UAIX UAI system files, LLMWikis public content, LLMWikis UAI system files, global files, concepts, and reports.
  • Keep AIWikis source-file pages synchronized after UAIX AI Memory Wizard changes so the generated pages show current protocol outputs without turning AIWikis into the authority.
  • 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 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