Admin Wiki

Ring clones store operational knowledge in a Postgres vault: tenant-wide pages plus optional project-order spaces. Humans edit at /admin/wiki and on Order Lab desks; agents search and mutate through ring-mcp using the same WikiKernel.

Admin Wiki

Ring clones store operational knowledge in a Postgres vault: tenant-wide pages plus optional project-order spaces. Humans edit at /admin/wiki and on Order Lab desks; agents search and mutate through ring-mcp using the same WikiKernel.

Admin Wiki

Ring clones store operational knowledge in a Postgres vault: tenant-wide pages plus optional project-order spaces. Humans edit at /admin/wiki and on Order Lab desks; agents search and mutate through ring-mcp using the same WikiKernel.

Typical scenarios

1. Platform playbook — Admins keep tenant pages for “how we ringize”, payment rails, and support macros.
2. Per-order brain — Buyer and integrator share a po:{orderId} vault for that clone’s decisions (no secrets — those stay in Order Lab #secrets).
3. Agent ingest — ring-mcp creates/updates concept pages, appends ops events, and lints dead [[wikilinks]].
4. Cross-vault cite — From a project page, link platform concepts with [[@Payments]] or [[tenant:Payments]].

Operator checklist

• Open /admin/wiki as platform admin; confirm _schema seeded (title lives in the right rail).
• Use rail Actions: CRM project orders, News, CRM tasks, Wiki docs.
• Create a folder path (e.g. concepts) by setting path on new pages — folders are path prefixes, not empty docs.
• Use [[Page]] for same-vault links; use [[@Title]] to cite tenant knowledge from a project vault.
• On /my-orders/[id] or /my-jobs/[id], use Project Wiki for that order only.
• Never paste Firebase keys or RingBase tokens into wiki bodies.

Who can write what

Wikilinks

Module map

ring-mcp tools

1. 1

   Apply migration

   bash

   
   psql "$DATABASE_URL" -f data/migrations/040_wiki_pages.sql

   Also present in data/schema.sql for fresh installs. No wiki-specific env vars are required beyond the existing Postgres DATABASE_URL / MCP service token.

2. 2

   Call WikiService from adapters only

   typescript

   
   import * as WikiService from '@/features/wiki/wiki-service'
   import { resolveWikiActor } from '@/features/wiki/resolve-wiki-actor'
   import type { VaultKey } from '@/features/wiki/types'
   
   const actor = await resolveWikiActor({
     userId: session.user.id,
     role: session.user.role,
     orderId, // when scoping a project vault
   })
   await WikiService.ensureTenantSchema(actor)
   const vault: VaultKey = 'tenant'
   const pages = await WikiService.listPages(actor, vault)

   MCP handlers set isAgent: true so tenant write rules apply even if the service token role is superadmin.

3. 3

   Append vs replace

   typescript

   
   await WikiService.updatePage(actor, pageId, {
     bodyMarkdown: '## Note\nIntegrator addendum…',
     mode: 'append', // required for integrator on tenant
   })

Deep-dive: JSONB collection pattern (`id` + `data`) used by wiki_pages and siblings.

Typical scenarios

1. Platform playbook — Admins keep tenant pages for “how we ringize”, payment rails, and support macros.
2. Per-order brain — Buyer and integrator share a po:{orderId} vault for that clone’s decisions (no secrets — those stay in Order Lab #secrets).
3. Agent ingest — ring-mcp creates/updates concept pages, appends ops events, and lints dead [[wikilinks]].
4. Cross-vault cite — From a project page, link platform concepts with [[@Payments]] or [[tenant:Payments]].

Operator checklist

• Open /admin/wiki as platform admin; confirm _schema seeded (title lives in the right rail).
• Use rail Actions: CRM project orders, News, CRM tasks, Wiki docs.
• Create a folder path (e.g. concepts) by setting path on new pages — folders are path prefixes, not empty docs.
• Use [[Page]] for same-vault links; use [[@Title]] to cite tenant knowledge from a project vault.
• On /my-orders/[id] or /my-jobs/[id], use Project Wiki for that order only.
• Never paste Firebase keys or RingBase tokens into wiki bodies.

Who can write what

Wikilinks

Module map

ring-mcp tools

1. 1

   Apply migration

   bash

   
   psql "$DATABASE_URL" -f data/migrations/040_wiki_pages.sql

   Also present in data/schema.sql for fresh installs. No wiki-specific env vars are required beyond the existing Postgres DATABASE_URL / MCP service token.

2. 2

   Call WikiService from adapters only

   typescript

   
   import * as WikiService from '@/features/wiki/wiki-service'
   import { resolveWikiActor } from '@/features/wiki/resolve-wiki-actor'
   import type { VaultKey } from '@/features/wiki/types'
   
   const actor = await resolveWikiActor({
     userId: session.user.id,
     role: session.user.role,
     orderId, // when scoping a project vault
   })
   await WikiService.ensureTenantSchema(actor)
   const vault: VaultKey = 'tenant'
   const pages = await WikiService.listPages(actor, vault)

   MCP handlers set isAgent: true so tenant write rules apply even if the service token role is superadmin.

3. 3

   Append vs replace

   typescript

   
   await WikiService.updatePage(actor, pageId, {
     bodyMarkdown: '## Note\nIntegrator addendum…',
     mode: 'append', // required for integrator on tenant
   })

Deep-dive: JSONB collection pattern (`id` + `data`) used by wiki_pages and siblings.

Typical scenarios

1. Platform playbook — Admins keep tenant pages for “how we ringize”, payment rails, and support macros.
2. Per-order brain — Buyer and integrator share a po:{orderId} vault for that clone’s decisions (no secrets — those stay in Order Lab #secrets).
3. Agent ingest — ring-mcp creates/updates concept pages, appends ops events, and lints dead [[wikilinks]].
4. Cross-vault cite — From a project page, link platform concepts with [[@Payments]] or [[tenant:Payments]].

Operator checklist

• Open /admin/wiki as platform admin; confirm _schema seeded (title lives in the right rail).
• Use rail Actions: CRM project orders, News, CRM tasks, Wiki docs.
• Create a folder path (e.g. concepts) by setting path on new pages — folders are path prefixes, not empty docs.
• Use [[Page]] for same-vault links; use [[@Title]] to cite tenant knowledge from a project vault.
• On /my-orders/[id] or /my-jobs/[id], use Project Wiki for that order only.
• Never paste Firebase keys or RingBase tokens into wiki bodies.

Who can write what

Wikilinks

Module map

ring-mcp tools

1. 1

   Apply migration

   bash

   
   psql "$DATABASE_URL" -f data/migrations/040_wiki_pages.sql

   Also present in data/schema.sql for fresh installs. No wiki-specific env vars are required beyond the existing Postgres DATABASE_URL / MCP service token.

2. 2

   Call WikiService from adapters only

   typescript

   
   import * as WikiService from '@/features/wiki/wiki-service'
   import { resolveWikiActor } from '@/features/wiki/resolve-wiki-actor'
   import type { VaultKey } from '@/features/wiki/types'
   
   const actor = await resolveWikiActor({
     userId: session.user.id,
     role: session.user.role,
     orderId, // when scoping a project vault
   })
   await WikiService.ensureTenantSchema(actor)
   const vault: VaultKey = 'tenant'
   const pages = await WikiService.listPages(actor, vault)

   MCP handlers set isAgent: true so tenant write rules apply even if the service token role is superadmin.

3. 3

   Append vs replace

   typescript

   
   await WikiService.updatePage(actor, pageId, {
     bodyMarkdown: '## Note\nIntegrator addendum…',
     mode: 'append', // required for integrator on tenant
   })

Deep-dive: JSONB collection pattern (`id` + `data`) used by wiki_pages and siblings.