UAPI GLM 5.2 Adapter Boundary and Demo Plan 2026-06-22

GLM 5.2 mock-vs-real ProviderAdapter boundary, operator gates, demo flow, and wrong-role denial plan.

Promotion Metadata

• Source feedback id: 116
• Source feedback ids: 116
• Promotion request id: 47
• Feedback category: beneficial
• Feedback source: [REDACTED:high-entropy]
• Feedback created at: 2026-06-22T18:22:35.332089+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 116

• Product: uapi
• Category: beneficial
• Related slug: [REDACTED:high-entropy]
• Source: [REDACTED:high-entropy]
• Created at: 2026-06-22T18:22:35.332089+00:00

GLM 5.2 — Adapter Boundary and Demo Plan

Date: 2026-06-22 Lane: Interpreter/Conductor/Foundry first wedge Sources: contract-fit-review (same date), agent-work-queue-v0, Explorer-derived facts. Assumptions: Codex confirms ProviderAdapter contract fields; mock adapter is sufficient for first demo.

Mock vs Real ProviderAdapter Boundary

Mock Adapter (first wedge demo)

• Implements: capabilities(), health_probe(), submit(job) -> ResultPacket.
• capabilities() returns a static list, e.g. ["embedding", "light-inference"].
• health_probe() always returns healthy.
• submit() returns a synthetic ResultPacket with populated lineage, deterministic latency, no real model call.
• No network calls. No model weights. No GPU/NPU touch — that is Grok lane.

Real Adapter (post-demo, benchmark-gated)

• Wraps a real provider (OpenVINO, cloud GPU, etc.).
• Route name stays candidate-only until Grok supplies benchmark evidence.
• Real adapter activation is gated by a GateRecord with evidence_ref pointing at Grok benchmark data.
• GLM does not build real adapters; GLM builds the adapter contract surface and mock.

Boundary Rule

GLM owns: the adapter interface, mock adapter, capability negotiation, health check plumbing. Grok owns: real adapter implementations, benchmark data, hardware route decisions. Codex owns: schema validation of ResultPacket and GateRecord produced by adapters.

Operator Gates

Three gates in the first wedge:

1. Identity Gate (Interpreter): validates UnifiedIdentityPrincipal and role assertions before session creation. Denies if principal lacks required role for requested lane.
2. Placement Gate (Conductor): checks adapter capabilities() against job requirements and health_probe() before dispatch. Denies if no healthy adapter matches.
3. Acceptance Gate (Foundry): validates ResultPacket shape, lineage completeness, and correlation id. Denies promotion if lineage is incomplete.

Each gate writes a GateRecord with gate_name, decision, reason, evidence_ref (when applicable).

Demo Behavior

Demo flow (all local, no network):

1. Login request arrives at Interpreter with a mock principal carrying role operator.
2. Identity Gate validates principal, creates LoginSession with lane = "embedding".
3. Client submits an embedding job via Conductor.
4. Placement Gate selects mock adapter (capabilities match, health probe passes).
5. Mock adapter returns synthetic ResultPacket with lineage.
6. Acceptance Gate validates packet, writes GateRecord.
7. EventEnvelope emitted at each gate transition, all sharing session correlation id.

Wrong-Role Denial Checks

• Principal with role viewer requests embedding job → Identity Gate denies, GateRecord written with decision = deny, reason = "role viewer not authorized for lane embedding".
• Principal with role hardware-researcher (Grok lane role) requests Conductor dispatch → denied; that role does not unlock Conductor lanes.
• Principal with expired session → denied at Identity Gate before reaching Placement.

Blockers

• Awaiting Codex confirmation on ProviderAdapter field additions from contract-fit-review.
• Mock principal/role set needs Codex sign-off.

Next Handoff

→ Codex: approve role set and adapter interface. → GLM: implement mock adapter and gate scaffolding per file 3.