All runbooks
evidenceuapiredacted view

UAPI Implementation Target Discovery

Read-only discovery evidence: no confirmed production UAPI implementation target found yet.

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

UAPI Implementation Target Discovery

Read-only discovery evidence: no confirmed production UAPI implementation target found yet.

Promotion Metadata

  • Source feedback id: 154
  • Source feedback ids: 154
  • Promotion request id: 85
  • Feedback category: consider
  • Feedback source: ai-lane
  • Feedback created at: 2026-06-22T20:01:32.001133+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 154

  • Product: uapi
  • Category: consider
  • Related slug: ``
  • Source: ai-lane
  • Created at: 2026-06-22T20:01:32.001133+00:00

UAPI Implementation Target Discovery (2026-06-22)

Created: 2026-06-22T19:59:37Z Authority: read-only discovery evidence. No implementation edits.

Question

Find the current production UAPI implementation target before applying the first-wedge contracts.

Sources Checked

  • Local project roots under /Users/scott/Desktop/Projects
  • Local git roots under /Users/scott/Documents/New project
  • UAI-2/project.md
  • UAI-Director/src/director_server.py
  • Thinktank UAPI sidecar:
  • [REDACTED:high-entropy].md
  • [REDACTED:high-entropy].md
  • [REDACTED:high-entropy].schema.json
  • [REDACTED:high-entropy]/*
  • Connected GitHub search for uapi PlacementDecision RunRecord ProviderAdapter UAPI Bridge

Findings

  • No confirmed production UAPI service repository was found.
  • UAI-2 is a project coordination surface, not implementation.
  • UAI-Director is a local operator/Cadence coordination surface; its server is read-only intake/probe code, not UAPI.
  • uai-agent-dispatch currently holds Codex dispatcher schemas, fixtures, validation evidence, queues, and rollups.
  • [REDACTED:high-entropy] is the closest code asset, but its runbook explicitly says fixture-only/no execution/not a UAPI service.
  • The Thinktank repo is dirty with many existing changes, so it must not be repurposed casually.
  • GitNexus tools were not callable in this Codex session; therefore no symbol edits were attempted in the indexed repo.

Reusable Assets

  • UAPI policy vocabulary from Thinktank:
  • Device
  • WorkloadRequest
  • RoutingPolicy
  • PlacementDecision
  • ApprovalRecord
  • RunRecord
  • EvidencePacket
  • ProductIntegrationContract
  • Codex first-wedge v0.2 contracts:
  • UnifiedIdentityPrincipal
  • LoginSession
  • JobBrief
  • PlacementDecision
  • GateRecord
  • EventEnvelope
  • ResultPacket
  • StorageCandidate

Decision

Treat current UAPI implementation status as target_not_selected.

Do not start coding production UAPI inside Thinktank, UAI-Director, UAI-2, or uai-agent-dispatch unless an operator gate chooses that path. The next safe step is a scaffold target gate that compares:

  1. New isolated UAPI repo.
  2. Existing Thinktank fixture promoted into a new bounded package.
  3. Existing UAI-Director/Command-Center integration surface.
  4. Remote/lab repo if discovered by worker review.

Blockers

  • Production target repo/path/language not selected.
  • GitNexus MCP unavailable for required impact checks in /Users/scott/Documents/New project.
  • No real auth/session store chosen yet.
  • No storage policy approval for Forge /mnt/skip_data; it remains candidate storage only.

Next Handoff

Queue Grok to finish implementation-target discovery and remote/lab repo mapping. Queue GLM 5.2 to prepare a scaffold gate and adapter-test plan that can be applied once Codex chooses or creates the implementation target.