0 of 317 twin API surfaces match the real vendor response.
0 drifted
0 critical findings
0 ruled
5 twins
Every tool Pome serves that a vendor does not declare carries a registered written reason: 27 of 27, none unexplained. Compared against captured real vendor responses, re-captured on dispatch rather than on the daily run; every row states how old its baseline is. Recorded daily since 3 Aug.
Platform
Pome platform uptime that evaluates agents.
DashboardOperational
3 Aug100.00% uptimeToday
Isolated sandboxes
Control plane uptime that runs MicroVM-isolated sandboxes.
Control planeOperational
3 Aug100.00% uptimeToday
Digital twins
Digital twin fidelity check: No twin called upstream on this run. Each surface was compared against a committed capture of the real upstream API, re-captured on dispatch rather than on the daily run.
Responses is whether a twin's answers match a captured vendor response. Tool list is whether it offers the same MCP tools the vendor's own server declares.
GitHubDegradedMCP 36 of 36 unmeasuredWrites not runMCP reads not runNo baseline
Responses0 of 99 matchTool list0 conflicts · 34 of 44 GitHub tools coveredBaseline noneLast drift 11 Aug, resolved
3 Aug36 of 38 days matched · 7 unmeasuredToday
SlackDegradedMCP 4 of 18 unmeasuredWrites not runMCP reads not runNo baseline
Responses0 of 51 matchTool list0 conflicts · 18 of 19 Slack tools coveredBaseline noneLast drift 17 Aug, resolved
3 Aug37 of 43 days matched · 2 unmeasuredToday
StripeDegradedWrites not runMCP reads not runNo baseline
Responses0 of 52 matchTool list1 conflict · Stripe uses a different tool architectureBaseline none
3 Aug28 of 29 days matched · 16 unmeasuredToday
GmailDegradedWrites not runMCP reads not runNo baseline
Responses0 of 59 matchTool listMCP table adopted (13 not independently compared)Baseline none
3 Aug35 of 36 days matched · 9 unmeasuredToday
LinearDegradedWrites not runMCP reads not runNo baseline
Responses0 of 56 matchTool list0 conflicts · 22 of 58 Linear tools coveredBaseline none