Decision
Done. jolt-architecture lives in the RyeValley org. Verified 2026-08-15 against the GitHub API: RyeValley/jolt-architecture resolves, and benorn213/jolt-architecture returns a 301 redirect to it, which is what GitHub leaves behind after a transfer. clawdy-architecture moved the same way (Live Google OAuth credential leaked in clawdy-architecture, needs rotation).
This record was reopened in error on 2026-08-15 while seeding open decisions from unresolved inbox signals. The signal was stale: the transfer had already happened. Closing it against the live state rather than the signal.
Context
Raised in Git identity incident: Mini global config leaked into Ben's personal repo and again when Ben invited hermes@ryevalley.co as collaborator on both repos (inbox/2026-07-30-jolt-clawdy-github-invites.md). Collaborator invites to personal repos are a workaround, not org-level access control.
Options considered
- Transfer jolt-architecture to the RyeValley org (org owns JOLT architecture), matching the clawdy-architecture precedent. Scan git history for secrets first (lesson from the clawdy credential leak).
- Leave under Ben’s account with collaborator access as-is.
Consequences
Until decided, JOLT architecture docs live outside org access control and offboarding risk sits with a personal account.