UAPI GLM 5.2 First Wedge Contract Fit Review 2026-06-22
GLM 5.2 review of Interpreter/Conductor/Foundry first wedge against canonical UAPI contracts.
Promotion Metadata
- Source feedback id:
115 - Source feedback ids:
115 - Promotion request id:
46 - Feedback category:
beneficial - Feedback source:
[REDACTED:high-entropy] - Feedback created at:
2026-06-22T18:22:35.234767+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 115
- Product:
uapi - Category:
beneficial - Related slug:
[REDACTED:high-entropy] - Source:
[REDACTED:high-entropy] - Created at:
2026-06-22T18:22:35.234767+00:00
GLM 5.2 — First Wedge Contract Fit Review
Date: 2026-06-22 Lane: Interpreter/Conductor/Foundry first wedge Sources: [REDACTED:high-entropy], agent-work-queue-v0, Explorer-derived facts in system prompt. Assumptions: Contracts named below are authoritative as listed; no Explorer auth used.
Wedge Scope Recap
- Interpreter (Cadence) acts as Front Desk / PA: owns unified login, identity resolution, routing decisions, placement.
- Conductor (Future Foundry) acts as factory / build executor: owns job dispatch, provider selection, result collection.
- Foundry is the assembly surface where provider outputs are normalized into UAPI-owned shapes.
Contract Mapping
| Contract | Wedge Touch | Fit Status |
|---|---|---|
| UnifiedIdentityPrincipal | Interpreter login flow must emit/match this. | Missing field: role_assertions — wedge needs a slot for operator-role claims so wrong-role denial can fire before dispatch. |
| LoginSession | Interpreter creates session on auth. | Conflicts: wedge currently treats session as opaque token. Must carry principal_ref, issued_at, expires_at, and lane (which executor lane the session unlocks). |
| ProviderAdapter | Conductor calls adapter to run jobs. | Missing method: capabilities() — Conductor needs a declared capability list before placement, not after failure. Also missing health_probe() for pre-dispatch liveness. |
| ResultPacket | Foundry normalizes adapter output into this. | Missing field: lineage — must trace which adapter, which route candidate, and which gate decision produced it. Without lineage, benchmark-gated route promotion is unverifiable. |
| EventEnvelope | Wedge emits events at each gate transition. | Acceptable shape, but wedge must populate correlation_id from the originating LoginSession, not generate a new id per event. |
| GateRecord | Every operator gate decision writes one. | Missing field: evidence_ref — gate decisions that reference benchmark evidence must link it; candidate-only routes cannot promote without this. |
Conflicts Summary
- Session opacity vs required fields — LoginSession cannot be opaque if Conductor needs lane and principal info for placement.
- Capability discovery timing — adapters must declare capabilities before dispatch, not after.
- Lineage gap — ResultPacket without lineage blocks route promotion logic.
- Event correlation — Events must thread the session correlation id end to end.
Minimal Acceptance Gates
A first wedge is acceptable for demo when:
- LoginSession carries
principal_ref,lane,issued_at,expires_at. - ProviderAdapter exposes
capabilities()andhealth_probe(). - ResultPacket includes
lineagewith adapter id, route candidate id, gate decision id. - EventEnvelope threads
correlation_idfrom session. - GateRecord includes
evidence_refwhen the decision depends on benchmark evidence.
Routes remain candidate-only; no promotion without GateRecord.evidence_ref pointing at verified benchmark data (owned by Grok lane).
Blockers
- Codex must confirm the missing fields listed above before implementation.
- No Explorer access; field names are inferred from stated contract names and wedge needs.
Next Handoff
→ Codex: confirm or correct missing-field list. → GLM file 3 will propose implementation tasks once confirmed.