From af8c33591068d43d8faf6221422d56ce0c5ea26e 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 325ac683..f3c87d0d 100644 --- a/AGENTS.md +++ b/AGENTS.md @@ -28,6 +28,9 @@ - Use feature branches with the `codex/` prefix for Codex changes. - Keep changes narrowly scoped and aligned with upstream Dire Wolf conventions. - Prefer small, reviewable patches over broad rewrites. +- 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. - Do not commit generated build trees, local configuration containing station details, audio captures, packet logs, credentials, API tokens, registry caches, or temporary tool state.