Skip to content

refactor: begin Phase 2 event interpretation boundary - #325

Closed
eshulman2 wants to merge 14 commits into
phase1/domain-contractsfrom
phase2/event-interpretation
Closed

refactor: begin Phase 2 event interpretation boundary#325
eshulman2 wants to merge 14 commits into
phase1/domain-contractsfrom
phase2/event-interpretation

Conversation

@eshulman2

@eshulman2 eshulman2 commented Aug 27, 2026

Copy link
Copy Markdown
Collaborator

Summary

  • introduce an infrastructure-free ingress adapter contract and registry
  • move Jira ticket-type/observation interpretation and source-control observation/PR-correlation evidence out of OrchestratorWorker
  • make worker source registration data-driven
  • derive stable, versioned workflow commands for approval, rejection, retry, questions, checks, reviews and merges in shadow mode
  • make unmatched/wrong-stage signals explicitly inspectable as ignored decisions
  • document the remaining Phase 2 delivery slices and compatibility rules

Stack

Verification

  • uv run ruff check src/forge/orchestrator/worker.py src/forge/orchestrator/event_adapters tests/unit/orchestrator/event_adapters
  • uv run pytest -q tests/unit/orchestrator/event_adapters tests/unit/orchestrator/test_worker.py (103 passed)

@eshulman2
eshulman2 force-pushed the phase2/event-interpretation branch from 2bf175b to 6395a86 Compare August 31, 2026 09:25
@eshulman2
eshulman2 marked this pull request as ready for review August 31, 2026 11:49
@eshulman2

Copy link
Copy Markdown
Collaborator Author

Superseded by the Forge 2.0 squash merged in #339.

@eshulman2 eshulman2 closed this Sep 6, 2026
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