Skip to main content

Context​

Eigenoid started as a multi-component project (Python package, A2A runtime, internal documentation, tooling). Until now, the code lived under the personal account @andylow92 (andylow92/SPIRE-A2A-Protocol), which is reasonable for an individual experiment but becomes fragile as soon as more people, AI agents, or bot-driven automation enter the picture: repo ownership, billing, secrets, and permissions all end up coupled to a single human user. Before adding more repos or inviting collaborators, we need to decide on a long-term home.

Decision​

We create a dedicated GitHub organization called eigenoid to host all of the project's code, documentation, and infrastructure, instead of continuing to work under personal accounts.

Consequences​

  • Clear identity and ownership: code and repos belong to the project, not to an individual. If someone leaves, access and continuity are preserved.
  • Centralized permissions: we can manage members, teams, and permissions at the org level instead of inviting people repo by repo.
  • Reusable bots and apps: GitHub Apps and secrets can be defined once at the org level and applied to all repos.
  • Controlled visibility: all repos default to private, aligned with the internal nature of the product.
  • Additional operational overhead: we need to maintain org membership, configure org-level settings (security, billing, branch protection), and migrate pre-existing repos from personal accounts.
  • We need a minimally useful plan tier (Free is enough to start, but some features like required reviewers in orgs require Team).

Alternatives considered​

  • Keep repos under personal accounts (andylow92/...): zero migration cost, but couples the project to one person and makes formal collaboration and permission management difficult.
  • Monorepo under a personal account: simplifies navigation but inherits the same ownership problems and also complicates independent versioning of subcomponents.
  • Organization on another provider (GitLab, Bitbucket): the tooling and community ecosystem we need (Actions, Discussions, Apps, Copilot) is more mature on GitHub.

References​