Curated profile
Rummy 77 profile
Rummy 77 is a reference profile curated by Come. The source profile is published at https://allnewyonoapps.com/rummy77/; the verified Come install path is at /install/.
Rummy 77
Reference profile
Category · Rummy
Rummy 77 facts at a glance
The Rummy 77 reference profile lists the four facts the editorial desk curates: name, category, source status and curator. Verified: those four fields are read from the directory row, not from the publisher. Unverified: anything beyond the four fields (payout route, KYC state, bonus tables, VIP tier, deposit route, withdrawal route) lives on the relevant hub, not on this reference profile.
Why the profile is a reference, not a product
Rummy 77 is listed as a reference profile rather than a Come product because the publisher handles sign-up, KYC, deposits and withdrawals on its own surface. Come does not own the publisher's KYC, the publisher's wallet or the publisher's withdraw flow. Verified: the reference profile is honest about that boundary; the verified install path is the only first-party surface, and it points at the Come app rather than at Rummy 77. Unverified: any claim on the publisher's surface about Come terms is not part of the verified surface until it is read against the Come snapshot.
How the reference profile is read against the rest of the site
The Rummy 77 reference profile fits into the broader Come surface in four places: the install action, the support action, the promo and code hubs, and the VIP table. Each of those is independent of the publisher's surface and resolves against the Come verified surface only.
How the four places are connected:
- Install action. The "Run the verified install path" CTA links to /install/, which is the first-party install route. The publisher's install is independent of the Come install.
- Support action. The support CTA links to /contact/ and /support/. The publisher has its own support channel; tickets opened on the Come support desk are resolved against the Come verified surface only.
- Promo and code. The publisher's promo rows are not on the Come verified surface; only rows on the promos hub are. The code hub lists the status of any public literal code.
- VIP table. The VIP hub lists Come's 15 VIP levels. The publisher has its own VIP table that is not part of the Come verified surface.
Tickets opened on the publisher's support desk. The publisher's support desk resolves against the publisher's snapshot, not the Come snapshot. If a ticket needs the Come verified surface, open it at /contact/ with the install route, KYC state and wallet timestamp; the Come support desk can resolve the ticket against the same snapshot the app reads.
Curation criteria and how a reference profile gets listed
Rummy 77 is listed in the Come app directory because the editorial desk has reviewed the publisher and the four facts on the row match the publisher's own surface. Verified: a reference profile is added to the directory only after a review that names the four fields and confirms the install route at /install/. Unverified: a profile that is added without a review is removed from the directory on the next editorial pass and the support desk treats tickets against the removed profile accordingly.
How the editorial review is conducted:
- Identity check. The publisher's name and the app name are read against the publisher's own surface. A name that disagrees between the publisher and the directory row fails the identity check and the row is not added.
- Category check. The category on the directory row matches the category on the publisher's own surface. A category that disagrees (the publisher says "Rummy" but the row says "Slots") fails the category check.
- Install route check. The verified install path is a first-party route; the publisher's install route is independent. The review confirms that the verified install route on the row matches the route at /install/ rather than a third-party mirror.
- Snapshot timestamp. The row is added with a snapshot timestamp. The timestamp is the source of truth at request time; live values on the publisher's surface may differ after the snapshot, but the row on the directory reads against the snapshot.
How a row is removed from the directory
A reference profile is removed from the Come app directory when the editorial review finds a field that no longer agrees. Verified: a removed row is closed on the next editorial pass and the URL returns a 404 with a pointer to the app directory landing page. Unverified: a removed row that is still linked from a third-party site is not restored on the directory; the third-party link is the third-party site's responsibility, not Come's.
How a row is removed:
- Identity field changes. A publisher name change or an app name change fails the identity check on the next editorial pass and the row is removed.
- Category field changes. A category change (the publisher moves the app from "Rummy" to "Games") fails the category check and the row is removed.
- Install route changes. An install route change (the publisher moves to a third-party mirror) fails the install route check and the row is removed.
- Publisher surface changes. A publisher that disappears or changes its surface fails the surface check and the row is removed.