← Back to catalogue
Research draft

wiki

vr.tr.wiki · PHY.OBJ

Enable an agent to recognise a wiki, assess its content and editing state, and determine which contributions or maintenance actions are appropriate.

Thing Registry Physical world and living systems

Research draft, second pass

A second pass drafted this model: the structure a model of this thing needs, and what is known about it in the world. The line under this one says how the second half was obtained - researched against sources, or recalled without web access, in which case nothing here was read anywhere and every claim is a lead to verify. Unreviewed either way.

recalled by Codex without web access - no source was read

Researched by: Codex

Purpose and description

Enable an agent to recognise a wiki, assess its content and editing state, and determine which contributions or maintenance actions are appropriate.

A wiki is a website or networked hypertext system that enables users with appropriate permissions to create, edit and interlink pages through a shared interface, typically retaining a history of revisions.

It can be Locate the canonical page for a topic and inspect its links, revisions and editorial status.; Create or revise pages within the workspace's topic boundary and contribution rules.; Compare revisions and propose or perform an authorised restoration of earlier content.; Repair links, consolidate duplicate pages and maintain redirects while preserving relevant history.; Raise a discussion or request review when a contribution is disputed or requires approval.; Assess and export permitted content together with the dependencies and history needed for its intended reuse..

Distinguishing features

Its principal content units are addressable pages organised as a navigable, interlinked workspace, rather than primarily chronological posts or message threads.

Authorised contributors can revise shared pages as maintained resources, rather than only submit comments or separate responses.

Editing changes the shared body of content; collaboration is not limited to exchanging individually owned files.

Wiki denotes the content workspace and its editing practices here; an installed wiki engine without such a workspace is a neighbouring software entity.

Public access, anonymous editing and encyclopaedic subject matter are not required recognition tests; the model must record the actual access and editorial arrangements.

Scope

+ Workspace identity, subject boundary and page organisation

+ Collaborative page creation, editing and revision handling

+ Internal links, reusable content and navigation conventions

+ Contributor permissions, discussion and editorial governance

+ Content provenance, maintenance status and recoverability

- Wiki engine source code and software product lifecycle

- Physical servers, storage devices and network infrastructure

- Independent models of subjects described by wiki pages

- The owning organisation's wider structure and activities

- General-purpose document collaboration without a wiki workspace

Characteristics

Subject and audience boundary
Declared topics, intended readers and inclusion criteria Determines whether a proposed page or contribution belongs in the workspace.
Wiki engine
Supporting software and relevant enabled extensions, if known Identifies which editing, revision and automation capabilities must be verified.
Page addressing convention
Title or identifier rules, namespaces, redirects and canonical addresses Supports reliable page discovery and prevents accidental duplicate topics.
Contribution access
Anonymous, registered, invited, role-restricted or locally defined combinations Establishes who may contribute and under what identity.
Revision exposure
Immediately visible, pending review, staged or locally defined workflow Determines when an edit affects readers.
Revision traceability
History available, partial, unavailable or unknown; attribution and comparison capabilities recorded Indicates whether changes can be inspected and attributed.
Page protection
Unrestricted within workspace, protected by role, locked or unknown Constrains permissible edits to particular pages.
Content reuse terms
Applicable licence or policy, including exceptions for imported text and media Governs whether content may be imported, exported or redistributed.
Broken internal link count
Links, with inspection date and treatment of intentional links to uncreated pages Helps distinguish planned page creation from navigation defects.
Content review age
Days since substantive review, per page; unknown where no review is recorded Supports maintenance decisions without treating a recent edit as proof of accuracy.

Also called

Gamepedia wikiPhrictionMediaWiki instancespecialized wikiencyclopedic wikidictionary wikiformer wikiKilakita WikiMediaWiki wikiblikiclosed wikiopen wikisemantic wikiReception WikisMiraheze website

Where this came from

wikidata · CC0 1.0

Source repository Registry entry point

Drafted structure

Bundle to layer to finding to question, as the second pass will find it: 6 bundles · 11 layers · 18 findings · 28 questions.

Workspace and page identity Identifies the wiki's subject boundary and the rules that make a page the recognised home for a topic.

An agent needs to distinguish the wiki from its engine and avoid creating competing pages for the same subject.

Workspace boundary

Establishes which information community and collection this wiki represents.

Wiki sense and remit

Record whether the registered thing denotes a wiki workspace, and identify its intended subjects, readers and exclusions.

  1. Does wiki here denote the shared information workspace, the editing approach or the software that implements it? definition
  2. Which subject and audience rules determine whether a proposed page belongs in this wiki? boundary

Canonical page identity

Captures page naming, namespaces and continuity across moves or merges.

Titles, identifiers and redirects

Record how pages are uniquely addressed and how alternate names continue to resolve after editorial restructuring.

  1. Which title, namespace and identifier rules distinguish separate pages from alternate names for one page? definition
  2. When a page is renamed or merged, how should links, redirects and revision attribution be preserved? action
Editing and revision control Describes how contributions become shared page content and how their effects can be inspected or reversed.

Wiki contributions modify maintained resources, so an agent must understand visibility, concurrent editing and restoration behaviour.

Edit publication

Captures the route from a proposed change to the version readers encounter.

Save, review and conflict behaviour

Record editor capabilities, publication gates and the handling of overlapping edits.

  1. Does saving a page expose the change immediately, or does a review or staging step intervene? definition
  2. How must an agent detect and resolve an edit conflict without overwriting another contributor's changes? action

Revision inspection and restoration

Establishes the available evidence of change and the limits of undoing it.

History, diffs and reverts

Record revision attribution, comparison support, history gaps and permitted restoration operations.

  1. Which revisions, contributor identities, timestamps and edit summaries are retained and accessible? provenance
  2. Can an unwanted change be reversed selectively, and what later edits or dependent pages would the reversal affect? action
Linked content and reuse Represents the page relationships and shared components through which the wiki organises information.

A page edit can affect navigation or many rendered pages, making link meaning and reusable dependencies necessary parts of the model.

Page network

Captures internal links, topic grouping and deliberate gaps in coverage.

Links, categories and uncreated pages

Record how readers discover related pages and distinguish intentionally uncreated targets from broken navigation.

  1. Which links, categories, indexes or equivalent structures establish the wiki's topic organisation? definition
  2. How many unresolved internal links are intentional requests for new pages, and how many result from moves, deletion or naming errors? measurement

Shared content dependencies

Identifies reusable content whose changes can propagate beyond its own page.

Templates, inclusions and media

Record whether templates, transclusion, shared media or structured properties are used and which pages depend on them.

  1. Which reusable components supply content or presentation to other pages in this wiki? definition
  2. Before changing or deleting a shared component, how can an agent identify and preview its effects on dependent pages? action
Participation and content trust Connects contribution authority, discussion and evidence to the state of shared pages.

Technical edit access does not by itself establish editorial authority or the reliability of page content.

Editorial authority

Captures who may act and how disagreements or protected-page changes are handled.

Permissions, protection and discussion

Record workspace roles, page-specific restrictions and the recognised route for obtaining editorial decisions.

  1. Which roles may edit, move, delete, protect or restore pages, and which page-level restrictions override general access? boundary
  2. Where should an agent propose a disputed change or request an action it cannot perform directly? action

Evidence and reuse rights

Distinguishes revision attribution from support for claims and permission to reuse material.

Claim support and content origin

Record supporting references, imported-content origins, review markers and applicable reuse terms without treating edit history as verification.

  1. What references, local records or review decisions support a page's substantive claims, and which claims remain disputed or unverified? provenance
  2. What licences or permissions cover the page text and embedded media, including material imported from elsewhere? boundary
Wiki maintenance and continuity Describes how the shared corpus remains usable, current and recoverable.

A functioning editor can coexist with abandoned pages, damaging automated edits or incomplete backups.

Corpus maintenance

Captures maintenance signals and controls over repeated or automated contributions.

Review backlogs and automated edits

Record stale-page indicators, unresolved maintenance requests and the rules governing bot or bulk edits.

  1. Which pages lack a substantive review within the wiki's own review interval, and which maintenance requests remain unresolved? measurement
  2. What preview, rate, approval and rollback requirements apply before an agent performs bulk or automated edits? action

Export and recovery

Establishes whether the wiki can be preserved or restored with its meaningful relationships intact.

Recoverable wiki corpus

Record export and backup coverage for pages, revisions, attachments and shared components, together with evidence of restoration.

  1. Do available exports or backups include revision history, media, redirects and reusable components, or only current page text? boundary
  2. What restoration or migration check has demonstrated that pages, links and included content remain usable? provenance
Evidence and external alignment What the world already says about this thing, gathered so the model can be checked against it.

A model that cannot be lined up against existing standards, identifiers and practice cannot be adopted by anyone who already uses them.

Reported evidence

Findings from the breadth pass, kept separate from the structural claims.

Check these first

Recalled without web access and unsourced; every item is a lead to verify.

  • This describes the general computing sense of wiki; the supplied PHY.OBJ classification should be checked because a wiki is ordinarily a digital information system.
  • Open public editing, anonymous contributions and simultaneous editing are not defining requirements.
  • Permissions, revision retention, identifiers and editing syntax vary by implementation; no universal capacities or wiki-specific regulatory standard are asserted.
  1. Which of these check these first hold for the sense of wiki this model covers, and on what evidence? provenance

Kinds and varieties

Recalled without web access and unsourced; every item is a lead to verify.

  • Public community wiki
  • Private organisational wiki
  • Personal wiki
  • Semantic wiki
  1. Which of these kinds and varieties hold for the sense of wiki this model covers, and on what evidence? provenance

Identifiers and schemes

Recalled without web access and unsourced; every item is a lead to verify.

  • Page title within a wiki - Page title, optionally qualified by a namespace - Identifies a page within a particular wiki; uniqueness, case sensitivity and namespace rules depend on the software.
  • Software-assigned page and revision identifiers - Implementation-specific identifiers - Many wiki engines distinguish a page's persistent identity from identifiers for individual saved revisions; there is no universal wiki identifier scheme.
  1. Which of these identifiers and schemes hold for the sense of wiki this model covers, and on what evidence? provenance

Real-world use

Recalled without web access and unsourced; every item is a lead to verify.

  • Collaborative encyclopaedias and reference collections
  • Internal organisational knowledge bases
  • Software and technical documentation
  • Project coordination and shared working notes
  • Educational collaboration
  1. Which of these real-world use hold for the sense of wiki this model covers, and on what evidence? provenance

Typical measurements

Recalled without web access and unsourced; every item is a lead to verify.

  • Revision count per page - No generally applicable typical range - revisions
  • Active contributors over a defined reporting period - No generally applicable typical range - contributors
  1. Which of these typical measurements hold for the sense of wiki this model covers, and on what evidence? provenance

Failure modes and hazards

Recalled without web access and unsourced; every item is a lead to verify.

  • Vandalism, spam or deliberately misleading edits
  • Outdated or unsupported information persisting without review
  • Accidental disclosure through permissive access controls or retained revision history
  • Conflicting edits and disputes over content
  • Broken links, orphaned pages and duplicated content reducing discoverability
  1. Which of these failure modes and hazards hold for the sense of wiki this model covers, and on what evidence? provenance

Regional variation

Recalled without web access and unsourced; every item is a lead to verify.

  • Language editions and local communities may use different terminology, editorial policies and content priorities.
  1. Which of these regional variation hold for the sense of wiki this model covers, and on what evidence? provenance

Neighbouring kinds and how to tell them apart

Recalled without web access and unsourced; every item is a lead to verify.

  • Wiki engine - The engine is the software implementing wiki functions; a wiki is the site or information system operated with it.
  • Wikipedia - Wikipedia is a particular encyclopaedia project using wikis; a wiki need not be encyclopaedic or publicly editable.
  • Content management system - A content management system is a broader software category; a wiki characteristically centres collaborative editing of interlinked pages.
  • Knowledge base - A knowledge base is defined by its information-storage purpose; it may use wiki software but need not support wiki-style editing.
  • Collaborative document editor - A collaborative document editor centres shared documents; a wiki centres a navigable collection of interlinked pages.
  1. Which of these neighbouring kinds and how to tell them apart hold for the sense of wiki this model covers, and on what evidence? provenance

What the second pass must settle

  • Does the registry intend wiki as a workspace, a software category or an editing method, and is the supplied PHY / PHY.OBJ placement appropriate for that sense?
  • Does an existing Vercy world model already cover this concept, requiring a registry link rather than a separate publication?
  • Which capabilities are essential to recognising a wiki, and which should remain optional, particularly revision history, discussion pages and transclusion?
  • Which authoritative sources should support the eventual researched definition and its boundary with collaborative documents and content management systems?
  • Which engine-specific behaviours and local governance rules require separate profiles rather than assertions about all wikis?
Draft as JSON