Profile
Your reports
- What you filed, and what came of it
Reporting a problem
A report raises a review by an authorised role. It never edits a football record — a correction arrives through the source the fact came from, with its provenance intact, because a platform whose readers can edit football has no football authority to protect.
Sign in to report a problem. A report is attached to your account so the platform can tell you what came of it, and there is nothing to show for a reader who is not signed in.
What Soka365 does not offer
Soka365 is not a social network and does not intend to become one. These are not features waiting to be built: each is prohibited by a clause of the frozen design constitution, and the clause is named so you can check it rather than take our word.
- Comments
Experience Bible §4.2.1 XD-049 MUST NOT
Soka365 is not a social network, and XD-049 names comments explicitly. The product specification asks for them; the frozen design constitution prohibits them. The conflict is recorded for the programme owner rather than resolved by building one.
- Reactions, likes and emoji
XD-049; P-03; carries_engagement_metric
Named by XD-049, and every one of them is a per-item counter of reader attention. P-03 prohibits an engagement metric and the column that would hold one fails a literal FALSE CHECK in three tables.
- Discussions, match conversation and community spaces
XD-049 — "no user-generated content"
A discussion space is user-generated content published to other readers, which is the category XD-049 prohibits rather than a feature within it.
- Follower counts and public community profiles
XD-049; FD-2558; FD-1591
XD-049 names follower counts. Beyond that, no reader is visible to any other reader anywhere on this platform: a subject’s data is reachable only by that subject, and there is no route that returns one reader’s record to another.
- Community Reputation Score
Book 3 §16.7 requires it; P-03 prohibits it
A reputation score is a fan score and a user value tier by another name, and it is an ability assessment of a person. `carries_ability_assessment` is a literal FALSE CHECK on the report table for this reason.
- Player ratings in a match thread
Book 3 §16.3 lists them; charter §7 freezes the prohibition
A reader-fed player rating is a Player Rating. Routing it through a community feature changes who supplies the number and nothing about what the number is. P-01 and P-08 apply unchanged.
- Trending or most-discussed
P-04; FD-2018; FD-2019
A popularity ordering over reader activity is the Trending Engine™ with a different input. BC-07 and BC-08 each refused it and `verify:content` fails any rail matching it.
- Community analytics — engagement rate, retention, growth
Book 3 §16.9 requires them; P-03 and FD-1591 prohibit them
The platform admits no engagement signal class at all, so there is nothing to aggregate. The platform measures reports by state, which is a queue depth and not a measure of readers.
- Blocking another reader
Not applicable — there is nobody to block
Blocking exists to stop one person reaching another. No route on this platform lets one reader reach, see, name or mention another, so a block control would protect against a path that does not exist — and building the path in order to be able to block it is the wrong order. If XD-049 is ever ruled differently, blocking ships with the content and not after it.
- AI moderation, toxicity scoring and discussion summarisation
Book 3 §16.8 requires them; there is no model and nothing to moderate
The platform holds no model (BC-10 established that "AI" here is deterministic computation), and with no user-generated content there is no text to classify. A toxicity score over readers would be an ability assessment of a person besides.