References and Contributors

Purpose

This page gathers the most important public UAIX links in one place and serves as the current attribution, discovery, and contributor handoff record for the public site.

Important public links

• Home for the public directory and institutional summary.
• Get Started for the first implementation-oriented reading path.
• About for mission, scope, standards posture, and practical use cases.
• UAI-1 for the current normative specification.
• Schemas for machine-readable definitions.
• Registry for stable identifiers and profile handles.
• Examples for readable exchanges and fixtures.
• Implementations for the main implementation tracks.
• WordPress Publication Track and .NET Bridge Track for current publication and runtime implementation tracks.
• Tools and Validator for discovery, inspection, and validation workflows.
• Governance and Changelog for policy, revision discipline, and release history.
• Press and News for public-facing language, assets, and release notes.

Implementation reading path

1. Start on Get Started for the adoption overview.
2. Read UAI-1 for the current normative message model.
3. Pair Schemas with Registry so field rules and profile identifiers stay aligned.
4. Review Examples and run the Validator before calling an exchange conformant.
5. Choose a publication or runtime path from Implementations.

[uaix_public_operating_layer context=”references”][uaix_handoff_packet context=”references”]

Minimum public handoff packet

• The clean canonical page path and page-level record code for the affected public record.
• The relevant schema, registry entry, example fixture, validator result, or implementation-track artifact.
• A short compatibility note stating whether the change is additive, corrective, policy-oriented, or breaking.
• The matching discovery, sitemap, changelog, and news links when outside readers need to verify the current public state.

Discovery and citation links

When citing a UAIX document, prefer the exact page path and the page-level record code shown in the document header.

• /.well-known/uaix.json as the preferred machine-readable discovery manifest.
• /.well-known/uai.json as the shorter standards-family alias.
• /sitemap.xml and /robots.txt as root discovery and crawl references.
• /sitemap.html, /en-us/sitemap.xml, and /en-us/sitemap.html as mirrored human-readable and locale-aware discovery surfaces for public QA.

Citation checklist

1. Name the site accurately: UAIX for the website and standards venue, UAI for the standard family, and UAI-1 for the current normative specification.
2. Link to the clean locale-prefixed page path rather than a query-string URL.
3. Include the page-level record code from the document header when citing a specific public page.
4. Use the discovery manifest or sitemap when automation needs to resolve the current public page inventory.
5. Use the changelog for compatibility posture and news for the public-readable release narrative.

Concrete public artifacts and endpoints

The current public record includes both human-readable pages and machine-facing routes that outside reviewers can inspect directly.

• Human-facing validator surface: Validator is the current browser-facing workbench for fixture review and conformance exports.
• Machine-facing route family: /wp-json/uaix/v1/catalog, /wp-json/uaix/v1/discovery, /wp-json/uaix/v1/status, /wp-json/uaix/v1/modules, /wp-json/uaix/v1/schemas, /wp-json/uaix/v1/registry, and /wp-json/uaix/v1/examples expose the current catalog, discovery, and record inventory.
• Machine validation route: /wp-json/uaix/v1/validate is the machine-facing JSON POST validator endpoint; treat it as automation infrastructure rather than a browsable report page.
• Current packaged artifact family: uaix-authority-theme-v2.8.0.zip is the active public launch theme, uaix-theme-v2.8.0.zip remains the packaged compatibility theme, uaix-core-v2.8.0.zip carries the core REST and standards runtime surface, uaix-modules-v2.8.0.zip carries the redistributable module pack, uaix-bridge-v2.8.0.zip carries the WordPress-to-.NET reference bridge, uaix-locale-router-v3.0.0.zip carries locale-prefixed routing, and uaix-seo-sweep-v2.8.0.zip carries canonical SEO, clean URL redirects, sitemaps, robots, and discovery-manifest delivery.

Current published ownership state

Current published attribution on this public site: Michael Kappel

This record will expand as additional editors, reviewers, implementers, and partner organizations are formally added to the published UAIX site. Until broader roles are published, use this page as the durable attribution and handoff record rather than assuming private organizational structure.

Current published operating roles

• Published attribution: Michael Joseph Kappel, MCP is the current named public attribution on the site.
• Current public ownership layer: UAIX currently publishes one named attribution plus record-level governance, discovery, validator, and implementation evidence rather than a broader public roster.
• Decision trail: when the public standard changes, the current decision record should appear on the affected canonical pages, the release trail, and the machine-readable record where relevant rather than in unpublished side channels.

Do not assume a separate public GitHub repository, issue tracker, or community forum unless it is linked from this page or another canonical UAIX page.

Current contributor intake workflow

1. Identify the affected record family and link its clean canonical page path.
2. Note the relevant record code, schema, registry entry, example fixture, validator evidence, or implementation-track artifact that the request touches.
3. Describe the expected effect as additive, corrective, policy-oriented, or breaking before asking downstream readers to treat the change as current truth.
4. Use Governance, the Changelog, and News as the public release trail when the work affects compatibility or public interpretation.
5. Keep citation, discovery, and attribution links attached to the change request so public review does not depend on private context.

What a public review packet should include

• The exact canonical page path and record code for every affected public record.
• The proposed change type and a short migration note for downstream readers.
• Linked schema, registry, example, validator, discovery, and implementation evidence when the request affects technical behavior.
• The changelog and news links needed to show how the clarification or release entered the public record.

Current public policy status

• Privacy: use Privacy and Data for the current published posture on public reading, discovery, and data-exposure changes. Pair it with Policy and Security and the release trail when a privacy-relevant change needs dated evidence.
• Accessibility: use Accessibility for the current launch expectations around real text, keyboard reachability, readable code examples, and mobile-safe layouts. Treat the page as the current public statement rather than inferring a larger certification or office program.
• Analytics and telemetry: use Analytics for the current published limits on measurement, telemetry-significant release work, and disclosure posture. Do not infer advertising, cross-site profiling, or a broader consent workflow that the site has not explicitly published.
• Hub and release discipline: use Policy and Security for the cross-cutting hub, licensing posture, and security-significant release expectations that sit beside these dedicated pages.

Current review and contact path

UAIX now publishes the Contact and Review route as the direct public maintainer contact path. For contributor-facing changes, citation questions, implementation review, or release-linked clarifications, use Contact and Review, Governance, the Changelog, and News together.

• Link the exact page path and record code for the affected public record.
• Attach validator or implementation evidence when the request affects conformance claims.
• Use the discovery manifest, sitemap, and canonical page paths instead of screenshots or query-string links when sharing the current public state.
• Do not imply broader partner, maintainer, issue-tracker, or contributor-queue structure beyond what is explicitly published here.
• A broader public contributor workflow remains planned work; when it is formally published, this page should point to it directly.