From 31a75da01ff64ee404dd67cfc0403455fb9377f5 Mon Sep 17 00:00:00 2001 From: Elodie Mirza Date: Sat, 20 Jun 2026 13:41:12 +0100 Subject: [PATCH] docs: link organization lessons learned controls Signed-off-by: Elodie Mirza --- AGENTS.md | 3 +++ 1 file changed, 3 insertions(+) diff --git a/AGENTS.md b/AGENTS.md index 731f4e3..88dd5f5 100644 --- a/AGENTS.md +++ b/AGENTS.md @@ -17,6 +17,9 @@ ## Workflow - Use feature branches with the `codex/` prefix. +- Before planning organization-spanning workflow, security-control, package, project, or governance changes, review the central SoloSentry lessons register in `SoloSentryOrg/github-enterprise-management-solosentry` at `docs/lessons-learned/register.md`. +- For organization-spanning changes, carry applicable lessons into the plan and include a short `complexity removed or justified` statement. +- Stop repeated same-cluster fix-forward until root cause is recorded in the relevant issue, PR, or central lessons register. - Treat this as a solo-maintainer repository unless the user says otherwise. - Do not recommend or apply branch-protection rules that require an independent approval when no second reviewer has been configured; that blocks