Evidence ledger · checked 2026-08-28

Sources, Dates & Confidence

See which public record supports each part of the site and how official, observed, community-unverified, and on-hold labels differ.

How to read this page

A record supports only the claim it actually shows

Roblox supports game identity and current description state. Official APIs support their returned fields. Dated gameplay supports visible interface and sequence context. None of those automatically proves a hidden formula, permanent timer, exact probability, universal item ranking, or a price from a different version.

Public records

Official and dated gameplay evidence

These are player-facing references. Private research notes and unrelated game material are never published here.

Official

Karinderya on Roblox

Exact place identity, SILOG creator, co-op Filipino restaurant premise, five-star goal language, and current description code strings.

Open record
Official

SILOG creator community

Creator identity and a creator-owned destination.

Open record
Official

Roblox badge API

Welcome and OG badge names plus enabled state at the check date.

Open record
Observed

CHALLS gameplay

Tables, chairs, stoves, shop/build context, and the visible customer/order service loop.

Open record
Observed

Berlian first-play and code video

Recent opening, code-control, customer, order, and service interface context.

Open record
Observed

Worker interface video

Hire panel, countdown, and Manual Assign wording in one dated run.

Open record
Observed

Restaurant layout video

Recent build-layout context without proving a universal best floor plan.

Open record
Confidence labels

What each state permits

Official

A Roblox, official API, or creator-owned record supports the named field.

Observed

A dated public gameplay record shows the interface, entity, or sequence.

Community unverified

A destination or claim exists without verified creator ownership.

On hold

The site refuses a value or recommendation until missing comparison fields exist.

When records disagree

Use the most current exact-game state

For codes, the current official description controls listing status while older reports remain visible as history. For interface behavior, prefer the newest clear capture and keep its date visible. For unknown values, the site waits rather than combining different versions into one row.

Update path

What happens after a correction

A correction is checked against the exact Karinderya place and current game context. If it changes a player-facing claim, the relevant page, checked date, and confidence label should change together so old certainty does not survive a new value.

FAQ

Evidence and corrections

Which source controls Karinderya code listing status?

The current Roblox description controls whether a string is currently listed. Older publisher reports remain separate and do not override it.

What can a gameplay video prove?

A dated video can support a visible interface, entity, or sequence. One run does not establish a permanent schedule, universal price, probability, or hidden formula.

How can I submit a correction?

Send the exact claim, a current public URL or screenshot context, the date checked, the server or version context, and what changed through the contact page.

Why are some fields on hold?

The site does not publish a value or recommendation when the fields needed to compare it are missing or tied to an unclear version.