What is waiting, and what is broken. Every figure below is a count this server returned; a panel that could not be loaded says so instead of showing a zero, because a zero and a failed request look identical and mean opposite things.
Needs attention
Derived from age and from health, which are the only two things this server can say without somebody having set a priority. Nobody has set a priority on any request: no source table has the column.
System health
Structural read. The full component list is under Systems.
AI suggests. Humans verify. The registry decides. Nothing in this queue is an animal yet. Each row is a photograph somebody sent in, and the only way one becomes an individual in the catalogue is a curator approving it below — which is why every decision here asks for a reason before it will submit.
| Image | Submitted by | Reserve | AI result | Confidence | Status |
|---|
Oldest first, deliberately. A queue sorted by score puts the confident submissions at the top and leaves the doubtful ones — the ones that actually need a person — at the bottom forever.
The catalogue. Merged identities are kept permanently and never deleted — historical identification decisions matter, and removing one orphans every encounter record filed against the code she used to have. A merged row still resolves, to the animal she now means.
This list shows HIDDEN clubs, unlike the device-facing listing. The console is the one place a club that has unlisted itself still has to be reachable, or an abusive one becomes unmoderatable by hiding.
Clubs
…
| Club | Where | Members | Posts | Held |
|---|
Members —
A volunteer can read the moderation queue and post without the member rate limit. Only a moderator can act on the queue — approving or removing somebody else's post is a decision, and handing it to whoever volunteered first is how a club moderates itself into a grievance. The owner cannot be changed here.
| Member | Device | Since | Role |
|---|
House clubs and machine-written posts
Create the house clubs adds Faunterra Club and WildJournal Club if they are missing, and one club per reserve the knowledge pack knows. These are created as real, unflagged clubs — they are the companies' own, not examples — so they carry no DEMO badge and the Remove button below will not take them away. It is idempotent by slug and never touches a club that already exists.
Remove machine-written posts deletes every post carrying the demo flag, by the flag and never by a list of names. It removes no club and no membership. A club is removed by its owner through the ordinary route, like anybody else's.
Starter activities
…
Written by the model, labelled as such inside the post itself, and put through the same submission guard a typed post is — so it cannot publish what a person could not. It writes only into clubs carrying the demo flag: machine-authored posts in somebody's real club is putting words in their mouth.
…
Compose post
| ID | Author | Species / tag | Text | Kudos | Status |
|---|
Oldest first. A queue worked newest-first leaves the oldest hold waiting forever, and a hold that waits forever is a deletion nobody decided on.
| Club | Post | Category | Held since |
|---|
Held posts are aged from a DATE, because a post has no clock — the same rule that keeps a time of day off a sighting.
Reader reports against published posts, read out of the requests inbox so this page and that one cannot come to disagree about what is open.
Somebody who writes to support expects to be read by somebody here, which is why this is readable at all and why it needs its own permission. Every read of a thread appends an audit row.
Select a device thread on the left.
Submitted from the partner portal at /portal. Approving issues that partner's access token — it is displayed once and never again.
| ID | Organisation | Type | Contact | Answers | Status |
|---|
Suspending a partner stops their listings being public and stops them editing. Their token keeps working as a credential, so reactivating does not need a new one.
| ID | Organisation | Type | Contact | Listings | Status |
|---|
New itinerary
One inbox over every store that already holds a request. There is no `requests` table: this is a read across applications, recognitions, candidates, club reports and support threads, so a row cannot fall out of it by a router forgetting to write here.
Component by component, including the ones that do not exist. A service nobody deployed reads NOT DEPLOYED and never counts against the overall figure; a deployed service this call did not look at reads UNKNOWN and does, because a green light for something nobody checked is the same lie in a smaller font.
The audit log is a window, not a door. There is no route here that writes, corrects or hides: the table is append-only in shape, and a wrong event is corrected by appending a later one that says so.