portal/docs/process/README.md

docs/process — business-process playbook (map section C10)

Home of the C10 «Бизнес-процессы (общее)» section. Defines the tooling Лидерра uses to model, automate and analyze business processes.

Toolset

Tool	Role	Status
operations plugin	9 skills — process-doc, process-optimization, change-request, capacity-plan, compliance-tracking, risk-assessment, runbook, status-report, vendor-review.	installed — operations@knowledge-work-plugins v1.2.0
process-modeling skill	Model a to-be process — BPMN 2.0, process maps, customer-journey / value-stream, RACI, state-machines.	installed — self-authored skill
process-analysis skill	Analyze an as-is process — discovery from code/audit-logs, bottlenecks, traceability, BP metrics.	installed — self-authored skill
n8n-mcp	Workflow-automation engine.	deferred — see below
mermaid · architecture-patterns · CCPM · product-management · writing-plans	Reuse — diagram render · DDD process boundaries · requirements→process traceability · process specs/metrics · process decomposition.	reuse — cross-referenced into C10

Boundaries (which tool for which job)

• Documenting a process / a change to it / capacity / generic optimization → the operations plugin skills (process-doc, change-request, capacity-plan, process-optimization, …).
• Designing a to-be process model (formal BPMN 2.0, swimlane, state-machine) → the process-modeling skill — which delegates rendering to the mermaid skill (operations and process-modeling emit Mermaid source; mermaid renders — OPS1/BPMN1).
• Reverse-engineering an as-is process from the Лидерра codebase → the process-analysis skill (discovery from routes/, app/Jobs, audit_* tables — what the generic process-optimization skill cannot do; OPS5).
• The operations capacity-plan skill plans cross-functional business-process capacity; dev-team sprint capacity is product-management /sprint-planning (OPS2).
• The operations change-request skill = a business-process change; an architecture decision is an ADR (adr-kit); a normative-doc edit is claude-md-management (OPS3).
• process-analysis finds business-process bottlenecks; code/runtime performance is perf-analyzer / analysis:bottleneck-detect (PA1).

n8n-mcp — why deferred

n8n-mcp builds workflows for the n8n platform. The Лидерра stack has no n8n — the process engine is the Laravel queue (Redis) + events/jobs. Adopting n8n as portal infrastructure is an architecture decision, not a tooling pick. n8n-mcp is a reserved slot: registered in the Tooling registry as pending, installed by a separate severable task when (and if) n8n is adopted via its own ADR. See the C10 plan's "Deferred Task".