Skip to main content

Editorial Policy

The Admissibility Wiki is a public vocabulary layer for careful explanation.

Its editorial policy preserves clarity, neutrality, and reviewability as the StegVerse vocabulary grows.

Done State

A page is publication-ready when it:

  • has a clear purpose;
  • uses stable terminology;
  • separates concept from implementation;
  • identifies maturity posture;
  • avoids unsupported claims;
  • links related pages;
  • can be understood without private context.

Page Posture

Each page should be understandable as one of the following:

concept
implementation map
comparison
proof path
runbook
ontology guide
essay
external comparison

Maturity Posture

When a concept is mapped to implementation, use one of these maturity postures:

conceptual
implemented
experimental
proposed
external

Do not silently promote a proposed concept into an implemented claim.

Claims Standard

Strong claims should be used only when supported by public evidence.

Examples that need public support include:

  • first;
  • only;
  • proven;
  • complete;
  • universal;
  • production ready;
  • standard.

Neutrality Standard

The wiki can explain why a concept matters.

It should not pressure the reader to accept StegVerse claims.

Preferred pattern:

Define the concept.
State the distinction.
Give a minimal example.
Map to implementation if appropriate.
Name remaining limits.

Source Posture

Pages may reference StegVerse artifacts, but should distinguish them from independent sources.

Use labels such as:

  • internal artifact;
  • public repository artifact;
  • external source;
  • implementation evidence;
  • proposal;
  • commentary.

Review Questions

Before merging a page, ask:

  1. Can a neutral reader understand the term?
  2. Does the page preserve governance distinctions?
  3. Does the page avoid overclaiming?
  4. Does the page help future researchers or developers?
  5. Does the page improve the public proof path?

Drift Control

When a core definition changes, update all of the following as needed:

  • the glossary page;
  • related comparison pages;
  • related proof-path examples;
  • static/ontology/admissibility-vocabulary.v0.1.json;
  • sidebar entries.