Evidence has a scope
A source article establishes what that article says. A file digest identifies bytes. A valid signature establishes a signing result. An installed test establishes behaviour on the recorded device. These are different kinds of evidence and are not interchangeable.
Release claims need a release record
Before publishing an exact version, package size or Android requirement as an app specification, obtain the actual release and record the 8 fields in our verification checklist. Record the method, source and date. This edition has 0 verified APK binaries; its numeric evidence tables describe source files and guide parameters.
How content is labelled
| Content | Method | Limits |
|---|---|---|
| Rules | Explain a stated classic model and house-rule differences | Does not prove an untested app’s settings |
| APK source | Cite the fixed URL found in the supplied reference | Does not certify ownership or availability |
| Probability | Enumerate all 22,100 three-card hands | Assumes 52 cards and 0 wild cards |
| Review date | Date substantive content was prepared or reviewed | Separate from an APK release date |
Commercial transparency
The /go/ routes point to the source archive’s campaign-style external file URLs. Their ownership and any referral relationship are unconfirmed. They are labelled as reference-linked sources, not publisher endorsements. No click analytics or affiliate scripts are included in this build.
Guide evidence record
| Parameter | Value |
|---|---|
| Release metadata fields required | 8 |
| Verified APK binaries in this edition | 0 |
| Automatic date-rotation scripts | 0 |
Editorial review: . Guide parameters and source measurements are separate from APK release specifications.