Skip to content

Document multi-repository routing direction - #9

Merged
m17kea merged 1 commit into
mainfrom
codex/document-multi-repo-future-work
Jul 16, 2026
Merged

Document multi-repository routing direction#9
m17kea merged 1 commit into
mainfrom
codex/document-multi-repo-future-work

Conversation

@m17kea

@m17kea m17kea commented Jul 16, 2026

Copy link
Copy Markdown

Context

Record the agreed multi-repository direction before implementation so repository routing stays bounded and broader orchestration remains explicitly deferred.

TL;DR

Use allowlisted Jira repo labels now; defer agent-planned cross-repo delivery.

Summary

  • Define symphony-repo-<alias> as the near-term repository-routing contract
  • Require one allowlisted repository per Jira implementation issue
  • Document agent-created subtasks and coordinated acceptance as future work
  • Add issue context for workspace hooks as a possible upstream contribution

Alternatives

  • A Symphony deployment per repository was rejected because it duplicates schedulers, UIs, and lease coordination.
  • Arbitrary repository URLs in Jira were rejected because they bypass the controlled GitHub and execution boundary.
  • Automatic planning and rollout were deferred until label-based routing is proven.

Test Plan

  • make -C elixir all
  • git diff --check
  • Reviewed the rendered Markdown diff for current and future scope separation

Summary:
- document allowlisted Jira repository labels for the next prototype
- record agent-planned subtasks and coordinated rollout as future work
- identify issue context for hooks as a possible upstream contribution

Rationale:
- keep the next implementation simple and close to upstream Symphony
- preserve a clear path toward safe cross-repository coordination later

Tests:
- make -C elixir all
- git diff --check

Co-authored-by: Codex <codex@openai.com>
@m17kea
m17kea merged commit 20d9fd8 into main Jul 16, 2026
2 checks passed
@m17kea
m17kea deleted the codex/document-multi-repo-future-work branch July 16, 2026 18:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant