Workflows
Context
This section documents the end-to-end operational flows that matter most for delivery continuity: data import, alerting, GitHub issue automation, manual AI code review, and Copilot session retrospectives.
Details
Use this section for flow-level understanding (what happens, in what order, and what to do when something fails).
Core V2 pages: - import-pipeline.md: import flow from source data to enriched output. - alert-system.md: alert triggers, SMTP flow, and fail-open behavior. - github-issue-bridge.md: how issue creation automation works from repository context.
AI code review operating mode (current policy):
- Trigger /speckit.review manually after commit, push, and PR creation.
- Use the generated terminal report as the decision artifact.
- Do not rely on direct PR publication as a mandatory step.
- Record the review decision manually in the PR when needed.
Copilot session review operating mode (current policy):
- Trigger /speckit.session-review manually once at session closure.
- Let Chronicle collect compact aggregates before reading detailed turns.
- Compare no more than five relevant activity reports.
- Record recommendations in the matching bilingual activity report; do not create a separate business report.