Roadmap

Roadmap is a machine-readable memory-file source record exposed by AIWikis.org with provenance, content hash, bounded public preview, and source-boundary metadata.

Metadata

Field	Value
Source site	uaix.org
Source URL	https://uaix.org/
Canonical AIWikis URL	https://aiwikis.org/uaix/files/raw-system-archives-uaix-recent-work-sweep-2026-05-03-wp-content-plugins-f7af79e1/
Source reference	raw/system-archives/uaix/recent-work-sweep/2026-05-03/wp-content/plugins/uaix-core/data/uai-1/roadmap.json
File type	json
Content category	memory-file
Last fetched	2026-06-22T01:56:21.9510185Z
Last changed	2026-05-02T19:20:42.5187665Z
Content hash	sha256:f7af79e10f70a993b0113b486abe4e687cbef7066f2f52bfa610409c0cb9ceb4
Import status	unchanged
Raw source layer	data/sources/uaix/raw-system-archives-uaix-recent-work-sweep-2026-05-03-wp-content-plugins-uaix-core-data-uai-1-ro-f7af79e10f70.json
Normalized source layer	data/normalized/uaix/raw-system-archives-uaix-recent-work-sweep-2026-05-03-wp-content-plugins-uaix-core-data-uai-1-ro-f7af79e10f70.txt

Current File Content

Structure Preview

• No Markdown headings were detected in this file.

Raw Version

This public page shows a bounded preview of a large source file. The complete source remains in the raw and normalized source layers named in metadata, with the SHA-256 hash above for verification.

• Source characters: 33201
• Preview characters: 11929

{
  "kind": "uaix.roadmap.v1",
  "standard_family": "UAI",
  "current_release": "UAI-1",
  "uai_version": "1.0",
  "release_date": "2026-04-25",
  "description": "Forward roadmap for the public UAI-1 launch surface, today-focus orientation, roadmap documentation ledger, interoperability evidence, bridge evidence examples, compact-transfer discipline, conformance fixture evidence, conformance maturity, AI Memory starter and wizard outputs, project-context handoff, active file intake, agentic-system evidence boundaries, evidence-discipline guidance, and developer handoff work.",
  "status_labels": [
    {
      "label": "current",
      "meaning": "Published on the public site or machine-facing route today."
    },
    {
      "label": "next",
      "meaning": "Launch-hardening work that should happen before broad public push."
    },
    {
      "label": "planned",
      "meaning": "Adopted future work that needs more fixtures, tooling, or governance before it becomes a public claim."
    },
    {
      "label": "research-track",
      "meaning": "Useful input that is not a current launch commitment."
    }
  ],
  "today_focus": [
    {
      "id": "authority-orientation",
      "status": "current",
      "question": "What should a new reader understand first?",
      "action": "Start with UAI-1 and Standards Fit, then use the roadmap before repeating broad claims about runtime fit, bridge profiles, SDKs, CLIs, adapters, certification, endorsement, or sync.",
      "verify": [
        "/en-us/specification/uai-1/",
        "/en-us/specification/standards-fit/",
        "/en-us/roadmap/",
        "/wp-json/uaix/v1/roadmap"
      ],
      "boundary": "UAIX is the UAI-1 authority and portable evidence layer, not an agent runtime, scheduler, SDK, CLI, adapter program, certification body, or replacement for adjacent protocols."
    },
    {
      "id": "first-proof-run",
      "status": "current",
      "question": "How should an implementer produce one useful proof today?",
      "action": "Choose one public profile, validate one packet, keep the result beside the Adoption Kit or Conformance Pack, and cite the changelog before treating the work as public support.",
      "verify": [
        "/en-us/tools/validator/",
        "/en-us/tools/adoption-kit/",
        "/en-us/tools/conformance-pack/",
        "/en-us/governance/changelog/"
      ],
      "boundary": "One passing validator result is packet evidence, not certification, endorsement, compliance, or ecosystem-wide support."
    },
    {
      "id": "ai-memory-package-work",
      "status": "current",
      "question": "What AI Memory work is useful and supportable today?",
      "action": "Use the AI Memory Package Wizard to produce generated local files, package model JSON, manifest overlay JSON, visitor-AI digest output, copy-paste decks, optional LLM Wiki plan output, and canonical starter ZIP links.",
      "verify": [
        "/en-us/ai-memory/",
        "/en-us/tools/ai-memory-package-wizard/",
        "/en-us/specification/project-handoff/",
        "/wp-json/uaix/v1/roadmap"
      ],
      "boundary": "Managed package records, hosted upload/import validation, automatic repository writes, automatic LLM Wiki sync, SDKs, CLIs, certification, and endorsement remain unsupported until public evidence exists."
    },
    {
      "id": "agentic-system-evidence",
      "status": "planned",
      "question": "How should agentic-system integration move forward?",
      "action": "Keep runtime execution, tools, approvals, tracing, interruptions, orchestration, and managed memory with the chosen runtime while UAIX records portable UAI-1 evidence, Project Handoff memory, and release records that survive the run.",
      "verify": [
        "/en-us/specification/standards-fit/",
        "/en-us/specification/project-handoff/",
        "/en-us/guides/project-handoff-openai/",
        "/en-us/roadmap/"
      ],
      "boundary": "Trace exporters, local redaction lint, reference adapters, and runtime-specific exporters stay planned or research-track until fixtures, owners, and release evidence exist."
    }
  ],
  "documentation_ledger": [
    {
      "id": "document-roadmap-work",
      "status": "current",
      "title": "Document roadmap work where readers can verify it",
      "summary": "Roadmap-changing work should update the public Roadmap, roadmap REST payload, canonical roadmap doc, focused tests, and compact handoff state together.",
      "records": [
        "/en-us/roadmap/",
        "/wp-json/uaix/v1/roadmap",
        "docs/roadmap.md",
        "scripts/test-uaix-ai-memory-bundle.php",
        "AGENTS.md",
        "readme.human",
        ".uai/progress.uai"
      ],
      "evidence_rule": "A roadmap statement becomes reusable current-support language only when public page copy, matching machine artifact, reproducible evidence, implementation or package proof when needed, and dated release trail agree.",
      "boundary": "Private chat, screenshots, archive folders, and unpromoted reports are not public roadmap truth by themselves."
    },
    {
      "id": "keep-source-leads-bounded",
      "status": "current",
      "title": "Keep intake files and reports as source leads until promoted",
      "summary": "Active intake, Reports, and AIWikis cold memory can inform roadmap work, but their conclusions are source input until promoted into current UAIX records.",
      "records": [
        "agent-file-handoff/Content/",
        "agent-file-handoff/Improvement/",
        ".uai/intake-index.uai",
        "/en-us/reports/",
        "AIWikis raw/system-archives/2026-05-01-uaix-internal-memory-reorg.json"
      ],
      "evidence_rule": "Useful source facts become UAIX truth only when restated in current docs, public pages, machine artifacts, tests, release notes, roadmap state, or handoff records.",
      "boundary": "Indexing, archiving, or preserving source material is not approval, certification, endorsement, validator evidence, conformance evidence, or permission to widen support claims."
    },
    {
      "id": "name-missing-proof",
      "status": "current",
      "title": "Name missing proof before support language moves",
      "summary": "If a claim lacks a public page, machine artifact, reproducible fixture or check, implementation/package proof when needed, or release trail, keep it next, planned, or research-track.",
      "records": [
        "evidence_promotion_gates",
        "support_claim_checks",
        "/en-us/governance/launch-readiness/",
        "/en-us/governance/changelog/"
      ],
      "evidence_rule": "Missing proof should be named in roadmap language instead of hidden behind broad support wording.",
      "boundary": "Adapters, trace exporters, hosted imports, automatic repository writes, automatic sync, SDKs, CLIs, certification, and endorsement remain unsupported until the missing proof is public."
    },
    {
      "id": "future-agent-pickup",
      "status": "current",
      "title": "Make future agent pickup deterministic",
      "summary": "Future agents should start from AGENTS.md, readme.human, loaded .uai files, refreshed active intake, docs/roadmap.md, and the roadmap REST payload before changing support language.",
      "records": [
        "AGENTS.md",
        "readme.human",
        ".uai/context.uai",
        ".uai/public-surface.uai",
        ".uai/decisions.uai",
        ".uai/progress.uai",
        "/wp-json/uaix/v1/roadmap"
      ],
      "evidence_rule": "Project truth changes should update the roadmap, machine payload, tests, changelog or release notes, and handoff state together.",
      "boundary": "Future agents should not create competing instruction files, recurring live-site dependencies, CI pickup, watchers, scheduled jobs, or background handoff automation."
    }
  ],
  "current_work_queue": [
    {
      "id": "deploy-current-artifacts",
      "status": "next",
      "title": "Deploy current packages and root assets",
      "summary": "Upload or apply the freshly generated 2026-05-02 publish artifacts, then verify production static-root headers, HSTS, discovery files, and well-known manifests against the launch host.",
      "evidence_needed": [
        "deployed uaix-core.zip containing the well-known public-page URL normalization patch",
        "deployed prod-fallback-root-assets with robots, sitemap, favicon, well-known files, and production .htaccess or edge equivalent",
        "production response-surface check passing for public pages, REST routes, robots, sitemap, well-known manifests, HSTS, and static-root security headers"
      ]
    },
    {
      "id": "serializer-parity",
      "status": "next",
      "title": "Prove AI Memory Package Wizard serializer parity",
      "summary": "Show that one set of wizard selections produces equivalent generated local files, copy-paste decks, overlay JSON, visitor-AI digest summaries, and canonical ZIP references.",
      "evidence_needed": [
        "focused wizard regression fixtures",
        "stale-review and changed-selection warnings before export",
        "matching generated system profile, receiver brief, startup packet, optional LLM Wiki plan, overlay JSON, digest, and ZIP reference evidence"
      ]
    },
    {
      "id": "local-validation-redaction",
      "status": "planned",
      "title": "Plan local validation and redaction lint",
      "summary": "Define local package validation and redaction checks that help teams review AI Memory and Project Handoff files without implying hosted upload/import validation or automatic repository writes.",
      "evidence_needed": [
        "public fixtures for allowed and blocked handoff content",
        "documented redaction and source-authority rules",
        "release notes that keep local lint separate from certification, endorsement, SDK, or CLI claims"
      ]
    },
    {
      "id": "trace-to-handoff-fixtures",
      "status": "planned",
      "title": "Design trace-to-handoff evidence fixtures",
      "summary": "Map selected runtime traces, tool calls, approvals, task status, and handoff summaries into UAI-1 records or Project Handoff files only after public examples, review gates, and redaction rules exist.",
      "evidence_needed": [
        "sample runtime-to-UAI evidence packets",
        "redacted trace identifier and approval posture examples",
        "validator expectations or handoff checks that preserve the runtime boundary"
      ]
    },
    {
      "id": "reference-adapter-evaluation",
      "status": "research-track",
      "title": "Evaluate reference adapters after evidence exists",
      "summary": "Study OpenAI, A2A, MCP, and runtime-harness adapter patterns as evidence exporters, not as UAIX-owned execution, orchestration, or official vendor-adapter support.",
      "evidence_needed": [
        "adapter scope statements that leave execution with the runtime",
        "fixture-backed export examples",
        "maintenance ownership before any adapter leaves research-track status"
      ]
    }
  ],
  "evidence_promotion_gates": [
    {
      "gate": "public-page-update",
      "required_before_current": "The current-support wording appears on the relevant UAIX public page with support boundaries and route links."
    },
    {
      "gate": "machine-artifact-update",
      "required_before_current": "The matching JSON, schema, registry, roadmap, discovery, package, or conformance artifact exposes the same state."
    },
    {
      "gate": "fixture-or-validator-evidence",
      "required_before_current": "Examples, fixtures, validator expectations, package checks, or handoff lint make the behavior reproducible."
    },
    {
      "gate": "implementation-or-package-evidence",
      "required_before_current": "A named implementation track, starter package, conformance packet, or release artifact carries the proof."
    },
    {
      "gate": "dated-release-trail",

Why This File Exists

This is a memory-system evidence file from uaix.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 has no Markdown headings, so its path, frontmatter, file type, and provenance metadata carry most of the retrieval meaning.

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-1200 (primary)
• Historical hash records are stored in data/hashes/source-file-history.jsonl.

Machine-Readable Metadata

{
    "title":  "Roadmap",
    "source_site":  "uaix.org",
    "source_url":  "https://uaix.org/",
    "canonical_url":  "https://aiwikis.org/uaix/files/raw-system-archives-uaix-recent-work-sweep-2026-05-03-wp-content-plugins-f7af79e1/",
    "source_reference":  "raw/system-archives/uaix/recent-work-sweep/2026-05-03/wp-content/plugins/uaix-core/data/uai-1/roadmap.json",
    "file_type":  "json",
    "content_category":  "memory-file",
    "content_hash":  "sha256:f7af79e10f70a993b0113b486abe4e687cbef7066f2f52bfa610409c0cb9ceb4",
    "last_fetched":  "2026-06-22T01:56:21.9510185Z",
    "last_changed":  "2026-05-02T19:20:42.5187665Z",
    "import_status":  "unchanged",
    "duplicate_group_id":  "sfg-1200",
    "duplicate_role":  "primary",
    "related_files":  [

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