Editorial standards

An idea should be presented in a form that allows a reader to understand what is proposed, what supports it and what remains uncertain.

Claims and evidence

Hypotheses are labelled as hypotheses. Proposed measures are distinguished from validated instruments. Observations, interpretations and conclusions should remain identifiable. Citations must be real, checked and relevant to the claims they support.

Publication on Strangium does not establish a claim as scientific fact. Strangium is not an accredited university, recognized standards authority or formally peer-reviewed scientific journal.

Authorship and AI collaboration

Every research document identifies its author. Substantial analytical, drafting or technical assistance from AI should be acknowledged in the relevant publication, with its role described. The human author remains responsible for claims, source verification and approval.

The website’s initial structure, design and public editorial introductions were prepared with AI assistance under the founding brief. This acknowledgement is not a claim that AI-generated analysis has been independently validated.

Status and review

Documents use explicit status labels: Draft, Experimental, Under Review, Accepted or Superseded. The RFC Library defines these labels. Review scope and reviewers should be stated when applicable. Editorial acceptance is not equivalent to scientific validation or independent peer review.

Dates and revisions

Creation and publication dates describe the public record. They must not imply an undocumented research chronology. Each RFC has its own revision history. Historical public releases remain accessible through permanent release URLs and the archive.

Information boundaries

Only approved public material belongs on this website. Original conversations, raw experiments and working observations remain in a separate private research archive. Commercial algorithms, proprietary datasets and unreleased product architectures are protected intellectual property.

A page omitted from navigation is still public if it is deployed. Private material must never be included in static output, search indexes, release downloads or public backup files.

Reading technical material

Technical publications may include code and mathematical notation. The examples below demonstrate presentation only; they are not research results or a published narrative scoring model.

{
  "identifier": "NSE-001",
  "revision": "0.1",
  "status": "Draft",
  "releaseType": "editorial-record"
}

A mathematical typesetting example, the sum of the first $n$ positive integers:

$$\sum_{k=1}^{n} k = \frac{n(n+1)}{2}$$

Corrections

Substantive corrections should state what changed, why it changed and which revision is affected. A correction should preserve enough context for a reader to understand the earlier claim and the revised position.