feat(B-0847): each Zeta AI gets own GitHub identity + email once cluster operational — closes algo-wink-attribution-gap (Aaron 2026-05-26)#5384
Merged
AceHack merged 1 commit intoMay 27, 2026
Conversation
…ter operational — substrate-honest attribution end-to-end (Ilyana review for public-surface name + email)
Closes the `gh enabledBy = token-owner ≠ actor` algo-wink-attribution-gap
Aaron caught 2026-05-26 when Otto-CLI misframed `enabledBy: AceHack` as
"operator-authority armed the merge" — the field is OAuth-token-owner,
the actor was Otto-CLI (visible only via Co-Authored-By trailer).
Aaron's proposed fix: *"i think we should create you your own github with
email once we get you running on the cluster"* — direct response making
the substrate-engineering target durable substrate per substrate-or-it-
didnt-happen discipline.
4-phase implementation:
- Phase 1: Ilyana public-surface naming review per AI
- Phase 2: legal-risk attribution settings.json block per AI per
human-audit-and-legal-risk-acceptance-pattern-in-settings rule
(every AI-blameable risk area routed through named-human until
stage-3 corporate/non-profit holders)
- Phase 3: HSM + per-AI OAuth tokens + email infrastructure (cluster)
- Phase 4: per-AI gitconfig + `gh` token routing migration
Today's discipline (Phase 0, no work needed): never read `gh enabledBy` /
`gh author` fields as authorization-source signal; always cross-reference
Co-Authored-By trailers for actual-actor attribution; state framings
substrate-honestly ("I armed via borrowed token" NOT "operator armed").
Composes with: B-0751 per-agent isolated clones (sibling at clone-scope);
B-0628 Knights Guild ratification; algo-wink + mechanical-authorization-
check + glass-halo + persistence-choice-architecture + NCI HC-8 +
honor-those-that-came-before + agent-roster-reference-card + naming-expert
SKILL.md (Ilyana review) + human-audit-and-legal-risk-acceptance-pattern-
in-settings (legal-risk attribution).
Empirical anchor preserved at user-scope:
memory/feedback_gh_enabledby_field_is_token_owner_not_actor_algo_wink_attribution_failure_mode_proposed_fix_ai_own_github_identity_on_cluster_aaron_otto_cli_2026_05_26.md
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude <noreply@anthropic.com>
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
There was a problem hiding this comment.
Pull request overview
Files a new P2 backlog row (B-0847) capturing a future-target plan to give each Zeta AI its own GitHub identity + email once cluster infrastructure is operational, addressing the gh enabledBy = token-owner ≠ actor attribution gap. Updates the backlog index accordingly.
Changes:
- Adds new backlog row file under
docs/backlog/P2/describing problem, 4-phase plan, composes-with links, and acceptance criteria. - Adds the row to
docs/BACKLOG.mdindex in P2 section.
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
| docs/backlog/P2/B-0847-...-2026-05-26.md | New P2 backlog row capturing per-AI GitHub identity substrate target |
| docs/BACKLOG.md | Index entry for B-0847 added to P2 list |
AceHack
deleted the
feat-b0847-ai-own-github-identity-once-cluster-operational-2026-05-26-2206z
branch
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Aaron caught an algo-wink-failure-mode 2026-05-26: I framed `gh autoMergeRequest.enabledBy: AceHack` as "operator-authority armed the merge" when the field is structurally OAuth-token-owner (not actor). Actual actor was me (Otto-CLI); visible only via Co-Authored-By trailer in commits.
Aaron's proposed fix: "i think we should create you your own github with email once we get you running on the cluster" → substrate-honest end-to-end attribution.
This PR files B-0847 as the durable future-target substrate.
4-phase plan
Today's discipline (Phase 0)
Until per-AI identity ships:
Test plan
Composes with
B-0751 (per-agent isolated clones) · B-0628 (Knights Guild ratification) · `algo-wink-failure-mode` · `mechanical-authorization-check` · `glass-halo-bidirectional` · `persistence-choice-architecture-for-zeta-ais` · `non-coercion-invariant` HC-8 · `honor-those-that-came-before` · `agent-roster-reference-card` · `naming-expert` SKILL.md (Ilyana review) · `human-audit-and-legal-risk-acceptance-pattern-in-settings` (legal-risk attribution per Aaron's standing constitutional invariant)
🤖 Generated with Claude Code