Published records / attributable only
The empty cohort is the record.
This table contains only reviewed observation records with stable IDs, timestamps, a declared Java or Bedrock edition, source traces, and a published state. The documented example does not qualify, and pasted JSON never enters this table.
| Record ID | Endpoint | Edition | Observed at | Reachability | Sources |
|---|---|---|---|---|---|
| 0 recordsNo attributable observation record has been published in either edition. | |||||
What a row requires
- Stable identity
- A schema ID and versioned record ID that remain addressable when the record is corrected.
- Observation trace
- A real UTC observation time, documented method, and at least one attributable source. “Unknown” is valid only when it is the sourced result.
- Declared edition
- The status-protocol family the observation spoke:
minecraft-javaorminecraft-bedrock. One record speaks one protocol; “crossplay” is never a row value. - Strict shape
- Every required field is present; unexpected fields fail validation instead of becoming unlabeled metadata.
- Evidence-backed claims
- Any hostname-control assertion references a dated
owner-evidencesource in the same record. - Reviewed state
publicationStateis explicitlypublished. Example and draft records remain outside the cohort.
Whether a server admits Bedrock is an observation
A row can say a server answers the Java or the Bedrock status protocol only when a published record of that edition says so. With zero published records, edition support for every server a reader might ask about is unknown here — this table does not answer it yet, and it will not guess.
Crossplay is a pair of records, not a value: it can only be shown by one published minecraft-javarecord and one published minecraft-bedrock record for the same server. A Java response is never converted into a Bedrock claim, and a status response in either edition demonstrates an answering endpoint, not admission or playability.
What validation does not establish
- That the endpoint was contacted, was reachable, or returned the pasted values.
- That a source is credible merely because its URL is syntactically valid.
- That an endpoint answering one edition’s status protocol answers the other.
- That hostname control proves broader legal ownership, quality, affiliation, or a place in any site grouping.
Use the local validator to check shape, then read the method to understand the evidence boundary.