The Majlis · the review standard
Verify
التحقّق
This page records how the hosted review process is meant to work. It is not a live submission ledger: the contribution database is not connected in this production build, so there are no submission records here to watch move.
The Atlas village research list is genuinely open now. Sourced corrections can be sent through the private contact desk; that form does not publish automatically or enter this future queue.
What each stage means
Waiting to be read
A future hosted submission will arrive privately. Its subject may be listed, but its unread contents will not be exposed as if the archive had verified them.
Being checked
A maintainer will read it and follow the source it came with. A source that has to be found in a library will take as long as that work requires.
In the archive
An accepted contribution will join the record with its source and a link to the page where it was published.
Declined
A declined contribution will carry a reason in the public process. This describes the intended workflow; no hosted queue is active in this build.
Current production state
No hosted queue is connected
There are no public submission rows to display
The contact desk and Majlis Board form use Netlify Forms and hold submissions for private human review. They do not feed this page automatically. Publishing an empty database frame would suggest a process that production does not have, so this page shows the standard and the working research route instead.
The activation boundary
When the hosted workflow is activated, a small number of maintainers will review it. The designed boundary keeps moderation authority in a database role that a browser cannot appoint for itself. That design is documented here; it is not being presented as a live production queue.
Activation requires more than adding a form: passwordless sign-in, row-level permissions, a named moderator and a signed-out production test all have to pass first. Until then, the private contact desk is the working route.
What is never shown
The future public view is designed never to show email addresses or unread claims. The current private forms are not exposed on this page.
What the public record will keep
The intended workflow keeps a declined item with its reason instead of quietly erasing the decision. That promise begins only when the hosted public queue is activated.