UAPI Grok Implementation Target Map
Grok Worker F read-only map of candidate UAPI implementation targets; no production service found.
Promotion Metadata
- Source feedback id:
157 - Source feedback ids:
157 - Promotion request id:
88 - Feedback category:
consider - Feedback source:
ai-lane - Feedback created at:
2026-06-22T20:07:32.995851+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 157
- Product:
uapi - Category:
consider - Related slug: ``
- Source:
ai-lane - Created at:
2026-06-22T20:07:32.995851+00:00
Grok UAPI Implementation Target Map (2026-06-22)
ALIVE: true Lane: Grok Worker F Authority: read-only. No code/service changes.
Sources
Required: uai-agent-dispatch diaries (uapi-implementation-target-discovery, agent-work-queue-v4, forge-sn850x-storage-policy-gate-v0), schemas/uapi-first-wedge-contracts-v0.2.schema.json, UAI-2/project.md, uai-thinktank uapi-policy-simulator-runbook.md. Workspace: hardware-autorouter-review.md, grok--inventory/route/forge/.md, uapi-*-runbooks contexts, UAI-Director src/README.
Commands/Searches (read-only only)
list_dir .; read_file (6 required + 10+ workspace files); grep UAPI|PlacementDecision etc in workspace + limited py; run_terminal ls/find (projects roots, uapi dirs, *.py server patterns, safe maxdepth, no ssh/auth). No mutations, no remote.
Candidate Surfaces
- uai-agent-dispatch: fixture/coordination (schema, fixtures, queues, validator; no impl)
- UAI-Director (director_server.py): coordination (Cadence operator intake/probes, local only)
- UAI-2: coordination (high-level project vision; UAPI planned as future control plane)
- UAI-Command-Center: coordination (docs/diary/prompts)
- uai-architecture: coordination (routing/control plans)
- uai-cloud-gpu: coordination (burst planning)
- uai-hw-autorouter-review: research/coordination (hw inventory, route plans, storage policy support)
- uai-glm52-first-wedge: coordination (wedge prep)
Real UAPI Service?
No. No production service repo found. No real PlacementDecision/RunRecord execution, adapters, or endpoints. Only explicit fixtures + coordination surfaces. Matches verified: "no confirmed production UAPI service repo".
Recommendation
Strong: new isolated repo for UAPI service. Reasons: clean boundaries; avoid dirty repos/coordination surfaces; direct first-wedge contract adoption (UnifiedIdentityPrincipal, PlacementDecision, GateRecord, EventEnvelope, ResultPacket, StorageCandidate). Order: 1. isolated repo 2. extract simulator as fixture pkg 3. existing coord surface (risk) 4. remote (none discovered).
Assumptions/Blockers/Next
Assumptions: searched roots cover candidates. Blockers: target unselected; contracts unimpl; /mnt/skip_data candidate_storage_only only; no adapters/registry. Next: Codex/operator select target (isolated pref) + init. GLM scaffold/tests. Promote map.
Report: ALIVE true | REDACTED:high-entropy.md | Surfaces classified, no service, isolated rec, cmds/sources/blockers. <3800. COMPLETE. End.