UAIX Authoring Style

UAIX Authoring Style is a uai-system source file exposed by AIWikis.org with provenance, current content, and generated explanation.

Metadata

Field	Value
Source site	uaix.org
Source URL	https://uaix.org/
Canonical AIWikis URL	https://aiwikis.org/uaix/files/uai-style-uai-06c952bc/
Source reference	.uai/style.uai
File type	uai
Content category	uai-system
Last fetched	2026-06-22T01:56:21.9510185Z
Last changed	2026-06-11T02:42:38.1787557Z
Content hash	sha256:06c952bc0c95eaa4c037d5d3ee1d586e3319452314065a2956f3d74a537722d8
Import status	unchanged
Raw source layer	data/sources/uaix/uai-style-uai-06c952bc0c95.uai
Normalized source layer	data/normalized/uaix/uai-style-uai-06c952bc0c95.txt

Current File Content

Structure Preview

• UAIX Authoring Style
• Writing Style
• Documentation Style
• Public Copy Style
• Interface Style
• Editing Style
• AI Handoff Style

Raw Version

---
uaix: "1.0"
type: style
title: "UAIX Authoring Style"
created: "2026-04-25"
updated: "2026-05-01"
status: active
author: "UAIX maintainers"
version: 5
---

# UAIX Authoring Style

## Writing Style

- Prefer plain, direct, explicit language.
- Make support boundaries easy to understand.
- Separate current public truth from planned or future work.
- Use route paths, page names, and artifact names precisely.
- Write for both humans and AI readers.
- Say UAIX.org is the source of truth for UAI-1.
- Say Protocol5.com distributes .NET plugins and NuGet packages and links back to UAIX.org.
- Do not frame Protocol5.com as the standards site, canonical validator, canonical registry, or public UAI-1 documentation host.

## Documentation Style

- Start active docs with a clear title and `Updated:` line.
- State whether a doc is canonical, helper, background, or compatibility-only.
- Point helper docs back to canonical docs.
- Keep research notes labeled as background inputs unless adopted elsewhere.

## Public Copy Style

- Make entry paths obvious.
- Explain what a page is for, when to use it, and what it does not claim.
- Prefer concrete reading orders and proof paths over vague description.
- Avoid overselling maturity, coverage, or support.
- On high-entry pages, expose task paths before dense record inventories so newcomers can decide whether they are here to understand the standard, build an AI Memory package, validate a message, or inspect governance.

## Interface Style

- Keep public headings readable across English, zh-CN, French, and Spanish by using normal letter spacing; do not rely on negative tracking to create a compressed editorial look.
- Reserve expanded letter spacing for short uppercase labels, badges, and metadata where scanning improves.
- Do not waste large areas of available page real estate while nearby text is cramped, stacked, clipped, or forced into narrow columns. If a viewport has open horizontal or vertical space, use it to improve readability, density, scanning, or task flow.
- Avoid jumbled layouts where a heading, intro paragraph, step list, card grid, or tool control wraps aggressively beside empty space. Rebalance columns, grid tracks, max widths, and content order before accepting the layout.
- Hero and intro sections should earn their footprint. Do not leave large decorative voids between headline and supporting copy unless the space carries a useful visual, navigation choice, status summary, or interaction.
- Tool and wizard screens should keep controls compact and legible. Progress steps, buttons, fields, and help text should not sprawl into unused bands or compress into unreadable chips when the surrounding panel has available room.
- Visual assets should support the task and fit the layout. Do not let decorative art create dead space, push useful content below the fold, or compete with the primary reading or action path.
- Check desktop and mobile layouts for real-estate waste, awkward wrapping, clipped labels, oversized blank bands, and text squeezed beside unused space before finalizing a public UI change.

## Editing Style

- Use `rg` for search when possible.
- Use `apply_patch` for manual file edits.
- Prefer existing repo patterns over new abstractions.
- Keep changes closely scoped to the task.

## AI Handoff Style

- A good handoff file should be understandable by an AI with zero prior context.
- Loaded context should answer purpose, stack, constraints, architecture, public surface, operations, and current progress.
- Hard rules belong in `constraints.uai`, not only in chat.

Why This File Exists

This is a UAI AI Memory handoff 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 .uai file is a compact style packet. It keeps one kind of durable project truth separate from the rest of the archive so an agent can load the topic it needs without pulling the whole project history into prompt context.

Structure

The file is structured around these visible headings: UAIX Authoring Style; Writing Style; Documentation Style; Public Copy Style; Interface Style; Editing Style; AI Handoff Style. Those headings are retrieval anchors: a crawler or LLM can decide whether the file is relevant before reading every line.

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

Machine-Readable Metadata

{
    "title":  "UAIX Authoring Style",
    "source_site":  "uaix.org",
    "source_url":  "https://uaix.org/",
    "canonical_url":  "https://aiwikis.org/uaix/files/uai-style-uai-06c952bc/",
    "source_reference":  ".uai/style.uai",
    "file_type":  "uai",
    "content_category":  "uai-system",
    "content_hash":  "sha256:06c952bc0c95eaa4c037d5d3ee1d586e3319452314065a2956f3d74a537722d8",
    "last_fetched":  "2026-06-22T01:56:21.9510185Z",
    "last_changed":  "2026-06-11T02:42:38.1787557Z",
    "import_status":  "unchanged",
    "duplicate_group_id":  "sfg-039",
    "duplicate_role":  "primary",
    "related_files":  [

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