JSP SHRARA / Our Open Method · JSP HOLDING · Research and education
JSP SHRARA — Public development status and proof thresholds
Here we distinguish between what is already visibly present on the website and what remains a technical or scientific ambition. An ambition must never be presented as completed through the design of a dashboard.
What exists now
JSP SHRARA has an independent main section within JSP HOLDING with informative pages about encyclopedia, journalism, research, language, children, and the morning newspaper. Additional standard pages describe how future dossiers, corrections, and editorial assessments are intended to function.
What is still missing
There is no full Wikipedia-wide subject index with verified entries, no continuous real-time news feed, no automatically proven fact-check for every media output, and no independently proven production version of DAM-DMA for this application.
Which figures we must publish later
Number of subject IDs, content-verified entries, opened claim dossiers, processed corrections, average verification time, unvetted dossiers, percentages of external audits, and license coverage must be tracked separately. These figures must not be fabricated.
Safety boundaries
A false accusation can harm people. Medical, legal, and reputation-sensitive claims are subject to higher evidence requirements and human review. The website must be accessible to people of different ages, languages, and beliefs.
Next milestones
First, testable sample entries and public claim dossiers; then the data model, rights inventory, correction procedure, and testable newspaper edition. Only after independent evaluation and technical monitoring can large-scale imports or more frequent updates begin responsibly.
Accountability status: A project plan, pedagogical lesson, or editorial method is not the same as an operational, independently tested knowledge service.
Administrative step on October 9, 2026
In the first administrative development phase, four separate Shopify data definitions existed for subjects, sources, claims, and corrections. 3 subject, 2 source, and 3 claim records have been registered. The correction register is still empty. All mentioned research records remain outside direct public Storefront access. View the dated public snapshot →
A new development milestone without sham approval
On October 9, 2026, two new protected administrative types were realized: shrara_review and shrara_release, which initially counted 14 and 12 content fields respectively (later expanded with typed references). In addition, separate pages exist for the assessment dossier and the publication gate. The local publication check is not authorization: there is no independent publication server that technically enforces decisions, no established independent review board, and no approved claim dossier. Both new registers currently contain zero records.
Follow-up check — October 9, 2026: linked sources and secure publication
The current administration counts seven protected SHRARA data registers: subject, source, claim, evidence, correction, editorial assessment, and publication proposal. The three existing claims now have a mandatory typed subject reference. For the two registered pieces of evidence, the source-claim link is type-checked. Assessment, correction, and publication proposal have received additional mandatory typed references.
In a real Shopify security test, a incorrectly linked source record was rejected in the assessment register. There are still zero actual independent assessments, zero real publication proposals, and zero formal correction records.
A separate, not-yet-rolled-out software prototype for publication assessment has passed 25 of 25 synthetic software tests. It uses text hashes and signed decision data, but there is still no production backend, no connected employee identity management, no immutable audit history, and no Shopify-enforced publication gate. A successful test result is not editorial recognition.
Read Evidence and Source Anchoring and the publication conditions. The demo newspaper, educational examples, and research library remain distinct from officially assessed reporting.
New control phase: testable publication and secure source provenance
The local development trial JSP SHRARA Release Gate v0.2 now includes a separate trust boundary: a request only provides claim and publication IDs. A future authorized server must independently retrieve all evidence, source rights, employee roles, original text, and assessment data from trusted systems. The test code does not yet contain a real server connection or Shopify publication authority.
In the protected technical trial, 42 of 42 automated tests yielded the expected outcome, including refusal of missing source records, manipulated input, and impermissible date values. A separate control link can identify subsequently modified or truncated audit records if its signed checkpoint is kept securely outside the registry. This feature is not a proven production audit archive and no automatic truth check.
Language and accessibility audit: the Shopify store has English as the primary language and Dutch as a published additional language. During a public check, the Dutch /nl/ address also led back to /en/. The active Netherlands market showed no separate linked web presence. Language routing, screen readers, SEO, and the position of other JSP companies therefore require a general, controlled solution; global language settings have not been changed.
The source code has been saved as a checked ZIP package v0.2 in the internal Google Drive folder ChatGPT. It is not yet a service for visitors. The full newspaper, encyclopedia, and independent assessment organization are explicitly not certified as operational.
Publication security v0.3 — tested, but not in production
In the follow-up build of October 9, 2026, an independent local HTTP control component was created, with only a health check and a secure read and assessment route. The code offers no route to publish, delete, or modify the Shopify store. The interface rejects requests without valid access, other types of input, incorrect HTTP methods, and missing or inconsistent evidence signals.
An additional recheck compares claim, review, publication proposal, evidence, sources, reuse rights, roles, candidate text, and timeliness just before releasing a technical admission signal. Even a currently valid assessment can be rejected when an assessor has been disabled in the meantime, the source right is revoked, or a piece of evidence changes.
The local synthetic test suite counts 70 successful tests out of 70, including real network requests on a local loopback address. In the first test suite, errors in handling large requests and timeouts were discovered and corrected. The tested software has been saved as a separate ZIP archive v0.3 in the internal project documentation, along with a current acceptance matrix.
Boundaries: there is no live Shopify link, paid hosting, operational identity service, key vault, independent assessment board, or transactional publication system yet. Existing Shopify administrators could bypass a future loose check as long as their rights are not separately limited and monitored. A test result is not the same as factual truth or human consent. Automatic publication remains NOT PERMITTED until these points have been demonstrably resolved.
SHRARA search engine v0.1 — October 9, 2026
Our own encyclopedic search function now has a separate pilot program that makes 30 existing SHRARA pages searchable. The index distinguishes between two source entries, three education or exercise pages, seventeen method pages, seven categories, and one status page. Results refer directly to existing dossiers and retain their preliminary proof status. One exercise case is explicitly fictitious.
The independent test version has passed 17 of 17 offline software tests. In the unpublished Shopify development theme, five new search engine files and a separate unpublished concept page have been created and read back. This does not yet mean that visitors can use the search engine on the regular live website. The general Shopify search field remains a separate, primarily product-oriented feature.
What is missing: reliable visual and mobile browser tests of staging, an automatically updated index, full global encyclopedia coverage, an actual DAM-DMA search and source control integration, independent reviewers, and an editorially authorized release. This prototype search engine publishes nothing and provides no AI truth certification.