Workspace Guidance

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

Metadata

Field	Value
Source site	llmwikis.org
Source URL	https://llmwikis.org/
Canonical AIWikis URL	https://aiwikis.org/llmwikis/files/uai-workspace-guidance-uai-293ab82a/
Source reference	.uai/workspace-guidance.uai
File type	uai
Content category	uai-system
Last fetched	2026-06-22T01:56:21.9510185Z
Last changed	2026-06-13T15:41:11.6738364Z
Content hash	sha256:293ab82aaf007c67402361745ef709d9ade64e9bfbf9d05247e9f74d7138d5df
Import status	unchanged
Raw source layer	data/sources/llmwikis/uai-workspace-guidance-uai-293ab82aaf00.uai
Normalized source layer	data/normalized/llmwikis/uai-workspace-guidance-uai-293ab82aaf00.txt

Current File Content

Structure Preview

• Workspace Guidance
• Canonical Memory Rule
• Legacy Memory Cleanup Rule
• Talisman Ecosystem Routing
• UAIX And LLM Wiki Wizard Alignment

Raw Version

Local absolute paths are redacted in this public view. The source hash and source-side raw layer are based on the unredacted source file.

---
uai: "1.0"
type: workspace-guidance
project: "LLMWikis.org"
created: "2026-05-26"
updated: "2026-05-31"
status: active
workspace: "[local path redacted]"
long_memory_destination: "https://AIWikis.org/llmwikis/"
---

# Workspace Guidance

This site is part of the `[local path redacted]` multisite WordPress workspace. Read `[local path redacted]` when target routing is ambiguous, then this site's `AGENTS.md`, `.uai/readme.human`, and focused typed `.uai/*.uai` records.

## Canonical Memory Rule

- The durable local AI memory root is `.uai/`.
- Do not create a separate memory directory, wiki folder, or scattered Markdown notes for default project memory.
- The full Project Handoff suite should include `.uai/context.uai`, `.uai/stack.uai`, `.uai/architecture.uai`, `.uai/constraints.uai`, `.uai/progress.uai`, `.uai/operations.uai`, `.uai/test-plan.uai`, `.uai/style.uai`, `.uai/coding-standards.uai`, `.uai/decisions.uai`, `.uai/memory.uai`, `.uai/short-term-memory.uai`, and `.uai/long-term-memory.uai`.
- `.uai/file-handoff.uai` is used when Agent File Handoff is enabled.
- For code-capable setup, create or verify `.uai/coding-standards.uai` before broad code work. Reflect on the target codebase's good parts, preserve DRY and once-and-only-once ownership, apply SOLID defaults, and require automated testing for every language or framework.

## Legacy Memory Cleanup Rule

If an old memory folder, wiki-memory folder, or stray Markdown handoff note already exists, do not leave it as confusing code debt. Review it, move current working facts into `.uai/short-term-memory.uai` or the right typed `.uai/*.uai` record, preserve durable reviewed facts in the long-term wiki/AIWikis namespace at `https://AIWikis.org/llmwikis/` or in `.uai/archives/` evidence, record what moved, then remove or clearly retire the mistaken path.

LLM Wiki and AIWikis records are optional long-memory/cold-memory destinations after source-site review. They do not replace this local `.uai/` suite, and they are not proof of current production deployment.

## Talisman Ecosystem Routing

- UAIX.org owns the official uaix-talisman-client and uaix-talisman-ecosystem-manager specifications, guidance, public documentation, package documentation, validators, package behavior, standards-alignment work, and official WordPress, PHP, .NET, and Python plugin/package lines, including plugin/package development and plugin/package distribution.
- Teleodynamic.com is the Talisman and philosophical fulcrum for this ecosystem; client sites should point active Talisman receiver/fulcrum configuration at Teleodynamic.com unless a human explicitly names a bounded exception.
- UAIX.org may install Talisman tooling for development and dogfood, but that does not make UAIX.org the ecosystem Talisman.
- Dogfood findings flow back into UAIX-owned tooling/docs/tests and into Teleodynamic.com when philosophy, claim boundaries, life-centered posture, trust posture, or Talisman assumptions need repair.
- Client sync, talkback, receipts, packets, and telemetry are proposal/request/evidence surfaces only and do not mutate protected anchors or certify alignment without human-reviewed evidence.

## UAIX And LLM Wiki Wizard Alignment

- Read .uai/wiki-wizard-alignment.uai when setting up, repairing, or updating this .uai package or its long-memory wiki route.
- UAIX.org AI Memory Package Wizard defines the local package/setup/File Handoff behavior; LLMWikis.org Setup Wizard defines wiki topology and ingest/review behavior.
- Reviewed long memory for this project routes to https://AIWikis.org/llmwikis/.

Why This File Exists

This is a UAI AI Memory handoff file from llmwikis.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 workspace-guidance 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: Workspace Guidance; Canonical Memory Rule; Legacy Memory Cleanup Rule; Talisman Ecosystem Routing; UAIX And LLM Wiki Wizard Alignment. 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-210 (primary)
• Historical hash records are stored in data/hashes/source-file-history.jsonl.

Machine-Readable Metadata

{
    "title":  "Workspace Guidance",
    "source_site":  "llmwikis.org",
    "source_url":  "https://llmwikis.org/",
    "canonical_url":  "https://aiwikis.org/llmwikis/files/uai-workspace-guidance-uai-293ab82a/",
    "source_reference":  ".uai/workspace-guidance.uai",
    "file_type":  "uai",
    "content_category":  "uai-system",
    "content_hash":  "sha256:293ab82aaf007c67402361745ef709d9ade64e9bfbf9d05247e9f74d7138d5df",
    "last_fetched":  "2026-06-22T01:56:21.9510185Z",
    "last_changed":  "2026-06-13T15:41:11.6738364Z",
    "import_status":  "unchanged",
    "duplicate_group_id":  "sfg-210",
    "duplicate_role":  "primary",
    "related_files":  [

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