Lilith Metaverse · Reference & analysis

V3 Documentation and Runbooks

accessibility controls, privacy controls, and escalation path.

2sections1 minread1table

On this page

Release gate: v3-documentation-runbooks.v1

Verifier: pnpm verify:v3 documentation-runbooks

This gate covers V3/V3_TODOS.md §71. A §71 item is complete only when the source document, evidence manifest, OpenAPI route, examples, and CI verifier all agree.

Coverage#

Area Required coverage Source
User help center Tara, Saraswati, and Commons GA surfaces V3/help-center/*.md
Operator runbooks Every day-one Lilith Operator Console action with an SLA V3/runbooks/operator-console-actions.md
Creator docs Each Lilith Studio publishable artifact type V3/creator-docs/lilith-studio-publishing.md
V3 BFF API docs Every /api/v3/* BFF route with OpenAPI and examples apps/lilith/bff/openapi/v3-lilith-launch.openapi.yaml

Signoff Rules#

  • Help articles must identify the GA surface, route, primary user tasks, accessibility controls, privacy controls, and escalation path.
  • Operator action runbooks must include owner, trigger, SLA, escalation, rollback, audit event, and verification command.
  • Creator docs must let a publisher complete the artifact without a second source of truth: inputs, steps, review gates, output, failure handling, and verification are required.
  • OpenAPI docs must include request and response schemas plus examples for the launch-route decision families.

The release evidence is stored at V3/docs/documentation-runbooks-release-gate.json.