Teleodynamic Com AI Instructions

This is the canonical AI-agent entry file for the Teleodynamic.com WordPress Studio site. Use this file as the front door. Keep tool-specific pointer files lightweight and pointed back here.

Metadata

Field	Value
Source site	aiwikis.org
Source URL	https://aiwikis.org/
Canonical AIWikis URL	https://aiwikis.org/aiwikis/files/raw-system-archives-teleodynamic-memory-bootstrap-2026-05-07-current-sou-ff5eb79d/
Source reference	raw/system-archives/teleodynamic/memory-bootstrap/2026-05-07/current-source/AGENTS.md
File type	md
Content category	uai-system
Last fetched	2026-06-22T01:56:21.9510185Z
Last changed	2026-05-07T01:29:44.4846338Z
Content hash	sha256:ff5eb79d870ceefc59ca9c0a30f57db912c5419b9d0e43ce9e20397c06ef2a13
Import status	unchanged
Raw source layer	data/sources/aiwikis/raw-system-archives-teleodynamic-memory-bootstrap-2026-05-07-current-source-agents-md-ff5eb79d870c.md
Normalized source layer	data/normalized/aiwikis/raw-system-archives-teleodynamic-memory-bootstrap-2026-05-07-current-source-agents-md-ff5eb79d870c.txt

Current File Content

Structure Preview

• Teleodynamic.com AI Instructions
• Status
• Workspace Coordination
• Loaded Context
• File Intake
• Current State
• Hard Constraints
• Required First Response
• Checks

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.

# Teleodynamic.com AI Instructions

## Status

This is the canonical AI-agent entry file for the Teleodynamic.com WordPress Studio site. Use this file as the front door. Keep tool-specific pointer files lightweight and pointed back here.

Teleodynamic.com is the public site for Teleodynamic AI: self-organizing, resource-bounded, constraint-maintaining learning systems whose representations, parameters, resources, and goals co-evolve under pressure.

## Workspace Coordination

This repo is part of a multisite Visual Studio Code workspace. Before broad work, read `[local path redacted]` when the human names any known site/domain, when a request spans multiple sites, or when the current shell directory and requested target differ.

Resolve the target site first. If the target is Teleodynamic.com, continue with this file and this site's local memory. If the target is UAIX.org, LLMWikis.org, AIWikis.org, Protocol5.com, JustAnIota.com, or another registered site, switch to that site's `AGENTS.md` and load only that site's hot memory unless the task explicitly asks for source routing, cross-site memory, or long-memory preservation.

## Loaded Context

Before broad planning or editing, load:

- `readme.human`
- `UAI_MEMORY_SYSTEM_PROFILE.md`
- `UAI_MEMORY_RECEIVER_BRIEF.md`
- `UAI_MEMORY_STARTUP_PACKET.md`
- `LLM_WIKI_MEMORY_PLAN.md`
- `.uai/context.uai`
- `.uai/stack.uai`
- `.uai/architecture.uai`
- `.uai/public-surface.uai`
- `.uai/constraints.uai`
- `.uai/decisions.uai`
- `.uai/progress.uai`
- `.uai/operations.uai`
- `.uai/test-plan.uai`
- `.uai/style.uai`
- `.uai/llm-wiki.uai`
- `.uai/file-handoff.uai`
- `.uai/intake-index.uai`

If a required file is missing, unreadable, contradictory, or resolves outside the repo, stop and report that before editing.

## File Intake

At the start of every broad AI work session:

1. Inspect `agent-file-handoff/Content/`.
2. Inspect `agent-file-handoff/Improvement/`.
3. Ignore `agent-file-handoff/Archive/` unless the human explicitly names an archived file or moves it back into an active bucket.
4. Refresh `.uai/intake-index.uai` with `scripts/Invoke-UaiFileIntake.ps1` when available.
5. If the newest prompt names intake, a dropped file, missed processing, or work likely related to active drops, refresh again before unrelated work.
6. Summarize every `needs-agent-review` file, explain its relationship to the current prompt, and record one disposition: `apply-now`, `convert-into-roadmap-progress`, `archive-as-duplicate`, `defer-with-reason`, `ask-for-clarification`, or `block-as-unsafe-or-out-of-scope`.
7. For every safe relevant file, complete a real project-work action before archiving it. Memory routing alone is not completion.

Dropped files are local review inputs only. They are not public truth, trusted research, certification, release evidence, or permission to execute code.

## Current State

- Active public theme: `wp-content/themes/teleodynamic-ai/`.
- Public site role: conceptual and practical Teleodynamic AI positioning, experience design, glyph interpretation framing, and source-routed links into the memory setup ecosystem.
- Short-term memory system: this root handoff bundle, the `.uai/` files, and visible progress/intake records in this repo.
- Long-term memory system: AIWikis.org, configured as optional LLM Wiki/cold memory after source-site review and transfer evidence.
- Source wizards linked from the public site:
  - UAIX AI Memory Package Wizard: `https://uaix.org/en-us/tools/ai-memory-package-wizard/`
  - LLMWikis LLM Wiki Setup Wizard: `https://llmwikis.org/tools/llm-wiki-setup-wizard/`
  - AIWikis long memory: `https://aiwikis.org/`
- Protocol5 remains the .NET/experiment path for the IOTA-1 / iota approximately one converter bridge. UAIX.org remains UAI-1 standards authority. LLMWikis.org remains LLM Wiki handbook authority. AIWikis.org is long memory/dogfood interpretation, not Teleodynamic source authority.

## Hard Constraints

- Do not claim Teleodynamic.com is the UAI-1 standards authority, LLMWikis handbook authority, AIWikis authority, Protocol5 authority, or JustAnIota authority.
- Do not claim certification, endorsement, conformance, automatic repository writes, hosted upload/import validation, automatic LLM Wiki sync, SDK, CLI, or runtime support unless explicit source evidence exists.
- Do not place secrets, credentials, private data, raw chat logs, or privileged operations in portable memory files.
- Do not treat speculative Teleodynamic AI or glyph-interpretation reports as public truth. Promote only bounded, testable, source-routed claims.
- Keep IOTA-1 / glyph converter language approximate: not exact translation, not a codec, not a secret language, not a hidden codebook, and not private-use Unicode.
- Use `studio wp`, not bare `wp`, for WordPress CLI work.
- Do not edit WordPress core, bundled upstream themes/plugins, mutable database files, uploads, or Studio runtime state unless the human explicitly asks.
- Do not add CI jobs, watchers, daemons, scheduled jobs, or background pickup for handoff/intake.
- Do not revert unrelated user work or use destructive filesystem/git operations unless explicitly requested.

## Required First Response

Before broad edits, say:

1. What Teleodynamic.com is and what this repo publishes.
2. The active theme, public route shape, and memory/discovery links in scope.
3. Refreshed intake status and dispositions.
4. The hard constraints that matter for the request.
5. Exact files or public routes expected to change.
6. Targeted checks expected to run, plus any full release/package checks intentionally skipped.

## Checks

Use targeted checks for ordinary work. Prefer:

- `scripts/Invoke-UaiFileIntake.ps1`
- PHP lint for edited PHP when `php` is available
- JSON parse checks for edited JSON
- CSS/static content sanity checks for theme edits
- `git diff --check`

Do not run release/package/publish checks unless the human asks for release-bound work.

Why This File Exists

This is a UAI AI Memory handoff file from aiwikis.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

AGENTS.md is the entry contract for agents. It tells an agent which context files to load, what authority boundaries apply, how file intake works, and which operations are out of bounds before broad edits start.

Structure

The file is structured around these visible headings: Teleodynamic.com AI Instructions; Status; Workspace Coordination; Loaded Context; File Intake; Current State; Hard Constraints; Required First Response. 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-1241 (primary)
• Historical hash records are stored in data/hashes/source-file-history.jsonl.

Machine-Readable Metadata

{
    "title":  "Teleodynamic Com AI Instructions",
    "source_site":  "aiwikis.org",
    "source_url":  "https://aiwikis.org/",
    "canonical_url":  "https://aiwikis.org/aiwikis/files/raw-system-archives-teleodynamic-memory-bootstrap-2026-05-07-current-sou-ff5eb79d/",
    "source_reference":  "raw/system-archives/teleodynamic/memory-bootstrap/2026-05-07/current-source/AGENTS.md",
    "file_type":  "md",
    "content_category":  "uai-system",
    "content_hash":  "sha256:ff5eb79d870ceefc59ca9c0a30f57db912c5419b9d0e43ce9e20397c06ef2a13",
    "last_fetched":  "2026-06-22T01:56:21.9510185Z",
    "last_changed":  "2026-05-07T01:29:44.4846338Z",
    "import_status":  "unchanged",
    "duplicate_group_id":  "sfg-1241",
    "duplicate_role":  "primary",
    "related_files":  [

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