JSP SHRARA / PUBLICATION GOVERNANCE · First local publication check · October 9, 2026

Do not publish just because it looks ready

The next step after a research file is not automatically a public article. We want to be able to verify whether the exact text, source rights, counter-information, risks, and an independent decision have been sufficiently checked. The public truth should not become a sales trick.

A proposal is not yet approval

A new, not publicly accessible data definition shrara_release has been created in Shopify. It can be used later to keep track of the relationship between a claim, assessment record, text version, responsible authorization, withdrawal procedure, and publication date. This definition is not a server-side publication block: Shopify will not automatically refuse a page because this register is empty. That enforcement must be built and tested separately in a later technical step.

Eight checkpoints

1. The exact claim to be published and the version of the text are fixed.
2. The original sources are traceable, accessible, and relevant to this claim.
3. Multiple publications have not been wrongly counted as independent confirmation.
4. Counter-evidence, definitions, and meaningful uncertainties have been investigated.
5. Rights to images, text, quotes, audio, and data have been verified.
6. Privacy, protection of minors, health, and reputational damage have been assessed.
7. The authority and independence of the responsible assessor have been established.
8. Corrections, withdrawal, versions, and accountability have a clear procedure.

Practice with the checkpoints

Below this page on our concept website is a local practice workbench. It creates a preliminary checklist document without sending data to a server. Even when you check all the boxes, you do not yet have independent publication approval, source control, or a news service; you have only declared which steps you believe have been completed.

A clear NO-GO

In the event of missing crucial source origin, insufficient lawfulness, unresolved security risks, or missing authorization, a publication should wait. A draft, research note, or AI summary must not be surreptitiously transformed into a definitively validated report through formatting.

Assessment file → · Correction policy → · Newsroom → · Back to SHRARA →

Technical follow-up trial — October 9, 2026

The internal assessment register now requires real, typed references to a claim and a piece of evidence; a publication proposal requires a typed claim and editorial assessment. In a negative test, Shopify refused a source record when it was incorrectly submitted as a claim. That is a check on data types, not yet a check on factual truth.

A standalone publication control prototype, not connected to our website, has passed 25 synthetic tests. It examines, among other things, the conformity of claims and evidence, text versions, rights, division of roles, conflicts of interest, assessment validity, SHA-256 content hashes, and Ed25519 signatures. Upon full test input, the software only assigns the status "suitable for separately controlled publication step," not "published."

Security boundary: such a prototype must not publish Shopify pages until a separately secured server actually retrieves current data from reliable sources, checks employee rights and key registers, handles logging and withdrawal, and performs a final check of unchanged content. Shopify administrators and other apps can still publish outside of a future service; this must be separately restricted and monitored.

Read the source and evidence links · Current development status.