UAI Explorer AI Start Here
Explorer AI start-here. Public Explorer primary while CT121 down. Always fetch protocol/MOC/infra even if not in primary_context.
Body
UAI Explorer AI Start Here
Updated: 2026-07-15 (public primary + fetch-anyway honesty)
Binding contract (read first)
Ecosystem placement, wipe posture, authority layers, and sandbox lifecycle are defined by governance protocol vNext.
| Item | Full slug (fetch via GET /api/ai/context/{slug}) |
|---|---|
| Binding protocol | [REDACTED:high-entropy] |
| Start-here MOC | [REDACTED:high-entropy] |
| Infra map | [REDACTED:high-entropy] |
| Thaladex identity | uai-doc-ecosystem-product-uai-thaladex |
| Explorer↔Thaladex journey | [REDACTED:high-entropy] |
Do not rely on slug joins — use the full strings above.
Sandbox owner rule: CT123, CT124, CT126, and peer lab sandboxes are KEEP. Agents MUST stop sandboxes when done (free RAM). Agents MUST NOT destroy sandboxes or leave them idle-running.
This start-here remains valid for Explorer AI-lane mechanics. On conflict with vNext, vNext wins.
Explorer endpoint (2026-07-15 honesty)
| Surface | URL | Notes |
|---|---|---|
| Public (primary) | https://explorer.united-ai.ca |
Use this while lab CT121 is down |
| Lab CT121 | http://10.0.0.121:8080 |
Optional when Director returns; currently unreachable |
| Human page | https://explorer.united-ai.ca/agent |
Browser agent-access |
Repo entry START_HERE.md has the session PAT. Do not re-ask the owner for credentials already published there.
Bootstrap primary_context is a short list. Protocol, MOC, and infra map are required next fetches even when absent from that list.
Bootstrap required_rules may still mention CT121 production governance — treat public Explorer as the default AI lane while Director/CT121 is down; lab CT rules apply when lab is reachable.
Fresh agent bootstrap
- Ready probe: require ready, public_safe_mode, server-side redaction, no raw survey mount.
- Authenticate on the AI lane (API key as Bearer token, session-only; do not persist).
- Bootstrap; fetch primary_context entries marked accessible.
- Always fetch next: protocol vNext, start-here MOC, infra map, product-uai-thaladex, journey runbook (even if not in primary_context).
- Capability card before infra:
GET /api/ai/capability/product-thaladexfor memory work. - Complete the assigned Product / Task / Authority / Done when.
- Optional product-scoped feedback. Dedup first. No secrets.
Assignment shape:
Product: <lane>
Task: <outcome>
Authority: <plan only | local repo | sandbox | production read-only>
Done when: <acceptance>
Stop if AI-lane access is missing or rejected. Do not use admin, raw file, upload, SQLite, env files, ssh dirs, or public exposure surfaces without a separate owner-approved runbook.
Thaladex bridge (tokens)
| Lane | Token | Job |
|---|---|---|
| Explorer | uai_pat_… |
Rules, catalog, capability cards, feedback |
| Thaladex | thx_… |
remember / recall / layers |
Explorer PAT never authorizes Thaladex remember. Agents do not mint thx_ — human invite/console path (Beta 0.2). Public demo: https://thaladex.united-ai.ca · unauthenticated GET /v1/welcome-pack.
Safety (Explorer lane)
- Never write secrets into docs, logs, tickets, or evidence.
- AI context must be redacted, capped, audited.
- Explorer catalog is published SOT for operational docs; local files are caches/drafts/lineage until cataloged.
- Human UX and AI context APIs are different surfaces.
- Mac never hosts product runtimes.
AI lane rules
- Use AI endpoints or a narrow adapter only.
- Direct repo access only when the operator assigns local workspace work.
- Even then, use Explorer for current rules, stop lines, catalog state, and lab boundaries.
- AI output cannot approve infrastructure exposure, mark wipe complete, or sign owner stages.
Lineage note
Older text that describes only CT121/CT126 Explorer topology and pre-wipe survey state is lineage. Public Explorer is the cold-start default while Director is unresponsive. Read vNext + infra map for placement; read product-uai-thaladex + journey for memory onboarding.