Skip to content

docs: link organization lessons learned controls #2

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
Elodie Mirza (elodiejmirza) merged 1 commit into from
Jun 20, 2026
Merged

docs: link organization lessons learned controls #2

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 3 additions & 0 deletions AGENTS.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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.
Expand Down
Loading