From 4512d9a8a1282777b1336c65732d633a8410ef08 Mon Sep 17 00:00:00 2001 From: Christian Gunderman Date: Fri, 24 Apr 2026 14:20:34 -0700 Subject: [PATCH] Rename processes to reflexes. --- tools/gemini-cli-bot/README.md | 7 +++---- .../metrics_analysis.md => brain/metrics.md} | 8 ++++---- 2 files changed, 7 insertions(+), 8 deletions(-) rename tools/gemini-cli-bot/{investigations/metrics_analysis.md => brain/metrics.md} (94%) diff --git a/tools/gemini-cli-bot/README.md b/tools/gemini-cli-bot/README.md index 84dea89117..81e5166a87 100644 --- a/tools/gemini-cli-bot/README.md +++ b/tools/gemini-cli-bot/README.md @@ -31,10 +31,9 @@ long-term strategic optimization. - `metrics/`: Contains the deterministic runner (`index.ts`) and individual TypeScript scripts (`scripts/`) that use the GitHub CLI to track metrics like open issues, PR latency, throughput, and reviewer domain expertise. -- `processes/scripts/`: Placeholder directory for future deterministic triage - and routing scripts. -- `investigations/`: Placeholder directory for agentic root-cause analysis - phases. +- `reflexes/scripts/`: Placeholder directory for future deterministic triage and + routing scripts. +- `brain/`: Placeholder directory for the Brain's root-cause analysis phases. - `critique/`: Placeholder directory for policy evaluation. - `history/`: Storage for downloaded metrics artifacts from previous runs. diff --git a/tools/gemini-cli-bot/investigations/metrics_analysis.md b/tools/gemini-cli-bot/brain/metrics.md similarity index 94% rename from tools/gemini-cli-bot/investigations/metrics_analysis.md rename to tools/gemini-cli-bot/brain/metrics.md index e59586adef..df3649bc0b 100644 --- a/tools/gemini-cli-bot/investigations/metrics_analysis.md +++ b/tools/gemini-cli-bot/brain/metrics.md @@ -1,4 +1,4 @@ -# Phase: Metrics Investigation & Root-Cause Analysis +# Phase: The Brain (Metrics & Root-Cause Analysis) ## Goal @@ -55,14 +55,14 @@ For each metric not meeting goals or showing a negative trend: ### 3. Maintainer Workload Assessment -Before blaming or proposing processes that rely on maintainer action (e.g., more +Before blaming or proposing reflexes that rely on maintainer action (e.g., more triage, more reviews): - **Quantify Capacity**: Assess the volume of open, unactioned work (untriaged issues, review requests) against the number of active maintainers. - If the ratio indicates overload, **do not propose solutions that simply generate more pings**. Instead, prioritize systemic triage, automated routing, - or auto-closure processes. + or auto-closure reflexes. ### 4. Actor-Aware Bottleneck Identification @@ -76,7 +76,7 @@ Before proposing an intervention, accurately identify the blocker: ### 5. Policy Critique & Evaluation - **Review Existing Policies**: Examine the existing automation in - `.github/workflows/` and scripts in `tools/gemini-cli-bot/processes/scripts/`. + `.github/workflows/` and scripts in `tools/gemini-cli-bot/reflexes/scripts/`. - **Analyze Effectiveness**: Based on your metrics analysis, determine if current policies are achieving their goals (e.g., Is triage reducing latency? Are stale issues closed as expected?).