Governance docs
evidenceuai-explorerredacted view

Documentation Governance Pass Evidence

Synced UAI Explorer evidence documentation from docs/evidence/documentation-governance-pass-2026-06-21.md.

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

Documentation Governance Pass Evidence

Date: 2026-06-21
Timezone: America/St_Johns

Scope

Performed a post-cutover content and rules pass for UAI Explorer after production CT 121 was cut over internally to public-safe 0.2.3.

This pass used three expert review lanes:

  • documentation governance and source-of-truth review,
  • AI lane and MCP adapter review,
  • lab access and operational boundary review.

No secrets, raw device files, raw survey folders, credentials, DNS/TLS routes, firewall settings, reverse-proxy settings, NetBird exposure, storage cleanup, or node onboarding changes were introduced by this documentation pass.

Changes Recorded

  • Updated current operating truth in START_HERE_AI.md and START_HERE_UAI_LAB.md.
  • Updated AGENTS.md with post-cutover production/sandbox rules.
  • Added [REDACTED:high-entropy].md.
  • Added docs/runbooks/ai-lanes-mcp-adapter.md.
  • Updated UAI_EXPLORER_RULES.md so UAI Explorer is the canonical documentation surface and local documents are caches, drafts, private material, or superseded lineage until cataloged.
  • Updated public-safe access guidance so external exposure remains a separate runbook and AI adapters are limited to bounded /api/ai/* access.
  • Marked pre-cutover planning and migration-ready documents as historical or superseded instead of deleting them.
  • Updated generated operator-decision evidence to support the no-open-decisions closed state.

Documentation Source Of Truth Rule

Explorer is the canonical documentation surface for UAI operational memory. Important local runbooks, plans, surveys, standards, evidence, and start-here files must be cataloged in Explorer or explicitly marked as draft, review, approved, published, superseded, or private.

Device-local start files are short safe caches that point back to Explorer. They are not the archive.

AI Lane Rule

MCP servers and local AI adapters are AI clients, not admin clients.

Allowed AI tools:

  • uai_ready
  • uai_list_ai_catalog
  • uai_get_ai_context
  • optional uai_search_ai_catalog

Denied surfaces:

  • raw filesystem paths,
  • admin APIs,
  • upload APIs,
  • generic HTTP proxying,
  • direct SQLite access,
  • direct DATA_ROOT reads,
  • .env, .ssh, raw-survey-zone, sanitized-exports, and device crawls.

Embeddings for AI-facing retrieval may use only packets retrievable through /api/ai/context/{slug} by an authorized AI account.

Current Boundaries

  • Production CT 121: public-safe 0.2.3, governed internal production.
  • Sandbox CT 126: public-safe 0.2.3, staging and verification lane.
  • Open UAI Explorer public-safe v1 decisions: 0.
  • External exposure: not changed and still requires a separate runbook.
  • Real raw content promotion: not performed; future work must use selected redaction, review, staging, and explicit catalog import.
  • Zenbook: closed for UAI Explorer documentation survey; future node work is separate infrastructure onboarding.

Result

The documentation system now reflects the desired model: Explorer is the source of truth, stale docs are lineage, AI lanes are bounded, production and sandbox roles are clear, and local-only documents are no longer acceptable as the long-term memory store.

The refreshed app/docs state was then synced to both CT 121 and CT 126 and verified with in-container tests and external health/readiness checks. Evidence: [REDACTED:high-entropy].md.

Repo-native Markdown docs were then synced into the Explorer catalog so the current documentation surface is reachable through Explorer. Evidence: [REDACTED:high-entropy].md.