Menu

Operations

Verification Required

Runbooks, diagnostics, troubleshooting, and support paths.

Use operations pages to move from symptoms to safe checks, diagnosis, remediation, escalation, evidence capture, and privacy-aware support handoff without turning unreviewed operational behavior into a stronger claim.

Operations Index

  • Runbook template

    Available: DOCS-049

    Standard sections, severity model, approval route, evidence records, safety rules, and reviewer routing for operator runbooks.

  • ObjectDB operator runbooks

    Available: DOCS-050

    Health checks, platform capabilities, S3 gateway limits, local adapter caveats, and support evidence.

  • Message Broker operator runbooks

    Available: DOCS-051

    Health, metrics, audit, diagnostics, storage inspection, quota rejection, replication status boundaries, and support evidence.

  • LogDB operator runbooks

    Available: DOCS-052

    OTLP admission, WAL, segment bundle, query troubleshooting, S3 query-read boundaries, BYOC preflight, and support evidence.

  • Concordia validation runbooks

    Available: DOCS-053

    Cache, Gateway, Storage, TSDB, active service, protocol fixture, validation-script, and evidence handoff workflows.

  • Observability and audit guide

    Available: DOCS-054

    Cross-product health, metrics, audit, logs, diagnostics, support bundle evidence, and privacy-safe handoff practices.

  • Troubleshooting index

    Available: DOCS-055

    Symptom-oriented troubleshooting entries organized by product, first check, likely cause, next action, evidence, and runbook route.

  • Support bundle and privacy page

    Available: DOCS-056

    Support bundle contents, exclusions, redaction expectations, approval triggers, and privacy review boundaries.

  • Production CDN, DNS, cache, and rollback plan

    Available: DOCS-101

    Cutover gates, docs-dev, docs-tst, production validation, DNS alias checks, CloudFront invalidation, cache-header evidence, rollback steps, owners, and go/no-go records.

  • Launch observability and incident hooks

    Available: DOCS-103

    Deployment health, 404s, failed searches, client-side errors, page-load regressions, feedback signals, watch cadence, and escalation paths for launch.

  • Dependency, license, and vulnerability audit

    Available: DOCS-102

    npm, Gatsby, .NET automation, Playwright, package-license, vulnerability, private-feed, owner-decision, and remediation evidence for launch readiness.

Operations Guardrails

Evidence Before Remediation

Runbooks should capture the evidence a reviewer or support engineer needs before a state-changing step can alter the signal.

Privacy-Aware Handoff

Support bundles, logs, traces, tokens, tenant data, and customer payloads need explicit redaction guidance before sharing.

Reviewer-Routed Claims

Product, operations, support, security, privacy, docs QA, and docs lead reviewers decide when wording can move beyond verification-required.