Skip to content
Get Started Free

UAIX Agents Protocol

What this page is for

UAIX Agents Protocol is the public dogfood record for the UAIX-produced UAI-1 Project Handoff WordPress package. UAIX.org remains the source-of-truth producer and distribution surface for the package; LlmWikis.org, AIWikis.org, and other test sites should consume the UAIX-published ZIP rather than treating their local copies as canonical.

Current status

  • Package name: uai1-project-handoff-v2.8.0.zip.
  • WordPress plugin slug: uai1-project-handoff.
  • SHA-256: C3C5123975D283BC25C709151950746CCDED22C24BA9F68D4FF6718BD73EF405.
  • Status: experimental/internal prototype.
  • Evidence role: local dogfood and smoke-test evidence for Project Handoff packaging, .uai/readme.human, a fuller .uai handoff set, active file-intake buckets, and ignored archive scaffolding, not official UAIX generator, validator, SDK, CLI, certification, or endorsement support.

Dogfood finding

The AIWikis.org package build exposed a practical failure mode: a package can cite Project Handoff while omitting the active agent-file-handoff/ workspace or a complete enough .uai context set. Version 0.2.4 tightens the exporter and ZIP validator so package evidence checks the actual files, not only the public explanation.

What UAIX should prove with it

  • Generated manifests use the current UAI-1 uai.intent.request.v1 shape and pass UAIX Core validation when the Core validator is available.
  • Generated packages include .uai/readme.human, the loaded .uai handoff records for context, stack, architecture, constraints, decisions, progress, operations, test plan, style, sources, prompts, file handoff, and intake index, plus agent-file-handoff/Content/, agent-file-handoff/Improvement/, and agent-file-handoff/Archive/ scaffolding without visible README files inside those buckets.
  • Plugin-local validation behavior stays aligned with UAIX Core validator behavior or with bundled schema and registry fixtures.
  • apply_to_site refuses to run when manifest validation fails.
  • Imports apply ZIP size, file-count, unpacked-size, traversal, path allowlist, and executable-file checks before extraction or apply.
  • Cleanup jobs remove temporary extraction folders, expired upload records, and stale package working files.
  • Activation smoke output exists before WordPress compatibility is treated as proven for a release.

How to use it in UAIX release work

  1. Install and activate the UAIX-published versioned ZIP in the local Studio workspace.
  2. Export a Project Handoff package from current UAIX repository context.
  3. Validate the generated manifest through UAIX Core and keep the result with the test packet.
  4. Confirm the package includes .uai/readme.human, the expected loaded .uai files, active file-intake buckets, and the ignored archive folder, but does not publish raw dropped or archived files as public content.
  5. Try invalid packages and confirm apply_to_site refuses them before any site write occurs.
  6. Record the package hash, file count, preflight outcome, validator result, cleanup result, and activation smoke result before widening public language.

Current public boundary

  • This page publishes a downloadable experimental WordPress package for dogfood and test-site evaluation.
  • This page does not publish a public .uai generator, hosted upload validator, SDK, CLI, certification process, or endorsement program.
  • The plugin can support dogfood evidence only while the public roadmap, fixtures, validation behavior, release notes, and broader support evidence remain incomplete.
  • Reader-facing copy should continue to say experimental/internal prototype until public evidence says otherwise.

Related public records

  • Project Handoff is the practical AGENTS.md, .uai/readme.human, and .uai handoff pattern this prototype exercises.
  • Agent File Handoff explains the active local intake and archive workspace this prototype now exports.
  • Validator explains the public evidence posture for UAI-1 message validation.
  • Conformance Pack is the reusable public packet model this prototype should not overclaim as certification.
  • Launch Readiness is the go-live gate for package evidence, locale QA, and support-claim boundaries.
  • Roadmap and Changelog are the places to check before repeating future tooling or compatibility claims.

Smoke sequence

Use a small, repeatable local sequence when this prototype participates in a UAIX release check.

studio wp plugin install uai1-project-handoff-v2.8.0.zip --activate
studio wp plugin is-active uai1-project-handoff
# Validate generated manifests with UAIX Core before apply_to_site.
# Record ZIP preflight, refusal, cleanup, and activation smoke evidence.