OpenVibe.Wiki

OpenVibe.Wiki is described in its README as "wiki spaces with page trees, revisions, citations, media and discussion — editable together, source-backed". At the cited commit the repository held only a charter: the README gives the status as placeholder ("planning only, no runnable code yet"), and STATUS.json records that it has no code. The README names openvibe.wiki as the domain and AGPL-3.0 as the license, and refers to the OpenVibe End-to-End Realignment & Implementation Plan, revision 3.

Planned purpose

The charter describes the knowledge product: spaces, canonical page identities and slugs, immutable revisions, redirects, citations and infoboxes. AI proposes revisions through registered workflows; humans publish.

Ownership

The charter lists wiki tables for spaces, pages, revisions, links, redirects, citations, infobox values, permissions, watchers and AI proposals. Wiki does not own discussion, since OpenVibe.Community owns talk pages; attachments, which OpenVibe.Media owns; or "publication truth by AI (never)". OpenVibe.Search indexes only published state.

Planned surfaces

Creating or importing a space, page tree navigation, edit, preview, publish and revert, history and diff, a citation inspector, backlinks and link validation, and AI research proposals with review state.

Dependencies

The charter lists the shared publishing packages (OpenVibe.Publishing), OpenVibe.Network, OpenVibe.Media, OpenVibe.Community, OpenVibe.AI with the source registry, Search and OpenVibe.Events. It states there is no current implementation and that Wiki bootstraps from the shared publishing runtime.

Acceptance and launch rule

Before the service counts as done, the charter requires an immutable lineage through create, edit, publish, revise, diff and revert; citations attached to the exact revision that used them; private or deleted pages leaving search, sitemaps and caches consistently; and public pages that are useful with JavaScript disabled. The domain keeps its placeholder page on OpenVibe.Sites until an owning runtime, identity integration, public routes useful without JavaScript, real persistence, contract registration, a security review and acceptance tests exist. The README states: "A placeholder is never counted as an implemented service."