Authority and sources

The operational hierarchy is:

1. Zenodo / DOI — canonical published-version record.
2. Canonical Source website — canonical web reference and current presentation of knowledge.
3. Git — version, provenance, and audit history; repository remains non-public.
4. OSF — independent mirror and research record.

This repository hierarchy complements, and does not replace, the project source-authority hierarchy in ../01_ptkr/prism_ptkr/07_SOURCE_HIERARCHY_AND_CODEX_RULES.md.

The website may present current approved explanations and navigation, but it must identify the version and source of normative content. It must never silently rewrite a DOI-bearing publication. Zenodo remains the persistent citation record for published versions.

Human Authority retains approval authority over:

• first publication of canonical or normative material;
• substantive revisions to the Canonical Specification or Foundational Paper;
• changes to frozen terminology;
• new normative Russian equivalents;
• public implementation classifications or listings;
• statements of organizational, legal, standards, certification, trademark, or conformance status;
• public release of the Git repository;
• deployment to the canonical domain;
• launch approval and any future superseding canonical version.

Routine publication operations may later be delegated to named maintainers, but delegation does not transfer the approval authority above. A delegated publisher may release only content whose required approvals and checks are recorded.

Frozen terminology is governed by ../00_governance/FROZEN_TERMINOLOGY.md, the imported decision register, and subsequent Human Authority decisions.

Rules:

1. No frozen term or approved definition may be changed through design, development, CMS configuration, translation, copyediting, search synonyms, structured data, or code.
2. No local glossary term may be presented as approved merely to make the site more complete.
3. Platform Operator, Retailer, and Merchant of Record remain analytically distinct.
4. Expert Commerce remains a core architectural pillar; ECCs and ECSs are not independent sellers in the base model.
5. Market Access Enablement retains its approved English term, Russian normative equivalent, meaning, and restriction boundary.
6. No additional Russian normative equivalent is created in this stage.
7. A translation may be published as reviewed explanatory language without becoming a normative equivalent.
8. Any future normative change requires an explicit Human Authority decision, version assessment, changelog entry, updated hashes, and preservation of the prior version.