Pome status

214 of 215 twin API surfaces match the real vendor response.

0 drifted
0 critical findings
1 ruled, reason published
3 twins

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 23 Sept.

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.

GitHubOperational

Responses99 of 100 match · 1 ruled exception (GH-DIV-024)Tool list0 conflicts · 34 of 46 GitHub tools coveredBaseline 79d ago

23 Sept39 of 39 days matchedToday

SlackOperational

Responses59 of 59 matchTool list0 conflicts · 19 of 27 Slack tools coveredBaseline 79d ago

23 Sept39 of 39 days matchedToday

LinearOperational

Responses56 of 56 matchTool list12 conflicts · 22 of 76 Linear tools coveredBaseline 79d ago

23 Sept39 of 39 days matchedToday

matched upstream
matched with a ruled exception
did not match
not checked
not measured
no record

Pome status

Platform

Isolated sandboxes

Digital twins