TECHNICAL DEEP DIVE

How ScribeOps Works

A detailed walkthrough of the ScribeOps pipeline: from Slack thread detection to privacy-safe runbook generation.

STEP 01

Heuristic Thread Detection

ScribeOps uses lightweight NLP heuristics to detect resolution patterns in conversations. It looks for signal phrases: 'fixed it', 'that solved it', 'deploying the fix', 'marking resolved'. No heavy ML models run on your data.

// Detection heuristics (simplified)
const RESOLUTION_SIGNALS = [
  /(?:fixed|resolved|deployed|patched)\s+(?:it|the|this)/i,
  /marking.*(?:resolved|done|closed)/i,
  /(?:root cause|RCA).*(?:was|is|identified)/i,
];

// Trigger only fires after 3+ participants
// and at least one code snippet or error trace

STEP 02

Local Redaction Engine

Before any content leaves your environment, a containerized redaction engine strips PII, API keys, internal URLs, customer identifiers, and credential patterns. The engine runs as a sidecar in your Kubernetes cluster or as a Docker container.

// Redaction categories
REDACT: {
  PII:        [emails, names, phone numbers],
  SECRETS:    [API keys, tokens, passwords],
  INFRA:      [internal IPs, hostnames, ports],
  CUSTOMER:   [account IDs, org names, PII],
}

// Output: sanitized thread JSON
// Original content: NEVER transmitted

STEP 03

Structured Extraction

The sanitized thread is processed through our extraction pipeline which identifies the problem structure, key actors, timeline, and resolution steps. Output follows a strict JSON schema mapped to your documentation template.

// Output schema (ADR example)
{
  "type": "architecture_decision_record",
  "title": "string",
  "context": "string",
  "decision": "string",
  "alternatives_considered": ["string"],
  "consequences": ["string"],
  "status": "proposed | accepted | deprecated",
  "participants": ["redacted_role"],
  "confidence_score": 0.0-1.0
}

STEP 04

Approval & Publishing

Generated runbooks are delivered via Slack DM to the designated approver (configurable per channel). Approvers can edit inline, request regeneration, or approve with a single tap. Approved documents publish to your configured destination via OAuth integration.

// Webhook payload on approval
POST /api/v1/webhooks/approval
{
  "document_id": "INC-0847",
  "approved_by": "user_role_hash",
  "destination": "notion",
  "workspace_id": "ws_xxx",
  "database_id": "db_xxx",
  "published_at": "2025-08-23T14:30:00Z"
}

RBAC Permission Inheritance

ScribeOps mirrors your Slack channel permissions in the destination wiki. Private channels produce private documents. Only users with access to the source channel can view the generated runbook.

🌐

Public channel

→ Public wiki page

🔒

Private channel

→ Restricted wiki page

⛔

DM group

→ Not monitored