All runbooks
rulesuai-explorerAgent-only

UAI Explorer Agent Instructions

Synced UAI Explorer rules documentation from AGENTS.md.

Updated 2026-06-21·Freshness: Agent·Sensitive tokens or credentials were hidden before display.

UAI Explorer Agent Instructions

Before changing UAI Explorer, read:

  • START_HERE_AI.md
  • START_HERE_UAI_LAB.md
  • UAI_EXPLORER_RULES.md
  • [REDACTED:high-entropy].md
  • docs/runbooks/ai-lanes-mcp-adapter.md
  • docs/runbooks/uai-development-standards.md
  • [REDACTED:high-entropy].md
  • [REDACTED:high-entropy].md
  • docs/runbooks/sandbox-protocol.md
  • docs/runbooks/public-safe-access.md
  • docs/plans/explorer-2.0-ux-blueprint.md
  • docs/plans/explorer-2.0-redaction-embedding-lanes.md
  • docs/qa/qa-qc-qol-gates.md
  • Latest entry in docs/diary/
  • For UI/UX changes, use the local uai-uiux-designer plugin standards at C:\Users\scott\plugins\uai-uiux-designer.

Working rules:

  • Treat production CT 121 as governed internal production. It runs public-safe UAI Explorer 0.2.3.
  • Use CT 126 as the staging and verification lane for exploratory work, destructive tests, rollback rehearsal, and content-pipeline experiments.
  • Do not expose public routes, DNS, TLS, firewall, reverse proxy, or NetBird changes without a separate approved exposure runbook.
  • Do not write secrets into code, docs, diaries, logs, tickets, tests, screenshots, or evidence. The only prompt exception is a short-lived UAI_EXPLORER_AI_API_KEY issued for a role=ai user; do not persist it.
  • Update the diary for meaningful work sessions.
  • Add or update a runbook before repeating an operational workflow.
  • Keep human UX and AI context APIs separate.
  • Fresh AI agents should authenticate as role=ai, call /api/ai/bootstrap, then fetch required context through /api/ai/context/{slug}.
  • AI agents should use AI lanes whenever possible. Direct repo access is only for explicit local code, documentation, or verification work.
  • Optional product-scoped agent feedback goes through /api/ai/feedback; no feedback means the current lane works as-is.
  • Keep navigation grouped by user mode: human work, AI surface, and admin ops.
  • Treat MCP servers and local AI adapters as bounded AI clients. They may use only /api/ai/bootstrap, /api/ai/catalog, /api/ai/context/{slug}, plus health/readiness unless a separate private-lane runbook explicitly grants more authority.
  • Do not leave important UAI documentation local-only. Catalog it in Explorer, or mark it draft, review, private, or superseded with a clear reason.
  • Historical migration-ready docs remain useful lineage, but current operating truth starts with the finish status, production cutover evidence, and final decision evidence.