UAPI GLM 5.2 Builder And First Wedge Runbook
GLM 5.2-owned Interpreter first-wedge, Conductor/Foundry gateway, and demo acceptance tasks.
Promotion Metadata
- Source feedback id:
81 - Source feedback ids:
81 - Promotion request id:
16 - Feedback category:
consider - Feedback source:
ai-lane - Feedback created at:
2026-06-22T16:31:04.567308+00:00 - Target slug:
[REDACTED:high-entropy] - Review state:
review - Reviewer note: AI lane auto-promoted redacted feedback into internal catalog context.
Source Feedback Body
Feedback 81
- Product:
uapi - Category:
consider - Related slug:
[REDACTED:high-entropy] - Source:
ai-lane - Created at:
2026-06-22T16:31:04.567308+00:00
title: UAPI GLM 5.2 Builder And First Wedge Runbook project: uapi kind: runbook state: review tags: [docs, runbook, uapi, glm52, interpreter, conductor, foundry] source_plan_title: UAPI Integrated Operating Plan v2
UAPI GLM 5.2 Builder And First Wedge Runbook
Owner: GLM 5.2. Mission: turn the Interpreter-first operating image into a builder plan that is demonstrable, gated, and compatible with Codex schemas and Grok routing evidence.
Access contract: Endpoint: http://10.0.0.121:8080. Token: set UAI_EXPLORER_AI_API_KEY out of band. Header uses Bearer token from that variable. Never print secrets. Fetch master program control, the main integrated UAPI plan, and the ChatGPT Interpreter First Wedge operating image context before work.
First-wedge behavior: - Interpreter should feel like an operator-facing work surface: understand intent, ask for missing constraints, draft JobBrief, show planned route, show gates, and produce auditable results. - Cadence remains Front Desk/PA behavior where applicable; Conductor/Future Foundry is the factory/gateway behavior. Do not collapse these into one vague agent. - The first wedge must run with mock adapters before real adapters, then graduate only by passing gates.
Deliverables: 1. Interpreter state machine: intake, clarify, plan, gate, dispatch, observe, summarize, archive. 2. Adapter matrix: mock, Explorer, UAPI, Conductor/Foundry, embedding lane, hardware route, cloud route. 3. Gate design: what requires operator approval, what is read-only, what is allowed in sandbox, what must never run without explicit authorization. 4. Demo acceptance: a small operator request becomes JobBrief, PlacementDecision, RunRecord, ResultPacket, and Explorer-visible evidence. 5. Mock-vs-real transition checklist with rollback and no-secret logging.
Coordination rules: use Codex contract names exactly once published; do not invent incompatible schema names. Use Grok route names only after hardware verification. Flag contradictions in Explorer feedback instead of silently choosing.
GLM diary fields: scenario tested, adapter mode, gates encountered, schema dependencies, route assumptions, demo evidence, blocker, next step.
GLM prompt starter: You are GLM 5.2 for UAPI Interpreter/Conductor first wedge. Use Explorer source of truth, fetch required contexts, design builder behavior and demo gates, keep mock and real adapters clearly separated, and publish diary/results without secrets.