Governing document · 03

The Contribution Specification

How records enter the catalog, how the community verifies them, and how disagreements are resolved. Every change is attributed; nothing is ever deleted.

VERSION 1.1
LICENSE CC0
STATUS BINDING
§01

The record lifecycle

Every record moves through a fixed set of states. Only the transitions below exist; records are never hard-deleted, and every version is preserved in the permanent history.

DRAFTSaved by the contributor; visible only to them. Expires after twelve months idle.
PENDINGSubmitted for review. Enters the public review queue.
UNDER REVIEWVotes have been cast but the verification threshold is not yet met.
VERIFIEDThe weighted Confirm total met the threshold. The record is citable and counts toward its contributor's trust level.
DISPUTEDA factual challenge with written explanation is open. The record remains visible with its dispute noted.
DEPRECATEDSuperseded by a successor record. The OSID resolves for decades and points at its canonical successor.

Permitted transitions: Draft → Pending → Under review → Verified; Verified ↔ Disputed; and Verified or Disputed → Deprecated. Deprecation is Steward-only, and the successor record must already exist before it is applied.

§02

Trust levels & vote weights

Trust is earned through verified work, not purchased or claimed. Each level carries a vote weight used in verification arithmetic.

Newcomer×0.5Every new contributor starts here.
Contributor×1Five verified submissions.
Trusted×2Twenty-five verified submissions and six months active.
Steward×5Appointed. A single Steward Confirm verifies a record.
§03

Verification

A record becomes Verified when the weighted Confirm total reaches 5, from at least three distinct contributors, at least one of whom is Contributor level or above. A Steward Confirm satisfies all three conditions at once.

Open does not mean unchecked. A small, verified catalog is more useful than a large, unreliable one.

Dispute votes require a written explanation. Abstaining is always available and never penalised — vote only on records you can evaluate against a reference.

§04

Edit policy

Versions are immutable and append-only: every edit creates a new version, and prior versions are never overwritten. Core identifying fields — country, year, denomination — cannot be changed after assignment; a different stamp needs a new record. Major edits to a Verified record return it for re-verification; minor edits (typography, formatting, reference notes) do not.

§05

Disputes

Any contributor may dispute a Verified record by filing a factual challenge with a written explanation and, where possible, a reference. The record remains publicly visible while disputed, with the dispute displayed alongside it. Stewards resolve disputes by upholding the record, applying a correcting edit, or deprecating it in favour of a successor — each path recorded permanently in the audit log.

This page is a summary

It restates the binding rules of the Community Contribution Specification v1.1 in plain language for day-to-day use. Where this summary and the full specification disagree, the specification wins.