JSP SHRARA / Our Open Method · JSP HOLDING · Research and education
JSP SHRARA — Public development status and evidence limits
We distinguish what is already visible on the site from what remains a technical or scientific ambition. A dashboard's appearance must never make an ambition look like a completed achievement.
What exists now
JSP SHRARA has a separate main section within JSP HOLDING with informational pages about its encyclopaedia, journalism, research, languages, education for children and the morning newspaper. Additional standards pages describe how future dossiers, corrections and editorial reviews should work.
What is still missing
There is no complete, Wikipedia-scale index of independently checked topics, no continuously updated live news feed, no automatically proven fact-check of every media statement, and no independently demonstrated production version of DAM-DMA for this application.
Figures that should be published in the future
Counts of topic identifiers, content-checked entries, open claim dossiers, resolved corrections, average verification times, unreviewed dossiers, external audit percentages and licensing coverage must be recorded separately. These figures must not be invented.
Safety limits
False accusations can harm people. Medical, legal and reputation-sensitive claims require stronger evidential safeguards and human review. The website should be accessible to people of different ages, languages and beliefs.
Next milestones
First come verifiable sample entries and public claim dossiers; then a data model, rights inventory, correction procedure and testable newspaper edition. Large-scale imports or more frequent updates would require independent evaluation and technical monitoring.
Accountability status: A project plan, teaching exercise or editorial method is not the same thing as an operational, independently evaluated knowledge service.
Administrative milestone on 9 October 2026
According to the dated project record, the initial administrative phase included four separate Shopify data definitions for topics, sources, claims and corrections. Three topic records, two source records and three claim records were registered. The correction register was still empty. These research records remain outside direct public Storefront access. View the dated public snapshot →
A development milestone without false approval
The Dutch project record dated 9 October describes two further restricted administrative types, shrara_review and shrara_release, initially containing 14 and 12 substantive fields respectively, later extended with typed references. Separate pages cover the review dossier and publication gate. The local publication check is not an authorisation system: there is no standalone publication server enforcing decisions, no established independent review board, and no approved claim dossier. Both new registers were reported as holding zero records.
Follow-up controls — traceable sources and safe publication
The dated record describes seven restricted SHRARA data registers: topic, source, claim, evidence item, correction, editorial review and publication proposal. The three existing claims acquired required typed topic references. The two registered evidence items underwent type-checked source-to-claim linkage. Reviews, corrections and publication proposals also acquired additional required typed references.
A Shopify safety test reportedly rejected a wrongly linked source entry within the review register. There were still zero actual independent reviews, zero real publication proposals and zero formal correction records.
A separate, undeployed publication-review prototype was reported to have passed 25 of 25 synthetic software tests. It uses text hashes and signed decision data but has no production backend, integrated staff identity management, immutable audit history or publication gate enforced inside Shopify. A passing software test is not editorial approval.
Read about evidence records and source provenance and the publication requirements. The sample newspaper, teaching exercises and research library remain distinct from formally reviewed journalism.
Further controls: testable publication and trustworthy provenance
The local research prototype JSP SHRARA Release Gate v0.2 was described as using a separate trust boundary: a request supplies only claim and publication identifiers. A future authorised server must independently retrieve all evidence, source rights, staff roles, original text and assessment records from trusted systems. The prototype code does not yet include a real server connection or Shopify publication permissions.
Within the restricted technical trial, 42 of 42 automated tests reportedly returned their expected outcomes, including rejection of missing source records, manipulated input and unacceptable dates. A separate checking component can identify later changes or truncation of audit records if its signed checkpoint is safely stored outside the register. This is neither a proven production audit archive nor an automatic truth test.
Language and accessibility audit: the Dutch record states that English is the Shopify shop's primary language and Dutch an additional published language. During a public check, the Dutch /nl/ address also returned to /en/; the active Netherlands market showed no separately linked web presence. Language routing, screen readers, SEO and the position of other JSP projects therefore required a general controlled solution. The global language configuration was not changed by that work.
The project record describes source code saved as a version 0.2 ZIP package in a restricted Google Drive project folder. That archive is not a service for visitors. The complete newspaper, encyclopaedia and independent review organisation were explicitly not certified as operational.
Publication security v0.3 — tested locally, not in production
The 9 October follow-up describes an independent local HTTP component with a health check and restricted read and review routes. It includes no interface for publishing or deleting material or changing the Shopify store. It rejects unauthorised requests, unsupported input, wrong HTTP methods and missing or inconsistent evidence signals.
An additional safeguard rechecks the claim, review, publication proposal, evidence items, source records, reuse rights, staff roles, candidate text and timeliness immediately before a technical approval signal is produced. A previously valid review can be refused if a reviewer is subsequently disabled, source rights are withdrawn or an evidence item changes.
The local synthetic test series reportedly passed 70 of 70 tests, including network requests to a local loopback address. Early tests exposed and led to corrections of issues involving large requests and timeouts. The tested software was described as archived separately in version 0.3 alongside an acceptance matrix.
Limits: there is no live Shopify integration, paid hosting, operational identity service, key management system, independent review board or transactional publication system. Existing Shopify administrators might bypass a future external check unless permissions are independently restricted and audited. Passing a test is not the same as factual truth or human consent. Automatic publication remains NOT AUTHORISED until these points are demonstrably resolved.
SHRARA search engine v0.1 — 9 October 2026
The original development record describes a separate prototype that can search 30 existing SHRARA pages. Its index distinguishes two source entries, three teaching or practice pages, 17 methodology pages, seven sections and one status page. Results link to existing dossiers while preserving preliminary evidence statuses. One teaching case is explicitly fictitious.
The standalone test version reportedly passed 17 of 17 offline software tests. Five search-engine files and one separate unpublished draft page were created and inspected in an unpublished Shopify development theme. This does not demonstrate that the search engine is accessible to ordinary visitors on the live site. The general Shopify search field remains a separate, primarily product-oriented feature.
Still needed: reliable visual and mobile browser tests in staging, an automatically refreshed index, worldwide encyclopaedic coverage, a real DAM-DMA search and source verification integration, independent reviewers and editorial release authorisation. This prototype publishes nothing and awards no AI truth certificate.
Explore the public encyclopaedia → · Open the sample library →