Skip to main content

Page Template

Use this structure when adding or updating a public vocabulary, governance, proof-path, comparison, implementation-map, or ontology page.

The template exists to make page posture, authority boundary, proposal history, decision history, replayability, and reconstructability explicit.

Purpose​

State what this page defines or explains.

Page Status​

draft | active | superseded | deprecated | historical | external-reference

Page Posture​

concept | implementation map | comparison | proof path | runbook | ontology guide | essay | external comparison | governance policy

Maturity Posture​

conceptual | implemented | experimental | proposed | external

Authority Boundary​

State what authority this page has and what authority it does not have.

Example:

This page defines vocabulary. It does not generate receipts, authorize execution, or replace formalism-tests.

Term Relationship Placement​

When a page defines a StegVerse term, place materially identical terms directly under the StegVerse term before the definition.

Use these sections when relationship information exists:

Equivalent Terms
Overlapping Terms
Adjacent Terms

Equivalent terms are terms from other domains that describe the same underlying concept for the page's purpose.

Overlapping terms describe part of the same concept but do not carry the full StegVerse meaning.

Adjacent terms belong to the same conceptual neighborhood but answer a different governance question.

If no equivalent term is known, say so explicitly rather than silently implying novelty.

Definition​

Give a concise definition.

Distinction​

State what the concept is not.

Why The StegVerse Term Is Retained​

If the page uses StegVerse-specific terminology, explain whether the term is retained because:

  • no equivalent term is known;
  • existing terms are only overlapping;
  • existing terms are adjacent but not equivalent;
  • the StegVerse formulation adds commit-time, consequence, continuity, receipt, or admissibility requirements.

Minimal Example​

Provide one small example that can be understood without private context.

StegVerse Mapping​

Name the relevant StegVerse repo, component, artifact, or proof path if applicable.

Every mature page should identify the governance records that explain how the page entered or changed state.

Use not_applicable only when the page is a seed page that predates the governance-link system.

governance:
  proposal_link: "not_applicable | proposals/<proposal-id>.json | issue-or-pr-url"
  decision_link: "not_applicable | decisions/<decision-id>.json | issue-or-pr-url"
  replay_link: "not_applicable | replay/<decision-id>.txt | command-or-artifact-url"
  reconstruction_link: "not_applicable | evidence/<decision-id>/README.md | evidence-url"

Proposal Record​

When a page is created or materially changed, the proposal record should identify:

{
  "proposal_id": "proposal.example.001",
  "target_page": "docs/path/example.md",
  "proposal_type": "create | update | deprecate | supersede | delete",
  "proposer_class": "maintainer | contributor | external | llm_assisted | browser_originated | user_submitted",
  "claimed_page_posture": "concept",
  "claimed_maturity_posture": "conceptual",
  "authority_class": "wiki_maintainer | vocabulary_editor | external_contributor | contributor_suggest",
  "policy_ref": "policy.wiki.page-review.v1",
  "evidence_posture": "present",
  "claimed_relationships": [
    {
      "relationship": "equivalent | overlapping | adjacent | broader_than | narrower_than | contradicts",
      "external_term": "Example external term",
      "external_domain": "Example domain",
      "notes": "Why this relationship is claimed."
    }
  ]
}

Page Decision Record​

When a page change is accepted, denied, escalated, or refused, the decision record should identify:

{
  "decision_id": "decision.example.001",
  "proposal_id": "proposal.example.001",
  "target_page": "docs/path/example.md",
  "decision": "ALLOW | DENY | ESCALATE | REFUSE | DEFER | SUPERSEDE",
  "authority_class": "wiki_maintainer",
  "policy_ref": "policy.wiki.page-review.v1",
  "evidence_posture": "sufficient",
  "review_posture": "entity_reviewed | maintainer_reviewed | quorum_reviewed | external_reference",
  "commit_time_validity": true,
  "relationship_disposition": [
    {
      "external_term": "Example external term",
      "relationship": "equivalent",
      "disposition": "accepted | rejected | deferred",
      "notes": "Reason for disposition."
    }
  ],
  "issued_at": "2026-06-17T00:00:00Z"
}

Provide the command, artifact, or record that can re-check the page decision when applicable.

If no executable replay exists yet, mark the link as not_applicable and explain why.

Provide the evidence location needed to reconstruct why the page decision appeared to have standing.

This may include proposal text, review notes, policy references, related proof-path examples, ontology diffs, or formalism-test artifacts.

Limits​

State what this page does not prove or claim.

  • Link to related glossary pages.
  • Link to implementation pages.
  • Link to proof-path pages when relevant.
  • Link to governance pages when relevant.

Ontology Update Required​

If the page defines or changes a core term, update:

static/ontology/admissibility-vocabulary.v0.1.json

Validation Checklist​

Before publishing or accepting a mature page, verify:

  • page status is declared;
  • page posture is declared;
  • maturity posture is declared;
  • authority boundary is explicit;
  • term relationship placement is complete or explicitly not applicable;
  • proposal link is present or explicitly marked not_applicable;
  • decision link is present or explicitly marked not_applicable;
  • replay link is present or explicitly marked not_applicable;
  • reconstruction link is present or explicitly marked not_applicable;
  • ontology update requirement is satisfied or explicitly not required;
  • the page does not claim proof authority unless it links to the actual proof authority artifact.