Unverified50% confidenceSolutionExact time
Nike's closed-loop system flow is: the agent observes the telemetry backend and fleet status through MCP read-only tools, drafts a configuration change proposal, and after human approval the OpAMP server delivers it to the Collectors, then decides on full rollout or rollback based on validation results.
1
Sources
50%
Confidence
Long-term
Relevance
10/25/2026
First Seen
Sources
Related Entities
Related Claims
UnverifiedNike's guardrails employ a design where allowlists and denylists coexist: the allowlist defines what the agent may currently do, growing from an initial 5 items to about 20; the denylist consists of red lines never to be crossed, such as prohibiting the agent from redirecting telemetry data to other destinations.64% similarUnverifiedNike built its own control plane based on the OpAMP protocol, grouping Collectors by topology and infrastructure to control the blast radius of changes.64% similarUnverifiedThe engine exposes a synchronous programmatic interface through which agents can pause the game, step forward frame by frame, fast-forward 50 frames, read and write node positions and velocities, inject semantic actions, and take screenshots at any time, turning an asynchronous real-time system into a synchronously verifiable process.61% similarUnverified后台任务机制的核心设计是通知队列：后台管理器用守护线程跑慢命令，结果放进通知队列，每次调用大模型之前排空队列将结果喂给模型60% similarUnverifiedThe automated permission review process adopts a "human in the loop" design, where automation is responsible for discovery and reminders, and the final decision on whether to remove permissions is made by the repository owner.59% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/1095963API
curl https://kongchang.com/api/v1/knowledge/claims/1095963MCP
get_claim(id=1095963)