Дмитрий
39 lines
1.4 KiB
Markdown
39 lines
1.4 KiB
Markdown
# Worked example — the deal-lifecycle process
|
|
|
|
A worked `process-modeling` artifact: the lead→deal lifecycle as a BPMN-style
|
|
swimlane. Demonstrates the C10 modeling workflow. Status slugs are illustrative —
|
|
the source of truth for the funnel is `db/schema.sql`.
|
|
|
|
```mermaid
|
|
flowchart TD
|
|
subgraph Поставщик
|
|
A((Лид поступил)) --> B[Лид в проекте-канале]
|
|
end
|
|
subgraph Менеджер
|
|
B --> C{Лид валиден?}
|
|
C -->|нет| D((Отклонён))
|
|
C -->|да| E[Создать сделку — статус new]
|
|
E --> F[Квалификация]
|
|
F --> G{Квалифицирован?}
|
|
G -->|нет| H((Потерян — lost))
|
|
G -->|да| I[Работа по сделке — in_progress]
|
|
end
|
|
subgraph Система
|
|
I --> J{Итог сделки}
|
|
J -->|успех| K((Выиграна — won))
|
|
J -->|провал| H
|
|
K --> L[Списание по тарифу — LedgerService]
|
|
L --> M((Завершено))
|
|
end
|
|
```
|
|
|
|
## How this was built
|
|
|
|
1. **process-analysis** (discovery mode) reconstructed the as-is flow from
|
|
`routes/*.php`, the deal controllers, and the status enum in `db/schema.sql`.
|
|
2. **process-modeling** chose the swimlane artifact (three roles, branching) and
|
|
wrote the BPMN structure.
|
|
3. The **mermaid** skill rendered the source above.
|
|
4. **operations** `process-doc` skill would wrap this into a full process
|
|
document when one is needed.
|